Bug#810938: exim4-daemon-light: Cannot assign requested address: daemon abandoned at each startup

Adam D. Barratt adam at adam-barratt.org.uk
Sat Jan 16 18:33:53 UTC 2016


On Fri, 2016-01-15 at 23:33 +0100, Manuel Bilderbeek wrote:
> $ sudo journalctl --unit=exim4.service
> -- Logs begin at vr 2016-01-15 19:02:54 CET, end at vr 2016-01-15 
> 23:12:00 CET. --
> jan 15 19:02:56 sonata systemd[1]: Starting LSB: exim Mail Transport 
> Agent...
> jan 15 19:02:56 sonata exim4[537]: Starting MTA: exim4.
> jan 15 19:02:56 sonata exim4[537]: ALERT: exim paniclog 
> /var/log/exim4/paniclog has non-zero size, mail system
> jan 15 19:02:56 sonata systemd[1]: Started LSB: exim Mail Transport Agent.

The two "exim4" lines are coming from the exim4 package. I'm not sure
where the lines referring to "LSB: exim Mail Transport Agent" are coming
from, but afaict it's not the Debian exim package.

That would explain the issue that you're seeing - the "LSB exim" daemon
is starting and claiming port 25; the daemon from the exim4 package is
then starting, failing to claim the port and exiting, leaving the "LSB
exim" daemon still running on port 25.

Checking a couple of jessie systems that are to hand gives what I'd
expect:

adam at mowgli:~$ sudo journalctl --unit=exim4.service
-- Logs begin at Sun 2015-12-20 22:31:54 GMT, end at Sat 2016-01-16 18:32:20 GMT. --
Dec 20 22:32:23 mowgli exim4[1015]: Starting MTA: exim4.

Regards,

Adam



More information about the Pkg-exim4-maintainers mailing list