Bug#860317: upgrade to latest stretch version breaks

Andreas Metzler ametzler at bebt.de
Sun Apr 16 09:42:42 UTC 2017


On 2017-04-16 Davide Prina <davide.prina at gmail.com> wrote:
> Package: exim4
> Version: 4.89-1

[...]
> Apr 16 11:06:06 davide systemd[1]: Starting LSB: exim Mail Transport
> Agent...
> Apr 16 11:06:07 davide exim4[3884]: Starting MTA:.
> Apr 16 11:06:07 davide systemd[1]: exim4.service: PID file
> /run/exim4/exim.pid not readable (yet?) after start: No such file or
> directory
> Apr 16 11:06:07 davide systemd[1]: Failed to start LSB: exim Mail Transport
[...]

> $ systemctl status exim4.service
[...]
> apr 16 09:42:10 davide systemd[1]: ^[[0;1;39mexim4.service: Failed with
> result 'resources'.


> $ journalctl -xe
[...]
> --
> -- The result is failed.
> Apr 16 09:41:32 davide systemd[1]: ^[[0;1;39mexim4.service: Unit entered
> failed state.
> Apr 16 09:41:32 davide systemd[1]: ^[[0;1;39mexim4.service: Failed with
> result 'resources'.
[...]

Hello,

this whole bunch of debug info from different commands does not seem to
belong together. The time stamps do not match. (11:06:07 vs 09:42:10 vs
09:41:32)

> $ cat /var/log/exim4/mainlog
[...]
> 2017-04-16 09:39:33 1czemS-0006A8-F3 Completed

Anything in paniclog? Does "exim4 -bV" report any errors? Are you able
to manually start a daemon instance?
update-exim4.conf && exim4 -bd -d

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



More information about the Pkg-exim4-maintainers mailing list