Your message dated Wed, 18 Apr 2007 14:06:12 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#405924: Puppet daemons no longer start if PID files can't
be written
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: puppetmaster
Version: 0.18.2-1
Severity: normal
Running the puppetmaster initscript to stop the dæemon doesn't seem to
stop it properly:
# /etc/init.d/puppetmaster stop
Stopping puppet configuration management tool master server.
pond:/etc/puppet/manifests# ps auxw |grep puppet
puppet 16684 0.0 1.1 24356 12176 ? Ssl 17:04 0:00 ruby
/usr/sbin/puppetmasterd --
Micah
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-vserver-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages puppetmaster depends on:
ii facter 1.3.3-1 a library for retrieving facts fro
ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip
ii puppet 0.18.2-1 centralised configuration manageme
ii ruby 1.8.2-1 An interpreter of object-oriented
Versions of packages puppetmaster recommends:
pn rails <none> (no description available)
ii rdoc 1.8.2-1 Generate documentation from ruby s
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.22.0-1
Since just a notfound doesn't seem to do the trick, I'm closing this bug
properly, as per my last comment in this bug log.
- Matt
--- End Message ---
