similar to: err: Invalid argument - /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

I have three (out of 90) machines with the error: cannot generate tempfile `/tmp/puppet.30616.9'' I have plenty of disk and plenty of inodes. My temp directory is permissioned: drwxrwxrwt 4 root root 20480 2012-05-24 01:33 /tmp I get these for two puppet items on each row. The daemon is not running. I run it manually using /usr/sbin/puppetd --verbose --no-daemonize --onetime

Our puppetmaster runs 0.24.8 on Ubuntu 9.10. Our clients are either Ubuntu 9.10 or Ubuntu 8.04. We''ve just brought up our first Ubuntu 10.04 machine. This machine installs puppetd 0.25.4. The Ubuntu 10.04 machine can''t seem to present it''s certificate request properly. In my masterhttp.log, I see [2010-10-20 13:09:06] 174-143-141-55.static.cloud-ips.com - -

Hello... I wanted to be able to startup an EC2 instance with one command and have a fully functioning server without having to shell into each new instance and configure the bits to allow puppet to finish the configuration. Here are some notes I came up with for bootstrapping an ec2 instance with puppet using Ubuntu 10.04. I left out a lot of things about creating and running custom AIM

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

So I have been trying to run puppet once in my kickstart %post scripts but every time it detaches and daemonizes even though I have explicitly stated otherwise. Am I missing something? # rpm -q puppet puppet-0.24.8-1 # /usr/sbin/puppetd --onetime --no-daemonize --verbose --debug debug: Creating default schedules debug: Failed to load library ''shadow'' for feature

Hi All, I would like to pick your brains as to the best way to configure the below senario within puppet. I am currently configuring puppet for our environment and have seperated development/back office from production through configuring roles for each server to identify them as such. What i need to be able todo is have the production servers only update outside of office hours, but have the

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

is there any way to prevent this timeou ? i tried --configtimeout=600 --filetimeout=600 but this does not changes anything -- Cordialement, Ghislain _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

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"

May I please ask again for some assistance with the question below? I hope somebody can help me. Thanks, Ed Greenberg -------- Original Message -------- Subject: Re: [Puppet Users] Using custom facts in Puppet Date: Tue, 16 Nov 2010 13:14:06 -0600 From: Ed Greenberg <edg@greenberg.org> Reply-To: puppet-users@googlegroups.com To: puppet-users@googlegroups.com On 11/16/2010 09:33

Hi Guys, I am new to the world of puppet. I have successfully configured puppet on centos 6 and am now trying to install puppetb on the same host. After the configuration when I try to run puppetd --test command on the client I get : [root@puppettest ~]# puppetd --test notice: Ignoring --listen on onetime run err: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to

So I''m new to puppet and I''m having a bear of a time just getting a test server going. I installed puppet and the puppet client via yum on CentOS on AWS, so that saved me some time. I followed a few various blog posts about getting everything set up and applying a file, etc. Now I am trying to install a module (puppetlabs/apache) and it''s failing miserably for me. I

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

Hi, I have run into an issue using puppet in an ldap environment and I am wondering if anyone else has run into the same issue. A number of the puppet clients in my testing environment are failing to apply new configurations because the puppet client is getting an ldap error. Currently, I am attempting to push a new bash_profile to my home directory and then set my username/group to then own the

I''m trying to use the 0.20.1 deb from the reductivelabs site and it doesn''t seem to create the /var/lib/puppet directory even though my puppetd.conf file has: vardir=/var/lib/puppet So, when I try the second run, it fails with: Could not lock puppetd: No such file or directory - /var/lib/puppet/state/puppetdlock

So I am beginning the long process of learning puppet... and it seems that I am missing some vital things. My systems are RHEL-4, and i have installed the puppet/facter/puppetmasterd from dlutter@redhat.com''s archive. [root@canopus puppet]# rpm -qa | egrep ''puppet|facter'' | sort facter-1.3.6-1.el4 puppet-0.22.2-1.el4 puppet-server-0.22.2-1.el4 on the client I

HI. Firstly, I''m bound to be doing something utterly basically wrong here, so if I am I apologise. Right now I have a fairly simple setup where the JAR files for a Weblogic-based application server are stored in the file server on my Puppet Master. I run scripts on the client that downloads the files from the file server, puts them in the right place etc etc. All very simple. I am

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

I keep on getting this message: err: Too many open files - /var/lib/puppet/state/state.yaml.tmp Does anybody know what might be causing it? I''m also getting "err: State got corrupted". Everything does seem to be kind of working, but it''s sort of worrying getting these new errors. -- You received this message because you are subscribed to the Google Groups