Re: [exim] Debian-Bug not stopping exim

Top Page

Reply to this message
Author: Evgeniy Berdnikov
To: exim-users
Subject: Re: [exim] Debian-Bug not stopping exim
On Wed, Feb 06, 2019 at 11:03:34PM +0100, Klaus Ethgen via Exim-users wrote:
> But, and that did change somewhen in the past months, start-stop-daemon
> seems to _not_ stop exim with that anymore. Both definitions above did
> not change for longer times. Just start-stop-daemon did.
> I checked, before I do a "/etc/init.d/exim4 stop", the pid file contains
> the correct PID of the exim process. And the rights are:
>    ~> ll -a /run/exim4
>    insgesamt 4,0K
>    drwxr-x---  2 Debian-exim Debian-exim  60 Feb  6 09:21 .
>    drwxr-xr-x 27 root        root        980 Feb  6 10:14 ..
>    -rw-r--r--  1 root        Debian-exim   6 Feb  6 09:21

> After the stop, exim is still running but the pid file is gone.
> And I get the message on the console:
>    ~> /etc/init.d/exim4 stop
>    [....] Stopping MTA:/sbin/start-stop-daemon: matching only on non-root pidfile /run/exim4/ is insecure
>    [ ok 4_listener.

The message "matching only on non-root pid file /run/exim4/
is insecure" is very strange in your context, isn't it?
Strange because file is owned by root.

I have no such message on stop with my Debian systems. And never seen,
while Exims under Debians are running for years. For most hosts now
start-stop-daemon is from dpkg-1.19.2 (i386 and amd64 are used).

So you have to study why start-stop-daemon ejects this strange message.
BTW, its binary does not contain strings with "matching only", maybe
some old versions of start-stop-daemon have relevant code.

Note that problem is not located so far. Maybe start-stop-daemon fails
to send signal to Exim, maybe Exim receives signal, but ignores.
So first step should be running strace on both to locate the fault.

> So there was a bug introduced in the last few weeks in start-stop-daemon
> that I have to find a way around. The current situation is not
> acceptable.

History of updates for Debian packages is stored in /var/log/dpkg.log.

Before submitting bug reports you have better to compare behaviour
of you system versus clean and fresh Debian. Otherwise you can waste
your time discussing upgrade problems.
Eugene Berdnikov