Package: dpkg
Version: 1.16.15
My kernel is the wheezy backport 3.16.3-2~bpo70+1
(linux-image-3.16-0.bpo.2-486).
I tried to update rsyslog from 5.8.11-3 to 5.8.11-3+deb7u1 this morning
(Oct 1). Aptitude told me first that rsyslogd couldn't be stopped because
it wasn't running, then that the new rsyslogd couldn't be started because
rsyslogd was already running.
rsyslogd _is_ running, but can't be stopped using either /usr/sbin/service
or /sbin/start-stop-daemon.
$ /usr/sbin/service rsyslog stop
[ ok ] Stopping enhanced syslogd: rsyslogd already stopped.
$ /sbin/start-stop-daemon --stop --verbose --test --pidfile \
/var/run/rsyslogd.pid --exec /usr/sbin/rsyslogd
No /usr/sbin/rsyslogd found running; none killed.
$ /bin/ps uw $(/bin/cat /var/run/rsyslogd.pid)
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 2838 0.0 0.1 30252 2532 ? Sl Sep30 0:01
/usr/sbin/rsyslogd -c5
I noticed that the executable name in /proc is a little funny:
$ /bin/ls -l /proc/$(cat /var/run/rsyslogd.pid)/exe
lrwxrwxrwx 1 root root 0 Sep 30 02:16 /proc/2838/exe ->
/usr/sbin/rsyslogd.dpkg-new (deleted)
The ".dpkg-new" suffix doesn't seem to have been considered by
pid_is_exec() in start-stop-daemon.c. Could my problem be a consequence
of a recent "File cross-renaming support" feature
(http://kernelnewbies.org/Linux_3.15) advertised in Linux 3.15?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
