similar to: Could not create PID file: /var/lib/puppet/run/puppetd.pid

Hi all, I''m doing a new install of my puppet server and I''m doing it like: 1.-) adding epel repo: http://fedoraproject.org/wiki/EPEL/FAQ#howtouse 2.-) yum -y install puppet-server 3.-) rm -rf /etc/puppet 4.-) copy my old puppet conf (from puppet-0.24.5 to 0.24.6) mv /etc/puppet.old /etc/puppet 5.-) start puppetmaster: [gridinstall etc]# /etc/init.d/puppetmaster start

I''m suddenly getting the below errors from Rack during puppetd -t (excerpted from the pink HTML output and cleaned for readability): Could not prepare for execution: Got 10 failure(s) while initializing: change from absent to directory failed: Could not set ''directory on ensure: Permission denied - /var/lib/puppet/yaml; change from absent to directory failed: Could not set

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

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

Hi, I am getting the following error on my CentOS clients; err: Could not run Puppet configuration client: Invalid parameter stage at /etc/puppet/manifests/nodes.pp:32 The server is CentOS 5.4 with packages from the epel-puppet repos; # rpm -qa | grep puppet puppet-dashboard-1.0.3-3 puppet-2.6.1-0.3.rc3.el5 puppet-server-2.6.1-0.3.rc3.el5 The clients are; # rpm -qa | grep puppet

Hi all, I am using Puppet to execute an Expect script (http://expect.sourceforge.net) on a client. The Puppet recipe, test.pp, is: exec { ''/root/test.exp'': command => ''/root/test.exp'', logoutput => true } The recipe runs correctly when run using ''puppet --debug --verbose test.pp'': debug: /Stage[main]//Exec[/root/test.exp]:

I just upgraded from 0.23.2-1 on RHEL 4&5 to 0.24.1-1. I used Dlutter''s repository. What a mess I''m in now. Anyway to make a long story short I moved all of the old configs out of the way (/etc/puppet, /var/lib/puppet) and started over with a fresh install. I can''t get puppetd on the server to request a cert. If I do a "puppetd -v --waitforcert 90" the

Hello puppet world, I''m sure this is probably an easy fix, but I cannot seem to resolve this issue. The puppetmaster starts correctly and so does the puppet agent, which receives the update correctly if I restart the puppet agent service manually or during the timed updates; however, if I perform an "puppet kick", it just fails with the following error: Triggering

Hi,,, I have a strange problem when installing puppet client 2.6.3 on a node. I have installed facter-1.3.8-4 and ruby-1.8.6-8. When I start puppetd as a normal user everything behaves normally. A .puppet directory is installed under $HOME and ssl key is installed under $HOME/.puppet/ssl.. I sign the certificat on the puppet master and the client is working fine. However I cannot change

The conf/redhat/client.init script (installed in /etc/init.d) in 0.24.6 has this "status" method: status) status -p "$pidfile" $puppetd RETVAL=$? ;; Unfortunately the ''-p "$pidfile"'' option is available in Red Hat Server 5 but not earlier versions, where it produces an error: $ cat /etc/redhat-release Red Hat Enterprise

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Puppet 0.25.1 - code name "zoot" - is now available. The 0.25.1 release is a maintenance release in the 0.25.x branch. The release is available at: http://reductivelabs.com/downloads/puppet/puppet-0.25.1.tar.gz http://reductivelabs.com/downloads/gems/puppet-0.25.1.gem Please report issues and feedback via the Reductive Labs Redmine site:

Just curious as to the functionality of puppet. Does Puppet ensure that a service is up and running as long as puppet is running? Ie, I want to make sure ssh is always running, if for some reason ssh get''s shut down, does puppet start it back up when it does it''s config sync run? Thanks! --------------------------------- Pinpoint customers who are looking for

Subject basically says it all. Anyone have a good idea of how to get puppetd restarted after installing a updated puppet.conf? Using the Service types obviously doesn''t work since puppet is already running. Is there no, please reload your config on the next run option? I mean there is always some screwing with a cronjob to just restart puppet once and awhile but I dunno I was

So when puppetd crashes/whatever, and a pid file is left behind, SMF in Solaris will try restarting puppet, but fail. And then it sits there restarting it forever. I''m not sure if I can adjust the flap detection in SMF.. it isn''t disabling the service for "restarting too quickly" because it takes so long to start. Probably because I''m NFS-mounting ruby. The

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

Heya, I''m using puppet on Ubuntu (Gutsy/Hardy) and there''s a problem with the default setup of Ubuntu. Ubuntu uses network-manager to start the network in the background, which in turn causes puppet to start before the network is up. Puppet will then exit because it can''t resolve the server name. Currently I "solve" this problem by uninstalling

Does anyone know where I can get the latest puppet, 2.7.1 as RPM''s? The spec file that comes with the puppet 2.7.1 source is broken again, and only version 0.25.5 seems to be available via EPEL, which means that the website''s assertion that you can get puppet as an RPM from there is somewhat untrue. Douglas. -- You received this message because you are subscribed to the

Hi all, I''m working on setting up Puppet to write out my Nagios configs. A few weeks back I inserted a few dummy Nagios checks into my Puppet config, and the Nagios configs were written out properly. I''ve now added loads of Nagios host and service checks like this: @@nagios_service { "check_smtp_${hostname}": check_command =>

I have two puppet master servers in my fledgling puppet infrastructure, a production one and a dev one. I have configured the production one as the authoritative CA, and I have one test agent machine which I''m switching back and forth with the "server" option in /etc/puppet/puppet.conf. When I point the agent at the production server and do puppet agent -t, it sets