Control: forcemerge 921326 921205 On 2019-02-04 Vincent Lefevre <vinc...@vinc17.net> wrote: > Package: exim4-daemon-light > Version: 4.92~RC5-1 > Severity: important
> After the latest upgrade, I got in /var/log/exim4/paniclog: > 2019-02-01 11:15:40 socket bind() to port 25 for address 127.0.0.1 failed: > Address already in use: daemon abandoned [...] > Feb 01 11:10:50 cventin systemd[1]: Reloading. > Feb 01 11:10:50 cventin systemd[1]: Stopping LSB: exim Mail Transport Agent... > Feb 01 11:10:50 cventin exim4[31423]: Stopping MTA:/sbin/start-stop-daemon: > matching only on non-root pidfile /run/exim4/exim.pid is insecure > Feb 01 11:10:50 cventin exim4[31423]: exim4_listener. > Feb 01 11:10:50 cventin systemd[1]: Stopped LSB: exim Mail Transport Agent. > [...] > Feb 01 11:11:07 cventin systemd[1]: Reloading. > Feb 01 11:11:09 cventin systemd[1]: Reloading. > Feb 01 11:11:10 cventin systemd[1]: exim4.service: Found left-over process > 1194 (exim4) in control group while starting unit. Ignoring. > Feb 01 11:11:10 cventin systemd[1]: This usually indicates unclean > termination of a previous run, or service implementation deficiencies. [...] > So, it seems that the issue comes from the fact that the old exim4 > daemon did not stop. Hello, strongly suspect that this is related to other infrastructure (systemd or start-stop-daemon) breaking with exim's init script. It shows up on exim upgrades, because that is basically the only time when exim is regularily shut down and restarted again. Do the warning messages quoted above show up on every stop/start? Is the issue, (service exim4 stop does not stop the daemon) reproducible? See also https://bugs.debian.org/921016 Anyway, I have not seen any indication that 921326 and 921205 are really different. Let's merge them. 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'
