Package: puppet
Version: 0.24.8-2ubuntu4
Severity: normal
Tags: patch
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.
-- System Information:
Debian Release: squeeze/sid
APT prefers karmic-updates
APT policy: (500, 'karmic-updates'), (500, 'karmic-security'), (500, 'karmic')
Architecture: i386 (i686)
Kernel: Linux 2.6.31-20-generic (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages puppet depends on:
ii adduser 3.110ubuntu7 add and remove users and groups
ii facter 1.5.4-1ubuntu1 a library for retrieving facts fro
ii libopenssl-ruby 4.2 OpenSSL interface for Ruby
ii libruby [libxmlrpc-ru 4.2 Libraries necessary to run Ruby 1.
ii libshadow-ruby1.8 1.4.1-8 Interface of shadow password for R
ii libxmlrpc-ruby 4.2 transitional dummy package
ii lsb-base 4.0-0ubuntu5 Linux Standard Base 4.0 init scrip
ii ruby1.8 1.8.7.174-1ubuntu1 Interpreter of object-oriented scr
Versions of packages puppet recommends:
pn libaugeas-ruby1.8 <none> (no description available)
pn rdoc <none> (no description available)
puppet suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
