similar to: Facter docs

Hi All Background: I am running Puppet to configure ESX 3.5 servers by NFS mounting the Puppet binaries and configuration from a shared server. This is to ensure VMware don''t come back refusing support for installing non standard software on the server. # ruby -v ruby 1.8.7 (2009-04-08 patchlevel 160) [i686-linux] # facter -v 1.5.5

Hi, I think the answer is no but is it possible to have a facter output from within puppet ? If i type facter on the command line i miss all the fact that puppet download with the factsync feature. How to see the output of facter including those of the factsync file ? -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list

I''m a newbie attempting to get a custom fact distributed to clients. I''ve followed the instructions at http://reductivelabs.com/trac/puppet/wiki/AddingFacts and based my first fact on a simple recipe. I''m having at least one problem and possibly more. 1) Puppet/facter fails to load the custom fact, complaining that "non- sh interpreters are not currently

Hi, I run into problems with the ipaddress fact using the latest Facter gem (1.6.4, 1.6.5) on SLES11. The versions and gems I use work perfectly fine on SLES10 SP3. The problem: running "facter" without arguments results in an error, even though the erroring fact "ipaddress" is ok. test:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL

I installed the 2.6.2 puppet and facter 1.5.8 gems and tried to run puppet, but it failed with the following message: err: Could not run Puppet configuration client: Could not retrieve local facts: uninitialized constant Facter::IPAddress Then I tried running facter alone: # facter /usr/lib64/ruby/vendor_ruby/1.8/facter/ipmess.rb:19: uninitialized constant Facter::IPAddress (NameError) After

Not sure if this is another issue cropping up with 0.24.1 but I''m getting the following: info: Loading fact raid /etc/puppet/facts/location.rb:5: private method `split'' called for nil:NilClass (NoMethodError) from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `call'' from /usr/lib/ruby/site_ruby/1.8/facter.rb:510:in `value'' from

Hello, Since i use facter 1.5.5 i got error running it by hand. It still work in puppet but i loosed the hability to run it from the command line: (aqadmin)> /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50:in `require'': no such file to load -- facter (LoadError) from /var/lib/gems/1.8/gems/facter-1.5.5/bin/facter:50

I just started getting this error on some machines after a yum update from centos 5.2 to centos 5.3. Does anyone know what it means? Since I''m not a ruby person, I''m not sure how to debug this, but it looks to me like facter is having trouble parsing information about my interfaces. # facter /usr/lib/ruby/site_ruby/1.8/facter/ipmess.rb:19: uninitialized constant

I could swear this worked fine earlier.. Now facter, and hence puppet, do not see the domain name anymore: What could cause this? C:\Temp>facter --version 1.6.2 C:\Temp>facter | findstr kernel kernel => windows kernelmajversion => 6.1 kernelrelease => 6.1.7601 kernelversion => 6.1.7601 C:\Temp>facter fqdn NCS-VDI-05.none C:\Temp>facter hostname NCS-VDI-05

I''ve just committed Facter 1.3.8. All of the work for this release was done by James Turnbull, so everyone should thank him for getting it done. Here''s the changelog: Fixed Rdoc::usage bug on CentOS 5 - closed Puppet #753 and Facter #40 Added support to return multiple interfaces and their IP addresses and MAC addressess as facts. Returns

Sometimes "facter --yaml" doesn''t list all the values specified on the command line. I can''t find rhyme nor reason why. Here''s a demo to show what I mean: # facter --version 1.5.7 # facter --yaml fqdn macaddress lsbdistcodename --- fqdn: my.host.name.example.com lsbdistcodename: squeeze macaddress: "00:00:00:00:00:00" We had been using the above

Quick and dirty: --- lib/facter.rb (revision 203) +++ lib/facter.rb (working copy) @@ -989,6 +989,18 @@ %x{/usr/sbin/scutil --get LocalHostName} end end + Facter.add(:interfaces) do + confine :kernel => :linux + setcode do + %x{/sbin/ifconfig -a -s}.split($/)[1..-1].collect {|line|

int he example below I run facter looking for the fact "sp_serial_number". as you can see, the command facter sp_serial_number returns nothing, but the fact is there and is returned when just running facter and grepping for the fact. Some fact seem to work and others do not. any ideas? marcuspro:~ allan$ facter --version 1.5.7 marcuspro:~ allan$ facter sp_serial_number marcuspro:~

Facter 2.0.0rc1 is a feature release candidate with bug fixes, features and other improvements. Facter 2.0 is designed to accompany the upcoming Puppet 3.0 release and has breaking changes from Facter 1.6.x. Facter 2.0 is not backwards compatible with Puppet 2.6 or 2.7. It includes contributions from the following people: Chris Price, Daniel Black, Daniel Pittman, Garrett Honeycutt, Gary Larizza,

Hello, when running the command "ip a" on a debian VM, I get this 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast

I''m trying to load custom facts via /etc/facter/facts.d/* according to instructions on http://docs.puppetlabs.com/guides/custom_facts.html#structured-data-facts I must have missed a setting somewhere because I get nothing. The first clue may be that /etc/facter didn''t exist. I had to create it manually. Is there a setting or search path I need to create? Details: puppet

Hi, I''ve noticed that defining multiple facts in one file is possible, and puppet can make use of them correctly, but when trying to call with facter --puppet they are not shown, do I need something special to make them work as any other single custom fact? Master is running 2.6.7 This is a custom fact with two facts in it: [modules/foobar/lib/facter/foobar.rb ] require

Hi All. I am using: #rpm -qa | egrep ''puppet|facter'' puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch facter-1.7.1-1.el6.x86_64 on: #cat /etc/redhat-release ; uname -r CentOS release 6.4 (Final) 2.6.32-358.11.1.el6.centos.plus.x86_64 My hostname is server.one.two.com: # hostname server.one.two.com # hostname --fqdn one.two.com #grep HOSTNAME /etc/sysconfig/network

I''ve just filed http://reductivelabs.com/trac/puppet/ticket/1182 with the aim of making it easier to add fact pickup from dmidecode in manufacturer.rb. As the ticket says, I think that the fact sections, keys and values shouldn''t be hardcoded in manufacturer.rb, but should be stored in a configuration file somewhere. This means that a given stable installation of Puppet can be

For 40 days and 40 nights Facter wandered in the wilderness sustained only by the occasional patch and bottle of Kool-Aid. Slightly less tanned and equally happy Facter 1.5.8 has arrived! 1.5.8 is a feature and maintenance release containing a number of fixes, updates and additional tests. You can get the release at: http://reductivelabs.com/downloads/facter/facter-1.5.8.tar.gz Please log any