similar to: custom fact and environment variable

I have created my first ''fact'', first attempt at Ruby too, and configured the fileserver to server it but when a Fedora (5 or 6) client sync''s puppetd appears to hang. CentOS clients sync and use the new fact fine. Find attached the fact file and the output from ''puppetd --debug --factsync'' on a FC5 client is below. This is a 0.20.1 client and

Hi, When starting puppet on a new machine, (or when the $vardir/lib is empty) puppet will not run the facts, it will only copy them. on the second time puppet runs, it works quiet well: on the client its defined: [main] pluginsync = true pluginsource = puppet://$server/plugins plugindest = $vardir/lib/puppet factpath = $vardir/lib/puppet/facter [puppetd] factsync = true I also tried with

Hi I''m trying to add extra facts to facter. The puppetd is running on Debian Etch Amd64 as Xen 3.1 guest. I''ve follow the Wiki on adding the facts. First I used relative path in the manifest and added "factsync=true" in client''s puppetd.conf. And then tested it with "puppetd -vt". But no matter what i tried, this error came: File paths must be fully

fact loads: I use facter to search the rsync path and then i write this sudoers line: Cmnd_Alias BACKUPCOMMANDS = /usr/bin/rsync I call puppet like this: puppetd --factsync --server=xxx.yyy.61.131 --waitforcert 60 --test the recipe is: sudoensure_line { sudobackupcommands: ligne => "Cmnd_Alias BACKUPCOMMANDS = $rsyncpath",

I''ve got one node that doesn''t seem to want to load my custom fact. I''ve got ''factsync = true'' in my puppet.conf, and I know I can manually go onto the node and issue a ''puppetd -vt --factsync'' to get it to sync up, but I''d like to know why its not picking this fact up, because this could become problematic. Any tips on

hi, i''m trying to set up my puppetmaster infrastructure with multiple puppetservers behind load balancers in each of our datacenters. i''m using 0.24.6. i''ve read the howto on puppet scalability, and i think i''ve got the ssl config working correct, but i''m noticing that when puppetd is used to build a puppetmaster, some of the files in $vardir/ ssl

May I please ask again for some assistance with the question below? I hope somebody can help me. Thanks, Ed Greenberg -------- Original Message -------- Subject: Re: [Puppet Users] Using custom facts in Puppet Date: Tue, 16 Nov 2010 13:14:06 -0600 From: Ed Greenberg <edg@greenberg.org> Reply-To: puppet-users@googlegroups.com To: puppet-users@googlegroups.com On 11/16/2010 09:33

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 have some facter file to distribute before running puppet on the platform. The problem is : how can i send the facter local.rb file so the rest of the .pp file take into account the new facts created ? ex: i have sudopath as a facter fact and one sudoers class that need that sudopath to work. How do you model that ? it seems puppet would have to rerun after the new local.rb is downloaded

Some time ago i sent to the list a problem i was having with facts on fedora core 6 and wasn''t able to find a solution at that time, but with the release of RHEL5 and CentOS 5 based on fc6 i have hit the problem again. i have written several facts to collect information about a clients network and i am also using the vmware fact from the wiki. i have separated my original fact into

So we run puppetd as a long running ruby process on the hosts. When we update a fact that gets auto sync''d to the host it seems when puppetd wakes up and starts its catalog run it doesn''t re-sync the facts. It you run it standalone it will or if you restart the service then it will do the right thing. Do other people see this? Or have you all gone to running out of cron?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I read that there is several problems about custom facts on this list. However, none is serving my task exactly so I start another. (Topic »custom facts in legacy puppet 0.24.[89]« is the might be the same issue but that gets no answer.) My problem is that I have to serve clients with different versions of puppet. The systems running ubuntu

Hello - Is the following a configuration issue (which is usually the case) or a bug? I''m trying to ensure a local user is present in a NIS environment using the following recipie: class dduck_add { user { "dduckl": ensure => present, uid => 60030, gid => "100", groups =>

I found what the problem is but I am posting this so hopefully people don''t scratch their heads when this happens. I need to be able to configure different things depending whether I''m running on a system that has a Xen kernel or not. I added a fact in /var/lib/puppet/facts/ Facter.add("xen_kernel") do server= `uname -r` if

err: /Settings[top]/Settings[main]/File[/usr/local/.aqadmin/puppet/var/yaml]: Failed to retrieve current state of resource: Could not find user puppet debug: Finishing transaction 75413780 with 2 changes since i put the last version on this test server i cannot launch puppet manualy: mkdir -m 700 -p /usr/local/.aqadmin/puppet/conf/ssl; \ mkdir -m 700 -p /usr/local/.aqadmin/puppet/var/facts; \

I''ve checked out the page on adding custom facts for Facter and I see that there are a number of ways to do this. Is there a preferred method of setting system-wide facts? In this case, I''d like to set a "Location" fact which represents the data centre a server is in. Cheers, James *********************************************************************************

Hi, I want to introduce "Proxmox" as new value in $::operatingsystem. "Proxmox" is based on Debian, so the normal value is currently "Debian". To change that, I just write a custom fact based on the facter fact "operatingsystem" Facter.add(:operatingsystem) do > ... > setcode do > ... > elsif

Hi, I''ve created this fact: require ''facter'' if FileTest.exists?("/etc/ha.d") if `service heartbeat status` =~ /running/ cib = `cibadmin -Q`.grep(/epoch/).to_s epoch = cib.scan(/[0-9]+/).first Facter.add("cib_epoch") do setcode do epoch.to_i + 1 end end end end end I''ve tested it as

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

Is there a recommended way to set $FACTERLIB so that Puppet will be able to access custom facts when running as a Red Hat service? If I export $FACTERLIB=/var/puppet/facts and then run Puppet manually I have no problems, but I''m not sure how I should be setting $FACTERLIB when Puppet is running automatically. Cheers, James