similar to: before everything

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

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

Hello, I try to install puppet on freebsd 6.X. All is well but i cannot get the certificte to install and be recognized. I run .19.3. I run the puppetd --test --waitforcert 60 then sign and then i got: err: No certificate; running with reduced functionality. info: Creating a new SSL key at /usr/local/.aqadmin/puppet/conf/ssl/private_keys/xxxxxxxxxxxxxx.pem info: Creating a new certificate

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; \

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

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

Hello, I have a strange problem this nigth that i cannot solve, perhaps you can help me understand what is wrong. I have a file type that upload a directory into my servers. Inside this uploaded directory i create subdirectory and files on my own (directly on the target host). The problem is that when puppet comes back to the directory it spills out this error: err:

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

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

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction

In my puppet client I have puppet.conf defined puppet server as mypuppet server = mypuppet.example.net Not sure why the puppet client puppet-test is still sending these noises to the syslog Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error] Could not find server : getaddrinfo: node name or service name not known Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911

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

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

Hi all, I''m getting very close to the next release of Puppet, and I need help making sure it''s as bug-free as possible. The major changes in this version relate to Rails (and thus resource collect/export) and transaction internals. If you are currently using Puppet''s rails support, you''re going to have to migrate manually, unfortunately (or just

I''ve added some custom facts to my Puppet setup but they aren''t being displayed by facter. I''ve tested them and they work correctly when run manually (and I''ve also tried a number of those listed on the wiki) but they aren''t included in facter''s output. I am using the default settings for factdest and factpath and the facts are being copied

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

Hello, I''m a little confused how to configure the puppermaster and puppetd to add a new fact. I''ve followed this tutorial http://reductivelabs.com/trac/puppet/wiki/AddingFacts but I''m with doubts about the factsource. In my puppetmaster I have the new fact in /etc/puppet/facts directory. fileserver.conf (on puppetmaster server): [files] path /etc/puppet/files [facts]

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

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

I''m having an issue with the default puppet.conf distributed with puppet 2.6.4 (FreeBSD port). I''ve reproduced the problem with a completely fresh install on a completely fresh OS in a VM. Under these conditions, running puppetmaster with no config is fine, but simply moving the puppet.conf-dist file to puppet.conf causes the following errors on console: Performing sanity