search for: fact_collector

...e request for xxxxxxxxxxxxxxxxx info: Requesting certificate warning: peer certificate won''t be verified in this SSL session notice: Did not receive certificate info: Requesting certificate warning: peer certificate won''t be verified in this SSL session info: Retrieving facts err: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts/source: Could not describe /facts: Certificates were not trusted: certificate verify failed notice: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts: source puppet://xxxxxxxxxxxx/facts does not exist err: fact_collector/file=/usr/local/.aqadmin/p...

...work::Client::File: defining fileserver.describe debug: Puppet::Network::Client::File: defining fileserver.list debug: Puppet::Network::Client::File: defining fileserver.retrieve info: Retrieving facts debug: Calling fileserver.list debug: Calling fileserver.describe debug: /fact_collector/File[/var/lib/puppet/facts]: Changing checksum debug: /fact_collector/File[/var/lib/puppet/facts]: 1 change(s) debug: /fact_collector/File[/var/lib/puppet/facts]/checksum: setting time (currently {time}Tue Apr 17 14:30:08 +1000 2007) debug: /fact_collector/File[/var/lib/puppet/facts...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I''m having a problem pulling down new facts. On one of my nodes I''m getting this error: err: fact_collector/file=/var/lib/puppet/facts/source: Could not describe /facts: Fileserver module ''facts'' not mounted notice: fact_collector/file=/var/lib/puppet/facts: source puppet://puppet/facts does not exist err: fact_collector/file=/var/lib/puppet/facts/source: Could not describe /facts: File...

Hi all, I''ve done as much bug-fixing as I''m going to be able to do in 0.24.2, I think, so please test the current code if you can. I made some unfortunately significant changes today, in order to try to remove any shared objects in the file server, which will hopefully solve the file corruption issues, plus some very strange issues resulting from renaming

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",

...setcode "no" end end You already may see what the problem is # /usr/sbin/puppetd -vt --factsync warning: Individual config files are deprecated; remove /etc/puppet/puppetd.conf and use puppet.conf info: Loading fact xen_kernel info: Retrieving facts err: /fact_collector/File[/var/lib/puppet/facts]: Failed to generate additional resources during transaction: Cannot access mount[facts] err: /fact_collector/File[/var/lib/puppet/facts]/source: Could not describe /facts: Cannot access mount[facts] info: /fact_collector/File[/var/lib/puppet/facts]/source: No specified...

...ishing transaction -606727528 with 2 changes notice: Starting Puppet client version 0.20.1 info: Creating PID file to /var/run/puppet/puppetd.pid debug: getting config debug: Loaded state in 0.00 seconds info: Retrieving facts debug: Calling fileserver.describe debug: Calling fileserver.list debug: fact_collector/file=/var/lib/puppet/facts: Creating checksum {time}Wed Jan 10 17:35:21 +1100 2007 debug: Calling fileserver.describe debug: Calling fileserver.list debug: fact_collector/file=/var/lib/puppet/facts/home.rb/checksum: Initializing checksum hash debug: fact_collector/file=/var/lib/puppet/facts/home....

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

...t 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: Retrieving facts err: /fact_collector/File[/var/lib/puppet/client-facts]: Failed to generate additional resources during transaction: Fileserver module ''facts'' not mounted err: /fact_collector/File[/var/lib/puppet/client-facts]/source: Could not describe /facts: Fileserver module ''facts'' not mounted...

...uppet/facts directory. fileserver.conf (on puppetmaster server): [files] path /etc/puppet/files [facts] path /etc/puppet/facts puppet.conf (on client): [puppetd] logdir=/var/log/puppet vardir=/var/lib/puppet rundir=/var/run server=my_server factsync=true This is the error on the client: err: fact_collector/file=/var/lib/puppet/facts/source: Could not describe /facts: Cannot access mount[facts] notice: fact_collector/file=/var/lib/puppet/facts: source puppet://my_server/facts does not exist This is the error on the server: info: mount[facts]: defaulting to no access for puppetd_client warning: mount[...

...e does > not load and it seems that they do not work and as i rely on facts in it > ll fails: > > Oct 6 02:54:18 oiseadmin puppetd[42243]: Could not call > fileserver.list: #<Errno::ECONNRESET: Connection reset by peer> > Oct 6 02:54:18 oiseadmin puppetd[42243]: > (fact_collector/file=/usr/local/.aqadmin/puppet/var/facts) Failed to > retrieve current state: Connection reset by peer > Oct 6 02:55:44 oiseadmin puppetd[42243]: Starting configuration run > Oct 6 03:00:04 oiseadmin puppetd[42243]: Could not call > fileserver.describe: #<Errno::ECONNRESET: Conn...

...ed to "/var/lib/puppet/facts"! All three facts I''m trying to install is taken from the wiki, so they should fine. I hope someone can see, what I''ve missed. Thanks /Lars -- Output from puppetd -vt --factsync --- ~# puppetd -vt --factsync info: Retrieving facts notice: fact_collector/file=/var/lib/puppet/facts/checksum:.... info: Loading fact ifname info: Loading fact virtual info: Loading fact home info: Caching configuration at /etc/puppet/localconfig.yaml notice: Finished configuration run in 5.29 seconds ----------------------------------------------------