search for: factsync

...#39;'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 the FC6 is a 0.22.0 and is having the same problem. Without the --factsync the command completes fine. After pressing (ctrl + c) puppetd takes some time to exit, a minute or two, which is odd. I have tested the fact on FC6 &...

...rdir/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 facter 1.5RC1, but no difference there as well. Am I missing something? Thanks, Ohad --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, sen...

...s fact like this : #export $FACTER_test="infof" #facter | grep test test => infof But my fact don''t synchronize with puppet master. I don''t see it in / var/puppet/yaml/clientfile.yaml If I want this works, I''ve need to start puppet like this : #puppetd -vt --factsync but factsync''s setting only works with test''s setting I''ve recently seen that adding custom fact method has changed so I''ve followed the wiki "plugin in module" to create my own fact. I successfully create this fact : # home.rb Facter.add("home...

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

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", before => sudoensure_line["sudoaqbackup"] }...

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

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 how I could go about deb...

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 Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

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 *********************************************************************************

Hello All, I''m using the "Branch Testing" approach documented at https://reductivelabs.com/trac/puppet/wiki/BranchTesting and am seeing an issue with certificates. On all clients, I can run puppetd --masterport=8141 successfully but see the following error when I run against the default (8140) port: err: Could not retrieve configuration: Certificates were not trusted:

...etion. I have attached my facts and would appreciate if someone could test them and possibly shed some light on where puppet is stopping. I find it really interesting that it runs fine when the "-o" (once) command line option is specified. below is the output from `puppetd --debug --factsync` Ben # rm -rf /var/lib/puppet/facts/* # puppetd --debug --trace --factsync /usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world writable dir /home/INTERNAL, mode 041777 /usr/lib/ruby/site_ruby/1.8/facter.rb:420: warning: Insecure world writable dir /home/I...

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 qualified So I used the absolute path and everything was loaded. { "/var/lib/puppet/facts": source => &...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''m just getting started with using Puppet, and from what I''ve seen I really like it. However, I''m trying get started with slighly more advanced things like templates but I''m running into a roadblock with not knowing what built-in variables I have available to me. Is there someplace this is documented?

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?

Is there a condition test to see if a file exists on the puppetmaster? I have about 15 different license files that are loaded on thirteen servers. Not every license goes on every server. I''d like to serve the files only if they exist on the puppet master server. I''m thinking of doing it like this: define install_license($host) {

...e => "/dduck", managehome => true, provider => useradd, password => "{CRYPT}al;ksdjfII" } } But I''m getting the following error (It''s trying to modify the NIS user): # puppetd -vt --verbose --factsync info: Loading fact suse info: Retrieving facts info: Loading fact suse notice: Ignoring cache info: Caching configuration at /var/lib/puppet/localconfig.yaml notice: Starting configuration run err: //global/super_add/User[dduck]/groups: change from dialout,video,super to dialout,dduck,users,video f...

...I did no find any location where the file /var/lib/puppet/lib/facter is defined in all manifest, modules or source of puppet. So my first question is, where do puppet get this file resource from? And why do it means that it has to remove it? (By the way, it seems that this path is only purged when »factsync = true« is in /etc/puppet/puppet.conf.) When I try to ensure that directory to exist it will be deleted on every begin of the run and created at the end. But it will always be empty. An other point that I found in debug log is that sometimes there is an error about not existing (not mounted) /fa...

I''m working with a pretty simple config at the moment to track down some issues I''m seeing with custom facts and plugins. I have factsync = true (default locations) and I have a simple fact in /var/lib/puppet/facts/ (actually it''s David''s netmask plugin) my pp file I''m testing with contains only: notice "netmask: ${netmask}" puppet -v test.pp give sme... info: Loading fact netmask info: Retrievi...

...ppet doesn''t like starting before it can contact the puppetmaster. # Wait up to 30 seconds before continuing. pserver=REDACTED for n in `seq 1 30`; do ping -c 1 $pserver >& /dev/null && break echo -n " $n" sleep 1 done DAEMON_OPTS="--server $pserver --factsync" ===== -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu

I might have the terminology wrong, but how to a give new puppet providers to the puppet clients? I''m thinking a provider is the thing the puppet client uses to implement a task that the master has given it. Am I way off here? Mike B. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.