similar to: Fact sync problems

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

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

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

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

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''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]

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

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

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

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

Hi, I wonder why the puppet agent on the server itself will not run: ---snip--- # puppet agent --test Error: Could not run Puppet configuration client: Puppet::Node does not respond to from_s; can not intern instances from text/plain Error: Could not run: can''t convert Puppet::Util::Log into Integer ---pins--- whereas the client on a test box tells me: ---snip--- # puppet agent --test

When I deploy a module I wrote with couple of custom facts, those facts do not show up in factor. But when I point FACTORLIB to the directory with those factor, they work just fine. I am running a masterless puppet version 2.7.22 and factor 1.7.1 The module structure looks like so: -license ---lib -----facter -------license.rb -------hardware_serial.rb -----puppet Any idea what is causing

Hi all, I''m setting up puppetdb to for storing facts et cetera. I installed puppetdb-1.3.0-1.el6.noarch.rpm on my puppetdb.local host (which is puppetized). This seems to work, service starts :). When I edit the settings on my puppetmaster (puppet.local), something goes wrong. I am following the guide [1]. I put the settings (storeconfigs = true, storeconfigs_backend=puppetdb) on my

Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,

No problem installing open puppet and using it. patterns run aok. when trying to use the installer for pe, on the puppetmaster, installs ok. when trying to use the installer for pe, on the puppet agent, installs ok but no cert sent as shown by puppet cert list on puppetmaster. also puppet agent --test on puppet agent shows err: could not retrieve catalog from remote server: error 400 on

Hello, I have configured puppet and puppetdb (storeconfig) with postgresql and the service run and the collecting are good for example: I can make query with the next command and responds ok . [.........................] [root@master]# curl -X GET -H ''Accept: application/json'' http://127.0.0.1:8080/v2/facts --data-urlencode ''query=["=", "name",

Hello everyone... I have configured the puppetmaster to use Apache/Passenger. However, executing a configprint (puppet --configprint all) from either the puppetmaster or an agent shows servertype = Webbrick Has anyone else seen this? What do I need to do to correct this? Thanks! JA -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

(I''m emailing the list, rather than direct.) Adnet Ghislain wrote: > Hello, > > More on my deployment, i have an issue where the fact sometime 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

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?