Bug#854896: exim4: Dpkg fails to upgrade exim4 on debian sid.

felipe zeden at riseup.net
Sun Feb 12 14:45:30 UTC 2017


Hi,


> On 11-02-2017 23:25, Vincent Lefevre wrote:
>> fev 11 13:57:11 fx8350 exim4[21370]: ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size…broken
>
> There may be interesting information in this file.
>

This is the output:

$ sudo cat /var/log/exim4/paniclog
2017-02-10 11:20:36 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-10 22:20:48 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 10:57:38 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 11:00:36 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 11:05:42 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 11:13:31 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 11:19:12 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 11:42:11 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 11:51:45 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 13:39:54 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 13:54:40 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 14:01:41 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 14:14:31 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 17:27:53 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 20:56:30 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-11 21:32:06 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2017-02-12 12:21:45 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned


>> fev 11 13:57:11 fx8350 systemd[1]: exim4.service: PID file /var/run/exim4/exim.pid not readable (y…rectory
> I would be interested what this line reads in full, and whether /var/run is a proper link to /run, and whether
/run/exim4 exists.

Sorry for the truncated line:
fev 12 12:26:49 fx8350 systemd[1]: exim4.service: PID file /var/run/exim4/exim.pid not readable (yet?) after start: No
such file or directory


$ ll /var/run
lrwxrwxrwx 1 root root 4 set 12  2014 /var/run -> /run


$ ll /run
drwxr-x---  2 Debian-exim Debian-exim   40 fev 12 12:17 exim4


$ sudo journalctl -xe
fev 12 12:26:48 fx8350 systemd[1]: Starting LSB: exim Mail Transport Agent...
-- Subject: Unit exim4.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit exim4.service has begun starting up.
fev 12 12:26:49 fx8350 exim4[3606]: Starting MTA: exim4.
fev 12 12:26:49 fx8350 exim4[3606]: ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail system possibly
broken
fev 12 12:26:49 fx8350 systemd[1]: exim4.service: PID file /var/run/exim4/exim.pid not readable (yet?) after start: No
such file or directory
fev 12 12:27:29 fx8350 ntpd[822]: 52.67.60.175 local addr 10.1.1.2 -> <null>
fev 12 12:28:38 fx8350 ntpd[822]: 52.67.63.45 local addr 10.1.1.2 -> <null>
fev 12 12:28:41 fx8350 ntpd[822]: 192.99.2.8 local addr 10.1.1.2 -> <null>
fev 12 12:28:41 fx8350 ntpd[822]: 192.155.90.13 local addr 10.1.1.2 -> <null>
fev 12 12:29:19 fx8350 ntpd[822]: 200.192.232.8 local addr 10.1.1.2 -> <null>
fev 12 12:29:43 fx8350 ntpd[822]: 52.67.171.238 local addr 10.1.1.2 -> <null>
fev 12 12:30:01 fx8350 CRON[4122]: pam_unix(cron:session): session opened for user felipe by (uid=0)
fev 12 12:30:06 fx8350 CRON[4122]: pam_unix(cron:session): session closed for user felipe
fev 12 12:31:19 fx8350 systemd[1]: exim4.service: Daemon never wrote its PID file. Failing.
fev 12 12:31:19 fx8350 systemd[1]: Failed to start LSB: exim Mail Transport Agent.
-- Subject: Unit exim4.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit exim4.service has failed.
-- 
-- The result is failed.
fev 12 12:31:19 fx8350 systemd[1]: exim4.service: Unit entered failed state.
fev 12 12:31:19 fx8350 systemd[1]: exim4.service: Failed with result 'resources'.
fev 12 12:31:21 fx8350 sudo[2294]: pam_unix(sudo:session): session closed for user root
fev 12 12:32:26 fx8350 systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
-- Defined-By: systemd



More information about the Pkg-exim4-maintainers mailing list