Your message dated Wed, 01 Aug 2012 15:11:12 +0200
with message-id <1343826672.6414.7.camel@alexander>
and subject line Re: chef: no PID file
has caused the Debian Bug report #584816,
regarding chef: init script expects different PID filename than daemon writes
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
584816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584816
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chef
Version: 0.8.16-4.2
Severity: important
/etc/init.d/chef-client thinks the PID for the daemon is in /var/run/chef-
client.pid
/etc/chef/client.rb writes the PID for the daemon to /var/run/chef/client.pid
Spot the difference?
As a result, "/etc/init.d/chef-client start" will always fail (even though the
daemon is started); "/etc/init.d/chef-client restart" will throw an error and
not restart the daemon as it cannot kill the existing instance; and logrotate
will be unable to tell the daemon to restart when the log is rotated, breaking
logging.
This renders chef-client useless as a daemon, and functional only on the
command line.
-- System Information:
Debian Release: squeeze/sid
APT prefers maverick-updates
APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500,
'maverick-backports'), (500, 'maverick')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 0.8.16-5
Hi,
while trying to fix this bug, I noticed this line in the changelog:
chef (0.8.16-5) unstable; urgency=low
* chef-client.init pidfile location (Closes: #584816)
-- Joshua Timberman <[email protected]> Wed, 09 Jun 2010 02:00:10
-0600
I don't know why this bug hasn't been closed automatically then; but to
be extra sure I checked whether the current version is still buggy:
$ grep '\.pid' chef_10.12.0-1_all/etc/init.d/chef-client
PIDFILE=/var/run/chef/client.pid
$ grep '\.pid' chef_10.12.0-1_all/usr/share/chef/client.rb
pid_file "/var/run/chef/client.pid"
$
As this looks fine to me, I'm closing this bug now. Please feel free to
reopen if necessary!
Best regards
Alexander Kurtz
signature.asc
Description: This is a digitally signed message part
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
