Your message dated Wed, 15 Oct 2008 15:09:38 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#497638: dirmngr: initscript kills itself for action
"restart"
has caused the Debian Bug report #497638,
regarding dirmngr: initscript kills itself for action "restart"
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.)
--
497638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497638
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: dirmngr
Version: 1.0.1-3
Severity: important
Although this appears similar to bug #495437, initscript kills itself
for action "stop", I think it may have a different cause so I have opened
it as a distinct bug.
The problem seems to be that "start-stop-daemon" is invoked (via lsb-base
"killproc" function) without reference to the pid.
Start-stop-daemon normally detects this and does not kill itself, but
the "restart" action invokes a recursive call of the initscript - which
then gets killed because killproc is defaulting to kill on "--name dirmngr".
This is the reason why logrotate fails with the following error. The
dirmngr postrotate includes a call to the initscript with "try-restart" :
"/etc/cron.daily/logrotate:
/usr/sbin/invoke-rc.d: line 446: 26551 Terminated
"${INITDPREFIX}${INITSCRIPTID}" "${saction}" "$@"
error: error running postrotate script for /var/log/dirmngr.log
run-parts: /etc/cron.daily/logrotate exited with return code 1"
Although I've read the history of #495437 I am not sure of the intended
usage of killproc here, and it is possible the error still lies in
lsb-base, so I haven't ventured a patch for this problem.
I have latest lsb-base, ucf, etc for Lenny.
To generate the following trace, I added "set -x" to /etc/default/dirmngr
nickl:~# /etc/init.d/dirmngr restart
+ . /lib/lsb/init-functions
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ case "$1" in
+ /etc/init.d/dirmngr stop
+ . /lib/lsb/init-functions
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ case "$1" in
+ log_daemon_msg 'Stopping DirMngr' dirmngr
+ '[' -z 'Stopping DirMngr' ']'
+ log_daemon_msg_pre 'Stopping DirMngr' dirmngr
+ :
+ '[' -z dirmngr ']'
+ echo -n 'Stopping DirMngr: dirmngr'
Stopping DirMngr: dirmngr+ log_daemon_msg_post 'Stopping DirMngr' dirmngr
+ :
+ killproc /usr/bin/dirmngr
+ local pidfile sig status base i name_param is_term_sig
+ pidfile=
+ name_param=
+ is_term_sig=no
+ OPTIND=1
+ getopts p: opt
+ shift 0
+ base=dirmngr
+ '[' '!' ']'
+ name_param='--name dirmngr'
++ echo
++ sed -e 's/^-\(.*\)/\1/'
+ sig=
++ echo
++ sed -e 's/^SIG\(.*\)/\1/'
+ sig=
+ '[' -z '' -o '' = 15 -o '' = TERM ']'
+ is_term_sig=yes
+ status=0
+ '[' '!' yes = yes ']'
+ /sbin/start-stop-daemon --stop --quiet --oknodo --name dirmngr
Terminated
nickl:~#
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (850, 'testing'), (600, 'stable'), (3, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dirmngr depends on:
ii adduser 3.108 add and remove users and groups
ii libc6 2.7-13 GNU C Library: Shared libraries
ii libgcrypt11 1.4.1-1 LGPL Crypto library - runtime libr
ii libgpg-error0 1.4-2 library for common error values an
ii libksba8 1.0.3-1 X.509 and CMS support library
ii libldap-2.4-2 2.4.10-3 OpenLDAP libraries
ii libpth20 2.0.7-10 The GNU Portable Threads
ii lsb-base 3.2-19 Linux Standard Base 3.2 init scrip
dirmngr recommends no packages.
dirmngr suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Nick Leverton wrote:
Package: dirmngr
Version: 1.0.1-3
Severity: important
Although this appears similar to bug #495437, initscript kills itself
for action "stop", I think it may have a different cause so I have opened
it as a distinct bug.
The problem seems to be that "start-stop-daemon" is invoked (via lsb-base
"killproc" function) without reference to the pid.
This is fixed in lsb-base 3.2-20.
--- End Message ---
