On Mon, Oct 02, 2023 at 07:12:28PM +0200, Marc Haber wrote: > On Mon, Oct 02, 2023 at 04:55:40PM +0200, Peter Bex wrote: > > I have the same issue on my server. It seems to happen any time the > > exim4 daemon gets restarted. Logs indicate that the process is not shut > > down correctly, leaving a stale daemon listening on the old port, which > > causes the error on startup for the new daemon. > > If this is reproducible,it is probably unrelated to this bug report. > Does the last exim process eventually vanish if you wait a while? It > might stil be doing something, such as waiting for a timeout.
I just waited for 15 minutes after "systemctl stop exim4", and the process is still alive. I can also still connect to port 25, exim is still actively listening on both ipv4 and ipv6 interfaces. Journalctl contains no errors, it just claims it stopped cleanly: Oct 03 09:23:29 scully.more-magic.net systemd[1]: Stopping exim4.service - LSB: exim Mail Transport Agent... Oct 03 09:23:29 scully.more-magic.net exim4[592530]: Stopping MTA:. Oct 03 09:23:29 scully.more-magic.net systemd[1]: exim4.service: Deactivated successfully. Oct 03 09:23:29 scully.more-magic.net systemd[1]: exim4.service: Unit process 575519 (exim4) remains running after unit stopped. Oct 03 09:23:29 scully.more-magic.net systemd[1]: Stopped exim4.service - LSB: exim Mail Transport Agent. Oct 03 09:23:29 scully.more-magic.net systemd[1]: exim4.service: Consumed 4.140s CPU time. It only complains about the left-over process when I start it again: Oct 03 09:38:40 scully.more-magic.net systemd[1]: exim4.service: Found left-over process 575519 (exim4) in control group while starting unit. Ignoring. Oct 03 09:38:40 scully.more-magic.net systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Oct 03 09:38:40 scully.more-magic.net systemd[1]: Starting exim4.service - LSB: exim Mail Transport Agent... Oct 03 09:38:40 scully.more-magic.net exim4[592898]: Starting MTA: exim4. Oct 03 09:38:40 scully.more-magic.net systemd[1]: Started exim4.service - LSB: exim Mail Transport Agent. This is also usually when exim itself notices and creates the paniclog entry. Strangely enough, it didn't do that this time... Cheers, Peter
signature.asc
Description: PGP signature
