[Puppet Users] Re: Facter 4 release

Thank you for pointing this out, we added a link to Facter 4 repo ( https://github.com/puppetlabs/facter-ng) in the Facter 3 Readme ( https://github.com/puppetlabs/facter/blob/master/README.md) On Tuesday, March 31, 2020 at 12:38:07 AM UTC+3, Stefan Wrobel wrote: > > Where is the source for the

Re: [Puppet Users] Re: Facter 4 release

Since it was developed in parallel, they used https://github.com/puppetlabs/facter-ng. I don't know if there are plans to reconcile them in the future, but Bogdan could tell you about that later. On Mon, Mar 30, 2020 at 2:38 PM Stefan Wrobel wrote: > Where is the source for the 4.x releases? >

[Puppet Users] Re: Facter 4 release

Where is the source for the 4.x releases? https://github.com/puppetlabs/facter only seems to have 3.x as the latest... On Wednesday, March 18, 2020 at 9:54:40 AM UTC-7, Bogdan Irimie wrote: > > Hi, > > I am very happy to announce the first release of Facter 4 >

[Puppet Users] Re: facter details copy to central location

Thanks Peter, I have created manifest to get details On Tuesday, July 25, 2017 at 8:29:31 PM UTC+5:30, Amber Mehra wrote: > > Hey Guys, > > I have certain requirement to get puppet client inventory like "facter > operatingsystem, facter ipaddress, etc : copied all details to some where > in

[Puppet Users] Re: facter details copy to central location

Have you looked at Puppet DB? (There's also a record of facts in /var/lib/puppet/yaml/facts/ for Puppet 3.x - might be available in Puppet 4 and 5 too.) On Tuesday, 25 July 2017 16:59:31 UTC+2, Amber Mehra wrote: > > Hey Guys, > > I have certain requirement to get puppet client inventory like

Re: [Puppet Users] Re: Facter error: empty packages.json

Hi Adam, The related code in Facter is at https://github.com/puppetlabs/facter/blob/master/lib/src/facts/external/json_resolver.cc#L211-L214 It appears that the JSON library we use (RapidJSON) considers an empty file to be an error condition, and we just raise that up without introspecting it.

[Puppet Users] Re: Facter error: empty packages.json

On Wed, Mar 1, 2017 at 6:50 PM, Adam Mercer wrote: > Error: Facter: error while processing > "/opt/puppetlabs/facter/facts.d/packages.json" for external facts: The > document is empty. I have now started seeing this on both Debian 8 and Ubuntu 16.04. Any ideas where to start

[Puppet Users] Re: Facter - custom fact regex

Thank you for the info John. I did fix the typo and it looks like the fact wasn't sync'd correctly to the client. It's all fixed up now and working as expected. You've always been a great help and I very much appreciate your time. Let me know where to send the six pack. Cheers, Mike On

[Puppet Users] Re: Facter - custom fact regex

That is a great idea and I'll get that changed to something else. Cheers, Mike On Thursday, January 14, 2016 at 10:23:06 AM UTC-8, Thomas Müller wrote: > > IMHO the fact "network" is a default fact from facter >= 3. i would change > the name. > -- You received this message because you are

[Puppet Users] Re: Facter - custom fact regex

On Tuesday, January 12, 2016 at 5:42:45 PM UTC-6, Mike Reed wrote: > > Hello all, > > I'm having some trouble with a custom fact and I was hoping somebody could > tell me what I'm doing wrong. > > Here is an example of the code: > > require 'facter' > Facter.add('network') do > setcode do >

[Puppet Users] Re: facter 3.0 not using /etc/facter/facts.d by default

On Thursday, June 25, 2015 at 7:35:36 AM UTC-7, math...@therussells.me wrote: I think this is a documentation issue only. Looking at this ticket https://tickets.puppetlabs.com/browse/FACT-826 I see mention of a different fact directory. Once i copied my facts to that new directory

[Puppet Users] Re: facter 3.0 not using /etc/facter/facts.d by default

I think this is a documentation issue only. Looking at this ticket https://tickets.puppetlabs.com/browse/FACT-826 I see mention of a different fact directory. Once i copied my facts to that new directory it picks them up. On Thursday, June 25, 2015 at 10:01:44 AM UTC-4,

[Puppet Users] Re: facter error esolved to an invalid value

On Wednesday, February 11, 2015 at 7:04:18 AM UTC-6, Robert Reilly wrote: All, I am getting the following problem with facter on 5 of my nodes, Fact resolution fact='enviro', resolution='anonymous' resolved to an invalid value: Expected (?-mix:xxx(vs|sv).{2,7}\d{1,2}) to be one of

[Puppet Users] Re: facter error esolved to an invalid value

Tried upgrading facter on that node, but same error ... On Wednesday, February 11, 2015 at 8:04:18 AM UTC-5, Robert Reilly wrote: All, I am getting the following problem with facter on 5 of my nodes, Fact resolution fact='enviro', resolution='anonymous' resolved to an invalid value:

[Puppet Users] Re: Facter on Amazon AMI with ruby2

On Wednesday, July 16, 2014 at 2:30:44 AM UTC-4, Peter Romfeld wrote: Hi, I have problems to get facter running: OS: Amazon Linux AMI release 2014.03 Ruby: ruby 2.0.0p451 (2014-02-24 revision 45167) [x86_64-linux] I tried the amz provided facter package and also facter2.1 from

[Puppet Users] Re: facter external-dir

Not really a puppet question or a puppet answer man alias (bash command) You should be able to alias the command and put into bash_profile for all users when they login. On Wednesday, December 24, 2014 10:28:09 AM UTC-7, guymatz wrote: Is there any way to get facter to return facts from

Re: [Puppet Users] Re: facter external-dir

I guess if the answer had been more of a puppet answer, my question would have been more of a puppet question. :-) Sorry to bother. Thanks, Guy On Wed, Dec 24, 2014 at 12:42 PM, Craig White white.n...@gmail.com wrote: Not really a puppet question or a puppet answer man alias (bash command)

[Puppet Users] Re: facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

On Wednesday, October 30, 2013 12:50:59 PM UTC-4, Paul Tötterman wrote: Hi, Is anyone else getting this: $ facter /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require': cannot load such file -- facter/application

[Puppet Users] Re: facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

I have installed version 2.0.0 from source. I saw the same error. But running ./install.rb fixed it! Oz On Wednesday, October 30, 2013 10:50:59 AM UTC-6, Paul Tötterman wrote: Hi, Is anyone else getting this: $ facter

Re: [Puppet Users] Re: facter error message - what does this mean?

Hi All, yes same with me. I restarted the system and errors are gone. Still was not able to find the root cause. I m good for now after the restart. With Warm Regards Kaustubh.A.Chaudhari (M)-09373102619 On Wed, Oct 1, 2014 at 3:21 PM, jmp242 jp10...@gmail.com wrote: Ok, thanks, it turns

[Puppet Users] Re: facter error message - what does this mean?

I also see this on 3.7.1... Same symptoms. On Wednesday, September 24, 2014 8:16:54 AM UTC-4, JonY wrote: I'm seeing this error appear on a client machine (/var/log/syslog): puppet-agent[17158]: Failed to apply catalog: Could not retrieve local facts: Invalid facter option(s) type If I

Re: [Puppet Users] Re: facter error message - what does this mean?

On Wed, Oct 1, 2014 at 9:48 AM, jmp242 jp10...@gmail.com wrote: I also see this on 3.7.1... Same symptoms. On Wednesday, September 24, 2014 8:16:54 AM UTC-4, JonY wrote: I'm seeing this error appear on a client machine (/var/log/syslog): puppet-agent[17158]: Failed to apply catalog:

[Puppet Users] Re: facter error message - what does this mean?

And here's the trace=true output: Oct 1 13:04:16 lnx7179 puppet-agent[18029]: Local environment: production doesn't match server specified node environment dev, switching agent to dev. Oct 1 13:04:17 lnx7179 puppet-agent[18029]: Could not retrieve local facts: Invalid facter option(s) type

Re: [Puppet Users] Re: facter error message - what does this mean?

On Wed, Oct 1, 2014 at 10:05 AM, Wil Cooley wcoo...@nakedape.cc wrote: On Wed, Oct 1, 2014 at 9:48 AM, jmp242 jp10...@gmail.com wrote: I also see this on 3.7.1... Same symptoms. On Wednesday, September 24, 2014 8:16:54 AM UTC-4, JonY wrote: I'm seeing this error appear on a client machine

[Puppet Users] Re: facter error message - what does this mean?

Ok, thanks, it turns out restarting the puppet service fixes this error. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [Puppet Users] Re: facter error message - what does this mean?

Hi, I was on 1.7 now upgraded to 2.2. With Warm Regards Kaustubh.A.Chaudhari (M)-09373102619 On Sat, Sep 27, 2014 at 1:43 PM, Jason Antman ja...@jasonantman.com wrote: What facter versions are you running? On Fri, Sep 26, 2014 at 6:02 AM, kaustubh chaudhari kaustu...@gmail.com wrote:

Re: [Puppet Users] Re: facter error message - what does this mean?

I don't know where that Invalid facter option(s) exception is coming from. Can you run with trace=true? Thanks! On Fri, Sep 26, 2014 at 3:02 AM, kaustubh chaudhari kaustu...@gmail.com wrote: Hi, I am also facing same issue. unable to find where to look for, puppet agent runes file facter

Re: [Puppet Users] Re: facter error message - what does this mean?

What facter versions are you running? On Fri, Sep 26, 2014 at 6:02 AM, kaustubh chaudhari kaustu...@gmail.com wrote: Hi, I am also facing same issue. unable to find where to look for, puppet agent runes file facter runes fine if run manually. But schedule run still not working. Any

[Puppet Users] Re: facter error message - what does this mean?

Hi, I am also facing same issue. unable to find where to look for, puppet agent runes file facter runes fine if run manually. But schedule run still not working. Any help is appreciated. FYI: This happened after upgrade from 3.3.2 to 3.6.2 -Kaustubh On Wednesday, September 24, 2014 8:16:54

[Puppet Users] Re: facter error message - what does this mean?

Hi, I am also facing same issue. unable to find where to look for, puppet agent runes file facter runes fine if run manually. But schedule run still not working. Any help is appreciated. FYI: This happened after upgrade from 3.3.2 to 3.6.2 -Kaustubh On Wednesday, September 24, 2014

[Puppet Users] Re: Facter doesnt resolve ipaddress or ipaddress_eth0

List, just to document the solution. My CentOS was localized and facter couldn't parse de output properly. Changing the locale to en_US solves this issue. Joao Morais Em quinta-feira, 26 de junho de 2014 14h25min27s UTC-3, Joao Morais escreveu: Hello list. I am trying to read the IP

Re: [Puppet Users] Re: Facter doesnt resolve ipaddress or ipaddress_eth0

Hmm, I find that hard to believe, ie. that's a pretty massive and fundamental bug in facter if that is indeed the case. Can you reproduce on other boxes? R. On 28 July 2014 19:19, Joao Morais l...@joaomorais.com.br wrote: List, just to document the solution. My CentOS was localized and

Re: [Puppet Users] Re: Facter doesnt resolve ipaddress or ipaddress_eth0

Em 28/07/14 16:34, Robin Bowes escreveu: Hmm, I find that hard to believe, ie. that's a pretty massive and fundamental bug in facter if that is indeed the case. Perhaps I have a not-so-common use case? I'm manually running (local rundeck) puppet agent in my tests via ssh. Ssh was sending my

[Puppet Users] Re: Facter unable to parse custom fact

As I understand from Facrer 2 manual (http://docs.puppetlabs.com/facter/2.1/custom_facts.html#adding-custom-facts-to-facter) I can set all custom facts to /etc/facts/facts.d. Fact example: Facter.add(role) do setcode do Facter::Util::Resolution.exec('ec2-describe-tags -O KEY -W KEY

Re: [Puppet Users] Re: Facter unable to parse custom fact

You are confusing custom and external facts, as david explained. Regards, El 22/07/2014 18:33, Maxim Nikolaev m...@maximnik.com escribió: As I understand from Facrer 2 manual ( http://docs.puppetlabs.com/facter/2.1/custom_facts.html#adding-custom-facts-to-facter) I can set all custom facts to

[Puppet Users] Re: Facter unable to parse custom fact

The problem is not fact script. I I run it from /usr/lib/ruby/site_ruby/1.8/facter/ it's working. When I set it to /etc/facter/facts.d - I get errors. More. If I make link from /etc/facter/facts.d to /usr/lib/ruby/site_ruby/1.8/facter/ also other fact scripts fail. On Tuesday, July 15, 2014

Re: [Puppet Users] Re: Facter unable to parse custom fact

Dear Maxim, /etc/facter/facts.d and /usr/lib/ruby/site_ruby/1.8/facter/ are used for two completely different kinds of scripts that cannot be mixed. /etc/facter/facts.d contains either text files with *static* facts OR executable *programs* returning a specific text format.

Re: [Puppet Users] Re: Facter path issue

On Fri, Jul 18, 2014 at 11:56 AM, Jim Richard jimr6...@gmail.com wrote: Yep, a custom fact. In case someone else happens upon this looking for a similar answer, here's my custom fact to override Facter's default path fact: Facter.add('path') do confine :kernel = 'windows' setcode do

[Puppet Users] Re: Facter path issue

Yep, a custom fact. In case someone else happens upon this looking for a similar answer, here's my custom fact to override Facter's default path fact: Facter.add('path') do confine :kernel = 'windows' setcode do my_fact = Facter::Util::Resolution.exec('C:\Windows\system32\cmd.exe /C reg

Re: [Puppet Users] Re: facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

Hello, I came looking for this exact error, but specifying --server puppetmaster.domain or setting server = puppetmaster.domain in puppet.conf doesn't allow a successful run of puppet. The error is the same as Paul had above: Error: Could not request certificate: SSL_connect returned=1

[Puppet Users] Re: Facter errors with InfiniBand and VDSM

On Sunday, February 9, 2014 1:34:57 PM UTC-8, treydock wrote: After some debugging it seems it's the ;vdsmdummy; interface that's causing both problems. I have a host with Infiniband, and the same version of Puppet and Facter, that has no errors running facter. My guess is when

Re: [Puppet Users] Re: facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

facter-1.7.4-rc1 is available and it looks like it works! Actually, it wasn't until 1.7.5 that the packages available from downloads.puppetlabs.com were fixed, but it really seems to work now. However, I have a problem with puppet on OS X 10.9. I'm using the latest packaged version 3.4.2. It

Re: [Puppet Users] Re: facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

Paul, that ssl error looks like the following post on puppet-users: https://groups.google.com/forum/#!topic/puppet-users/4-6EimF_-NY/discussion, which relates to SNI. Adding a server alias to your puppetmaster vhost may resolve your problem. This is a change in ruby after 1.9.0, so it wouldn't

Re: [Puppet Users] Re: facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

Paul, that ssl error looks like the following post on puppet-users: https://groups.google.com/forum/#!topic/puppet-users/4-6EimF_-NY/discussion, which relates to SNI. Thank you for pointing me in the right direction. Adding a server alias to your puppetmaster vhost may resolve your

[Puppet Users] Re: Facter errors with InfiniBand and VDSM

After some debugging it seems it's the ;vdsmdummy; interface that's causing both problems. I have a host with Infiniband, and the same version of Puppet and Facter, that has no errors running facter. My guess is when ifconfig is executed for ;vdsmdummy; it's not using '2 /dev/null', but I

[Puppet Users] Re: facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

facter-1.7.4-rc1 is available and it looks like it works! Martijn Op woensdag 30 oktober 2013 17:50:59 UTC+1 schreef Paul Tötterman: Hi, Is anyone else getting this: $ facter

[Puppet Users] Re: facter timeouts

On Tuesday, 5 November 2013 15:14:26 UTC, jcbollinger wrote: On Monday, November 4, 2013 10:38:00 AM UTC-6, james.e...@fasthosts.comwrote: Hi, I am having some issues with facter on a couple of servers which have a large number of ip addresses. Essentially, all my puppet runs time out

[Puppet Users] Re: facter timeouts

On Monday, November 4, 2013 10:38:00 AM UTC-6, james.e...@fasthosts.com wrote: Hi, I am having some issues with facter on a couple of servers which have a large number of ip addresses. Essentially, all my puppet runs time out because facter takes in excess of 25 seconds to populate

[Puppet Users] Re: facter behaves different for different users

On Thursday, October 10, 2013 9:41:50 AM UTC-5, Bernd Weber wrote: Anybody? I'm not particularly interested in analyzing your transcripts to identify the differences. Would you care to clue us in? In any event, facter output may differ for different users for at least these reasons:

[Puppet Users] Re: facter behaves different for different users

John, thanks for the reply. You know how it is, you attache the output - I don't want to analyze your transcripts, you don't attach them - 'Please attach the output otherwise we can't help you'... Well, let's move on, shall we. As described on top of the post the issue lies with specifically

[Puppet Users] Re: facter behaves different for different users

On Friday, October 11, 2013 8:53:41 AM UTC-5, jcbollinger wrote: I'm not particularly interested in analyzing your transcripts to identify the differences. Would you care to clue us in? Sorry, you did mention the $::ec* facts, and I see that they are present in one output and not the

[Puppet Users] Re: facter behaves different for different users

Thanks John appreciate this feedback. I did not see that. Let me do some testing and research. There might be something to this. Not sure why there would be several versions installed but better to double-check. I'll get back to you after some more digging. -- You received this message

[Puppet Users] Re: Facter value at Catalog compilation

On Thursday, September 19, 2013 4:23:15 PM UTC-5, Frederiko Costa wrote: Hi, I've got a facter shipped with a custom module. This factor returns the version of a determined package. It returns nil if the package is not installed yet. When running for the first time, assuming the

Re: [Puppet Users] Re: Facter value at Catalog compilation

Sure ... Here it is: # # terracota_version.rb # # Reports terracota version if terracotta is installed Facter.add(:terracotta_version) do cmd = %x{/bin/rpm -qa terracotta --queryformat %{VERSION}} setcode do if ! cmd.nil? cmd else nil end end end -frederiko On Fri, Sep 20, 2013 at

[Puppet Users] Re: Facter value at Catalog compilation

Post the code for the custom fact? On Thursday, September 19, 2013 2:23:15 PM UTC-7, Frederiko Costa wrote: Hi, I've got a facter shipped with a custom module. This factor returns the version of a determined package. It returns nil if the package is not installed yet. When running for

[Puppet Users] Re: facter string value comparison to integer

hi hyde, You don't need to convert facter string into integer before comparing to integer value, puppet internally take care of it. I just checked it on open source puppet version - 2.7.12 and puppet enterprise version - 2.7. On Monday, August 5, 2013 8:38:09 PM UTC+5:30, hyde wrote: It

[Puppet Users] Re: facter 1.7.1 crashed on sshfp_* facts

Looks like this is a some problem with ruby/dependencies [root@ndb2r0 ~]# cat 1.rb #!/usr/bin/ruby # require 'digest/sha1' require 'base64' require 'digest/sha2' puts Digest::SHA256.hexdigest(123) [root@ndb2r0 ~]# ruby 1.rb Illegal instruction But this version looks good: [root@ndb2r0 ~]# cat

[Puppet Users] Re: facter 1.7.1 crashed on sshfp_* facts

additional info: #0:/usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:89:Hash:: if @facts.empty? #0:/usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:89:Hash:: if @facts.empty? #0:/usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:89:Facter::Util::Collection:-: if

[Puppet Users] Re: facter wrong report

I'm on 1.7.1, Facter finds xen fine. is_virtual = true virtual = xen odd part is I'm not sure the detection method has changed since 1.6. It just check if any of these paths exist: /proc/sys/xen, /sys/bus/xen, /proc/xen On Wednesday, May 22, 2013 1:06:02 AM UTC-7, Heriyanto wrote: Hi,

Re: [Puppet Users] Re: facter wrong report

Hi Ellison, thank you for help, theres some bug i think in that version, now i use 1.6.18-3.el6 its solved. On Wed, May 22, 2013 at 11:49 PM, Ellison Marks gty...@gmail.com wrote: I'm on 1.7.1, Facter finds xen fine. is_virtual = true virtual = xen odd part is I'm not sure the detection

[Puppet Users] Re: Facter fact appears to be a string and not an array.

On Wednesday, May 15, 2013 2:15:14 AM UTC-5, Brent wrote: Would anyone know why I am getting a string as opposed to an array. Because all facts are strings. That's the way it has always been, though I understand there's some work underway to provide for more data types in the future.

[Puppet Users] Re: Facter Strings to integer.

On Monday, March 18, 2013 11:16:41 AM UTC-5, olli...@googlemail.com wrote: Hello, If I want to do something like this:- if $::lsbdistrelease = 6.3 { SOMETHING } Do I have to convert lsbdistrelease from a string to a number with an inline template or some such ? Generally

[Puppet Users] Re: Facter and eth1

On Tuesday, January 15, 2013 8:40:56 AM UTC-6, Ygor wrote: I have one older server where the physical NIC port for eth0 won't hold the CAT5 cable in place, so I use the other NIC port, eth1, and have eth0 disabled/turned off Facts ipaddress and netmask accurately duplicate

Re: [Puppet Users] Re: Facter and eth1

(Calvin Hobbes) - Original Message - From: jcbollinger john.bollin...@stjude.org To: puppet-users@googlegroups.com Sent: Wednesday, January 16, 2013 10:57:35 AM Subject: [Puppet Users] Re: Facter and eth1 On Tuesday, January 15, 2013 8:40:56 AM UTC-6, Ygor wrote: I have one older

[Puppet Users] Re: [facter]Bug can't get : ipaddress_ethX

sorry there is a typo : Le mercredi 28 novembre 2012 18:06:54 UTC+1, AnOnJoe a écrit : Hello, I have a problem with facter : eg: facter |grep ipaddress_eth1 ipaddress_eth*1* = 192.168.0.254 works but facter ipaddress_eth1 return nothing Do you know how I can work with this ?

Re: [Puppet Users] Re: [facter]Bug can't get : ipaddress_ethX

Which facter version are you seeing this on? (`facter --version`) On Wed, Nov 28, 2012 at 9:14 AM, AnOnJoe anon...@gmail.com wrote: sorry there is a typo : Le mercredi 28 novembre 2012 18:06:54 UTC+1, AnOnJoe a écrit : Hello, I have a problem with facter : eg: facter |grep

Re: [Puppet Users] Re: [facter]Bug can't get : ipaddress_ethX

Havent read the code yet... But cmd facter xx executes the xx plugin and print the return value. the ipaddress_ethX are part of the ipaddress plugin that is the one that should be executed. Nonetheless as the ipaddress plugin register the ipaddress_ethX facters they would not show either. On

Re: [Puppet Users] Re: [facter]Bug can't get : ipaddress_ethX

*facter --version* *1.5.7* 2012/11/28 Matthaus Owens matth...@puppetlabs.com Which facter version are you seeing this on? (`facter --version`) On Wed, Nov 28, 2012 at 9:14 AM, AnOnJoe anon...@gmail.com wrote: sorry there is a typo : Le mercredi 28 novembre 2012 18:06:54 UTC+1, AnOnJoe

Re: [Puppet Users] Re: [facter]Bug can't get : ipaddress_ethX

I have upgraded my facter version : facter --version 1.6.9 It's now working like a charm Thx. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit

[Puppet Users] Re: Facter does not deliver ip addresses

Hi Krysztof, like this: eth0 Link encap:Ethernet Hardware Adresse 00:50:56:99:05:02 inet Adresse:130.250.8.15 Bcast:130.250.8.255 Maske:255.255.255.0 inet6 Adresse: fe80::250:56ff:fe99:502/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST

[Puppet Users] Re: Facter does not deliver ip addresses

uuh ... /inet addr[...]/ as pattern in ip.rb? a wild guess ... if the output is localized - then puppet won't be able to get the IP address info, right? check. *l1215022:~ # facter | grep _eth* *l1215022:~ # export LC_ALL=en_US* *l1215022:~ # facter | grep _eth* ipaddress_eth0 = 130.250.8.15

[Puppet Users] Re: Facter does not deliver ip addresses

... @joseph: do you have localized ipconfig output? (btw I have facter 1.5.2, puppet 2.6.17, both from suse rpms) Am Donnerstag, 6. September 2012 08:25:45 UTC+2 schrieb Axel Bock: uuh ... /inet addr[...]/ as pattern in ip.rb? a wild guess ... if the output is localized - then puppet won't

Re: [Puppet Users] Re: Facter does not deliver ip addresses

Hi, Why do your init scripts start puppet with a locale other than C? Cheers, -- Stephen Gran Senior Systems Integrator - guardian.co.uk Please consider the environment before printing this email. -- Visit guardian.co.uk -

[Puppet Users] Re: Facter does not deliver ip addresses

I'm on a fresh install of Fedora 17 and using Factor 1.6.11 and Puppet 2.7.19. [root@localhost ~]# ifconfig -a lo: flags=73UP,LOOPBACK,RUNNING mtu 16436 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10host loop txqueuelen 0 (Local Loopback)

Re: [Puppet Users] Re: Facter does not deliver ip addresses

I have no idea what my init scripts are doing actually :) . I am just wondering why nothing shows up when *I* run puppet agent --test. And it still confuses me that this seems to be a requirement (which I could not find anywhere ... not that I looked, though :) for a command line tool which

Re: [Puppet Users] Re: Facter does not deliver ip addresses

On Thu, Sep 6, 2012 at 1:01 AM, Axel Bock axel.b...@arbeitsagentur.de wrote: I have no idea what my init scripts are doing actually :) . I am just wondering why nothing shows up when *I* run puppet agent --test. And it still confuses me that this seems to be a requirement (which I could not

[Puppet Users] Re: Facter does not deliver ip addresses

Hello, @Joseph: not yet. @Eric: sure :) . SLES 11 SP2, and the output is here: http://pastebin.com/jqgNmewk But I have an idea. I have another host where it still works. The host it stopped working on has two IP addresses configured on one (!) network device. so an ip a gives me: [...] 2:

[Puppet Users] Re: Facter does not deliver ip addresses

Hi, How does your ifconfig -a output looks like? Suspects: https://github.com/puppetlabs/facter/blob/master/lib/facter/interfaces.rb https://github.com/puppetlabs/facter/blob/master/lib/facter/util/ip.rb KW On Wednesday, 5 September 2012 09:52:03 UTC+1, Axel Bock wrote: Hello, @Joseph:

[Puppet Users] Re: Facter does not deliver ip addresses

I have the same issue. Did you find a solution? Joseph On Monday, August 20, 2012 11:19:39 AM UTC+3, Axel Bock wrote: Hi readers, another problem of mine. A host which worked just fine on friday is now not able to find out its own IP address. The reason is pretty simple as far as I

[Puppet Users] Re: Facter does not deliver ip addresses

Hi Axel - what OS? What version of Facter? What does the output of your 'ifconfig -a' (or local equivalent) look like? Could you please run 'facter --debug' and pastebin the output somewhere? On Monday, August 20, 2012 1:19:39 AM UTC-7, Axel Bock wrote: Hi readers, another problem of mine.

[Puppet Users] Re: Facter scripts and shell environment variables

On Thursday, August 23, 2012 7:56:38 AM UTC-5, André Fernandes wrote: Thanks for the insight. I've been investigating a bit deeper and found that this is likely an issue with the build of apache I'm using. I've run into the same problem with a squid version facter script and found

[Puppet Users] Re: Facter scripts and shell environment variables

Thanks for the insight. I've been investigating a bit deeper and found that this is likely an issue with the build of apache I'm using. I've run into the same problem with a squid version facter script and found that, in the affected hosts, the squid binary had been compiled with the

[Puppet Users] Re: Facter scripts and shell environment variables

On Wednesday, August 15, 2012 4:12:52 AM UTC-5, André Fernandes wrote: I'm currently running a puppet master-client setup and using facter to gather information on the client hosts. However, I've run into a problem when trying to get the deployed apache version for some of the hosts. My

[Puppet Users] Re: facter plugin requires cause catalog failure, prevent setting up new clients

- Original Message - From: Jo Rhett jrh...@netconsonance.com To: puppet-users@googlegroups.com Cc: r...@devco.net Sent: Wednesday, June 20, 2012 12:05:47 AM Subject: facter plugin requires cause catalog failure, prevent setting up new clients There's a generic problem that I

[Puppet Users] Re: Facter 1.6.9 complains about No LSB modules are available.

On Friday, May 18, 2012 1:28:43 PM UTC+2, Andreas N wrote: it seems that Facter 1.6.9 complains that No LSB modules are available. on every run. This is on Ubuntu 10.04 and 12.04, probably others as well. This message (on stderr) usually comes from calling lsb_release -v when no

[Puppet Users] Re: Facter not initialized in rspec in puppetlabs-stdlib?

On Apr 16, 2:01 pm, Jeff McCune j...@puppetlabs.com wrote: On Sat, Apr 14, 2012 at 8:34 PM, Wil Cooley wilcoo...@gmail.com wrote: On Thursday, April 12, 2012 10:06:25 AM UTC-7, Jeff McCune wrote: The problem is that modules like stdlib need Puppet to be initialized in a manner suitable for

[Puppet Users] Re: Facter on a VM...

Hey.  Just getting back to this issue. It happens on just about every OS, or VM enviro.  I'm currently testing on MacOSX, but have also seen it on various Linux distros, most recently CentOS-6.  I can reproduce it in AWS, VMware, and Virtualbox, but only from my app.  It never happens if in IRB,

[Puppet Users] Re: Facter variable $puppetversion

Following on to http://groups.google.com/group/puppet-users/browse_thread/thread/271f6f6522524207/c90596d1823a1bbf As another data point - I was seeing the same wrong values for $puppetversion on the puppet master - the client says one thing, the server says another. This is puppet 2.7.5. Now

[Puppet Users] Re: facter variables empty

I found it : http://projects.puppetlabs.com/issues/8342 I switch to passenger and it works now. Thanks you On 5 oct, 23:41, Denmat tu2bg...@gmail.com wrote: Hi, sounds like it could be a similar issue of puppet with mongrel. This was raised recently on the list. Have a look at those.

[Puppet Users] Re: facter variables empty

hmm.. I'm new too puppet and I don't understand compile the manifest for the node. I write my manifests on the puppetmaster node. And I test on the client node with : puppetd --test --debug --trace there is no error in the debug trace : debug: [.. many auotorequiring File[/var/puppet/... ] info:

Re: [Puppet Users] Re: facter variables empty

Hi, sounds like it could be a similar issue of puppet with mongrel. This was raised recently on the list. Have a look at those. Also paste the code you are trying to apply so we can see what you're attempting to do. Here is a link that you can use to see some tips on debugging issues.

[Puppet Users] Re: Facter variable $puppetversion

Err, what is that 0.25-5 doc folder and what RPM owns it? rpm -qf /usr/share/doc/puppet-0.25.5 If nothing owns it, you've pretty much proved your system has old Puppet artefacts lying around. Personally I wouldn't trust any of the content in /usr/lib/ruby now. Is this a production system?

[Puppet Users] Re: facter not returning 'fqdn' any more

Nope, facter domain doesn't return anything either. [root@disk10 ~]# facter domain date Tue Sep 13 14:44:21 BST 2011 hostname, dnsdomainname and resolv.conf are just fine, like this: [root@disk10 ~]# hostname disk10 [root@disk10 ~]# dnsdomainname hep.xxx.xxx.ac.uk [root@disk10 ~]# cat

Re: [Puppet Users] Re: facter not returning 'fqdn' any more

Yep - that looks like a bug. The change was here: https://github.com/puppetlabs/facter/commit/f7daae300d5c993052dd6c49b1b5e1f3501eaa10 Basically the domain =~ part is _not_ returning true even though dnsdomainname is returning something, and not falling through as it used to to find the answer

Re: [Puppet Users] Re: facter not returning 'fqdn' any more

I could be wrong about the cause actually ... I think its still a bug though :-). Let me take a closer look at the code and see if I can work it out. ken. On Tue, Sep 13, 2011 at 3:29 PM, Ken Barber k...@puppetlabs.com wrote: Yep - that looks like a bug. The change was here:

Re: [Puppet Users] Re: facter not returning 'fqdn' any more

Since this is urgent and we are in RC, I've raised a bug for you Sans: http://projects.puppetlabs.com/issues/9457 ken. On Tue, Sep 13, 2011 at 3:43 PM, Ken Barber k...@puppetlabs.com wrote: Yeah okay I was close though :-).    if name = Facter::Util::Resolution.exec('hostname')       ...  

Re: [Puppet Users] Re: Facter variable $puppetversion

On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum luke.bi...@lmax.com wrote: Err, what is that 0.25-5 doc folder and what RPM owns it? rpm -qf /usr/share/doc/puppet-0.25.5 If nothing owns it, you've pretty much proved your system has old Puppet artefacts lying around. Personally I wouldn't trust

Re: [Puppet Users] Re: Facter variable $puppetversion

- Original Message - On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum luke.bi...@lmax.com wrote: Err, what is that 0.25-5 doc folder and what RPM owns it? rpm -qf /usr/share/doc/puppet-0.25.5 If nothing owns it, you've pretty much proved your system has old Puppet artefacts

Re: [Puppet Users] Re: Facter variable $puppetversion

Yeah this doesn't seem to be old versions of Puppet. So from my other email ... can you show us the code where you are doing your comparison for $puppetversion? I have a feeling I might know what it is ... although I'm probably wrong ... In fact - grep for 'puppetversion' in all of your puppet

Re: [Puppet Users] Re: Facter variable $puppetversion

If that were true the job of QA would be much easier On Sep 13, 2011 10:48 AM, Douglas Garstang doug.garst...@gmail.com wrote: On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar r...@devco.net wrote: - Original Message - On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum luke.bi...@lmax.com

  1   2   3   >