similar to: Problem adding facts ...

Displaying 20 results from an estimated 800 matches similar to: "Problem adding facts ..."

2007 Apr 17
7
Still having factsync trouble ...
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
2006 Aug 31
4
crashes
I just started playing with puppet. Unfortunately, it keeps crashing in a variety of places. I don''t have much experience with Ruby yet, so any tips in tracking down these problems would be appreciated. I''m using the Debian package 0.18.4-1. Here''s the output of a couple runs: www01:/home/cwarden# puppetd --verbose --onetime info: Caching configuration at
2007 Jan 15
7
Yaml Segfaults on ubuntu puppetd client
While running puppetd on a linux client I get the following, the actual spot that the segfault happens varies, but it always happens. This is on ubuntu with the stock apt ruby1.8.4 package. Puppet also installed from apt. Puppet version 0.18.4 It seems very likely that this isnt a bug in puppet per se, but it is tickling a yaml bug (regardless of where it fails, it is always yaml). But I
2007 Nov 11
4
puppetrun fails: "Certificates were not trusted"
Hello all, I''ve tried to run ''puppetrun'', but there seems something unconfigured regarding the certificates. The reverse way (puppetd pulls the config from puppetmasterd) works fine. The namespaceauth.conf on the client (where puppetd runs) is configured as follows: [puppetrunner] allow *.abc.net (also tried the calling host: puppet1.abc.net) But when I call
2007 Nov 26
2
Unable to launch puppetmasterd after installing mongrel
Moving to mongrel as our footprint has grown considerably. Configs worked fine before but for some reason we are unable to start puppet on the new host. Any help would be greatly appreciated. -jeff Centos 5 # ruby -v ruby 1.8.5 (2006-08-25) [i386-linux] # gem list mongrel *** LOCAL GEMS *** mongrel (1.0.1) A small fast HTTP library and server that runs Rails, Camping, Nitro and
2008 Jul 02
3
undefined method `name' for nil:NilClass
I''m a new puppet user. I can''t puppetmasterd to start. I searched this group for the error message I get, but found nothing. Any ideas? [root@puppet ~]# puppetmasterd undefined method `name'' for nil:NilClass Using the --debug switch and ruby''s --debug option shows the following: [root@puppet ~]# puppetmasterd --debug debug: Parsing /etc/puppet/puppet.conf
2007 Nov 17
7
oddness with fileserver, facts and plugins sync
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
2012 Aug 23
1
Puppet Agent VS User
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
2006 Nov 02
6
certificate not trusted
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
2006 Sep 15
4
before everything
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
2006 Sep 29
7
Facts load by puppet -factsync question
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",
2007 Jul 16
5
exec and notify
Are exec resources triggered by notify events supposed to be run once for every event received or only run once per run irregardless of the number of resources that notified it? It seems to me that it gets run twice no matter how many resources triggered it. consider the following class: class dhcp { $prefix = "/usr/local/etc/dhcpd" $dhcpd_conf = "$prefix/dhcpd.conf"
2007 Aug 18
0
Out of memory error while running puppet
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
2007 Aug 19
6
Problem with adding custom facts
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
2007 Aug 28
1
adding facts
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]
2009 Feb 10
7
Lock file /var/lib/puppet/state/puppetdlock
I''m just starting a roll out of Puppet and I''m seeing a problem on maybe 25% of client nodes. The symptoms are that the clients stop updating. In the Puppetmaster log, I''m seeing things like: Feb 9 20:10:23 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9 20:40:41 vs4 puppetmasterd[17942]: Compiled catalog for xxxx in 0.05 seconds Feb 9
2007 Jun 07
17
Puppet/webrick benchmark
We haven''t been able to use mongrel for testing yet, but in order not to waste time, we did some performance testing with 1, 2 and 4 puppetmasterd/webrick processes. Attached is an HTML page (ripped from our wiki - not pretty, but reasonably readable) which describes the method and results. If someone feels like making some nice graphs, that would be great. If not, I''ll try to
2007 May 08
1
Fact sync problems
-----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:
2008 Jan 14
5
Puppetrun denied by puppetd
Hi, I have a Gentoo server running puppetmasterd from Puppet 0.24.1 and a Ubuntu server running puppetd from Puppet 0.23.2. I have added listen=true to the [puppetd] section on the client and run puppetd --debug. I then run puppetrun --debug --host hostname on the puppetmaster server. This is the output I get: Puppetmaster: # puppetrun --debug --host hostname Failed to load ruby LDAP library.
2012 May 25
1
err: Invalid argument - /var/lib/puppet/state/puppetdlock
I have the error err: Invalid argument - /var/lib/puppet/state/ puppetdlock appearing on one of my servers. I have plenty of disk and plenty of inodes. The daemon is not running. I run it manually using /usr/sbin/puppetd --verbose --no-daemonize --onetime --server=xxx --fqdn=yyy There is no file /var/lib/puppet/state/puppetdlock and there is a root writable directory /var/lib/puppet/state