similar to: service won't restart puppetd

I''m having this issue where "puppetd -v -o" hangs (won''t return my prompt) when starting a daemon I wrote. If puppetd is running as a daemon a zombie process is created each time puppetd tries to start my daemon. Puppet detects when the daemon is down and starts it just fine. I''m using version 0.22.3 on RHEL 5. Here''s the class. I''ve

OS: FreeBSD 6.2-RELEASE Puppet: 0.22.4 OS: CentOS 5.0 Puppet: 0.23.2 Is it currently not possible for puppetd to upgrade itself (0.22.4 -> 0.23.2)? I tried it, and when puppetd attempted to restart itself (using the init provider), it failed to start back up. Perhaps the init provider needs to close all file handles before executing the rc.d scripts? Additionally, I had puppetd update its

OK, I started down this road a few months ago and got side tracked with project work. I have a class called "install" that I want to use with only machines on one protected subnet. In my site.pp file, among other node entries, I have - node default { install } The class itself - class install { case $domain { "test.example.com": { file:

Hi, From looking at the puppetd --help, there is not currently (at 0.22.4) a method of specifying tags in the puppetd.conf. I was hoping to use this for the following reason: Currently, I use ''noop = true'' in my puppetd.conf, and run ''puppetd --no-noop {tags}'' to install the configurations that I am happy with. This is because I''m currently

On the Configuration refrence page the listen setting is descriped thusly: listen Whether puppetd should listen for connections. If this is true, then by default only the runner server is started, which allows remote authorized and authenticated nodes to connect and trigger puppetd runs. The question is when listen is set to true, does puppetd only listen for remote calls or will it listen for

Hi guys, Unlike what it says in the documentation and the --help output, I can''t seem to get puppetd to use the --server setting. The only way I can get puppetd to work is to include a ''puppet'' alias to the ip of the machine I''m running puppetmasterd on in my hosts file. The strange thing though, is that the logs of my puppetmaster show that it *is* getting

Hi, I have a lot of systems where the puppetd doesn''t do anything .. When I test with puppetd -tv, it s running well, but when it is started as deamon th process do nothing :( How can I debug this ? Vincent May 29 10:07:56 puppetd[6160]: Reopening log files May 29 10:07:56 puppetd[6160]: Starting Puppet client version 0.24.8 May 29 10:07:56 puppet: puppetd startup succeeded May 29

I recently had a working puppet server serving around 4-5 clients. One of the clients needed to be re-built and now only that client cannot connect. puppetca --clean hostname did not work So here is what I did on both the server/client I removed /var/lib/puppet/* Then I restarted the server via puppetmasterd --mkusers --verbose I then connect in via the client with /usr/bin/ruby

This feels like a FAQ and sorry if it is, I failed to find an answer. I''d like some advice on handling backward compatibility between puppetd and puppetmaster. My puppetmaster is at v0.24.5 using Debian Lenny packages. I tried to bring up a puppetd client v0.25.4 (Ubuntu 10.04 packages) but failed to have it download the puppetmaster''s certificate. The puppetd client seemed

I configured my rsync daemon to be restarted when the rsyncd configuration file changes. When the rsync daemon gets restarted by puppet, it listens on the same port puppetd does, so running puppetd again results in an error. The init script for rsync is small and can not be changed from puppet (all variables are declared within the init script and it only searches for the path where the rsync

If you install puppet from the ubuntu 9.04 repositories (apt-get install puppet) it sets up puppet differently than the gem. The differences are obvious from the /etc/puppet/puppet.conf which looks like this [main] logdir=/var/log/puppet vardir=/var/lib/puppet ssldir=/var/lib/puppet/ssl rundir=/var/run/puppet factpath=$vardir/lib/facter pluginsync=true [puppetmasterd]

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

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

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

Guys, I seriously could not find this topic in the documentation. What do you do when you need to force puppetd hosts get the new settings from puppetmasterd? What I found was only sending USR1 signal to the client process in order to make it refresh its configuration from the master. But I find it a bit inconvenient for a large amount of hosts. There is also puppetrun which, if I understand

Hello... What is the last version of puppet that will work with ruby version 1.6.8? I have a few RHEL 3 machines I would like to run puppetd (only the client, not puppetmaster). They will be updated to RHEL 5 fairly soon, so I don''t want to spend a lot of time trying to get a more recent version of ruby on them. thanks /me buys Luke a beer for all his help :) I now have

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

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

(I know more questions... :-)) I know the default for puppetd is to check puppetmasterd every half hour, but my question does each puppetd check at the same time? Or does it depend when puppetd is started or like a cronjob does it run at the 1/2 hour and hour mark? Is there some randomness to the times they run? My point is if they all run at the same time then if you have a large amount of