Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
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
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
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. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
Dear maintainer, 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. After an update just now: Oct 02 16:46:37 scully.more-magic.net systemd[1]: Stopping exim4.service - LSB: exim Mail Transport Agent... Oct 02 16:46:37 scully.more-magic.net exim4[574161]: Stopping MTA:. Oct 02 16:46:37 scully.more-magic.net systemd[1]: exim4.service: Deactivated successfully. Oct 02 16:46:37 scully.more-magic.net systemd[1]: exim4.service: Unit process 701 (exim4) remains running after unit stopped. Oct 02 16:46:37 scully.more-magic.net systemd[1]: Stopped exim4.service - LSB: exim Mail Transport Agent. Oct 02 16:46:37 scully.more-magic.net systemd[1]: exim4.service: Consumed 2min 17.056s CPU time. Oct 02 16:46:40 scully.more-magic.net systemd[1]: exim4.service: Found left-over process 701 (exim4) in control group while starting unit. Ignoring. Oct 02 16:46:40 scully.more-magic.net systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Oct 02 16:46:40 scully.more-magic.net systemd[1]: Starting exim4.service - LSB: exim Mail Transport Agent... Oct 02 16:46:40 scully.more-magic.net exim4[574712]: Starting MTA: exim4. Oct 02 16:46:40 scully.more-magic.net systemd[1]: Started exim4.service - LSB: exim Mail Transport Agent. In /var/log/exim4/paniclog: 2023-10-02 16:51:10 socket bind() to port 25 for address (any IPv6) failed: Address already in use: daemon abandoned If I use systemctl to stop the daemon, it leaves an exim4 process running. Manually calling "pkill exim4" and then using systemctl to start exim4 resolves the issue (until the next restart). I thought it was ipv6-related, but if I see message #5 in this bug it seems that this is not necessarily the case. Perhaps it is caused by having exim listen on multiple interfaces (ipv4 and ipv6), or maybe it's a red herring? Anyway, I hope this helps debug the problem further! Regards, Peter Bex signature.asc Description: PGP signature
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 在 2023-04-09星期日的 15:14 +0200，Marc Haber写道： > exim paniclog Thank you. paniclog removed -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEMNkEN5bfqrr/ykm8AZx+p0DYjwsFAmQ3+poACgkQAZx+p0DY jwvm/gv8C7MODD8ocExFJ6Yyoz7tHLpK+f/wYxQelb6GHuh6nbC3dadxI8SEridg PDT8/9h5HfYYt7KsxsJOLmhDswjpnOur88QoK+U4673uAk/x+JOy4Tr4XyKFZfiu wYSsNJBzs/1qcGLIj6umkqFezsJ4Na0ICG9C3/ZxUpRnD/Uax/l2WOV3BCG9Sd9X eHxCkssnB56bHNbqNZDNO/34mY6+qllNUOsonojWW9zBAIK2x961EifgIibs8f/k Fp3397nGgqCaaveg3klPp+EHqJNEkmBXDFS3v9Vzq7FUYFkxrq97ZAAPOc14Gq4v 0N+D8vhwFCFpzCfgsK1iQXPlh4MqRI7UnbACS1TUijBJ52nG1n01EBUuL+t2fJox mryRj9QCG0Wm3fZTx4YPXwBiPToBZMqRGGHYZ9cf/7pOUp42XRQXwIA11m2hYfce 7PpAet01JBXfECIEenTgN1KSpPEj0ZoaW5KQd5wmaFPax97UqIFYZSoLcPYNbHDJ XVHa2MCi =NhWB -END PGP SIGNATURE-
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
On Sun, Apr 09, 2023 at 08:43:23PM +0800, Wensheng Xie wrote: > > Actually that does seem to be relevant at all, the message is from > > March > > 17. > > Each time I start the machine, my mailbox will have at least one such > email. This is expected and intended behavior, you need to manually move the paniclog away for the message to go away. See README.Debian 2.5.1 Andreas, we should probably include this reference into the mail message. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
> > Actually that does seem to be relevant at all, the message is from > March > 17. Each time I start the machine, my mailbox will have at least one such email. > > What do the configuration files look like (especially > /etc/exim4/update-exim4.conf.conf)? What doi the log files show for > which mail? > I attach the conf file and the email. # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='internet' dc_other_hostnames='lenovo.debian.lenovo ; mail.debian.lenovo' dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='mail.debian.lenovo' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='maildir_home' exim_paniclog_on_lenovo_has_non-zero_size.mbox Description: application/mbox signature.asc Description: This is a digitally signed message part
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
Control: tags -1 moreinfo Control: severity -1 normal On 2023-04-06 Wensheng Xie wrote: > Package: exim4 > Severity: important > X-Debbugs-Cc: none, Wensheng Xie [...] >* What exactly did you do (or not do) that was effective (or > ineffective)? > Sending/receiving emails to local users is ok; > LAN users receiving emails from server PC is ok, but cannot send > emails. >* What was the outcome of this action? > exim paniclog /var/log/exim4/paniclog on lenovo has non-zero size, mail > system might be broken. Up to 10 lines are quoted below. > 2023-03-17 23:26:36 daemon_notifier_socket bind: Address already in use ^ [...] Actually that does seem to be relevant at all, the message is from March 17. What do the configuration files look like (especially /etc/exim4/update-exim4.conf.conf)? What doi the log files show for which mail? cu Andreas
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
On 2023-04-06 Wensheng Xie wrote: > Package: exim4 > Severity: important > X-Debbugs-Cc: none, Wensheng Xie [...] >* What exactly did you do (or not do) that was effective (or > ineffective)? > Sending/receiving emails to local users is ok; > LAN users receiving emails from server PC is ok, but cannot send > emails. >* What was the outcome of this action? > exim paniclog /var/log/exim4/paniclog on lenovo has non-zero size, mail > system might be broken. Up to 10 lines are quoted below. > 2023-03-17 23:26:36 daemon_notifier_socket bind: Address already in use > 2023-03-17 23:31:06 socket bind() to port 25 for address 127.0.0.1 failed: > Address already in use: daemon abandoned > 2023-03-17 23:31:34 socket bind() to port 25 for address 127.0.0.1 failed: > Address already in use: daemon abandoned >* What outcome did you expect instead? > There is no error, and emails for LAN users via port 25 should work. Looks like there is another program liestening on port 25. cu Andreas
Bug#1034015: exim4: exim paniclog on lenovo has non-zero size
Package: exim4 Severity: important X-Debbugs-Cc: none, Wensheng Xie Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installed exim4 and setup localhost as mailserver * What exactly did you do (or not do) that was effective (or ineffective)? Sending/receiving emails to local users is ok; LAN users receiving emails from server PC is ok, but cannot send emails. * What was the outcome of this action? exim paniclog /var/log/exim4/paniclog on lenovo has non-zero size, mail system might be broken. Up to 10 lines are quoted below. 2023-03-17 23:26:36 daemon_notifier_socket bind: Address already in use 2023-03-17 23:31:06 socket bind() to port 25 for address 127.0.0.1 failed: Address already in use: daemon abandoned 2023-03-17 23:31:34 socket bind() to port 25 for address 127.0.0.1 failed: Address already in use: daemon abandoned * What outcome did you expect instead? There is no error, and emails for LAN users via port 25 should work. *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-20-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:zh Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
