Joerg Herzinger <joerg.herzin...@global2000.at> writes: > Im running a small company (60 clients, 15 Servers and VMs) all managed > by puppet. My clients are Ubuntu, my Servers mostly lenny, some > squeeze. From time to time I find that the lock file isn't removed after > a reboot and puppetd doesn't start.
> This happens mostly with my clients so I guess its problem with > rebooting when puppet is currently running. I would suggest adding > something like > if [ -f /var/lib/puppet/state/puppetdlock ] && [ `pgrep -cx puppet` -eq "0" ] > then > rm /var/lib/puppet/state/puppetdlock > fi > to the start daemon part at the init script to delete the lockfile if it > exists and puppet is not running. We actually currently rely on this behavior so that we can lock Puppet and have it persist across a reboot. It would be nice if there was another way to lock Puppet that wasn't the same as what Puppet does while it's running, since I agree with you that rebooting a system while Puppet is running shouldn't cause Puppet to stay locked after the reboot. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
