Jose Luis Alarcon Sanchez, le dim. 16 nov. 2025 19:47:04 +0100, a ecrit: > El Sun, 16 Nov 2025 13:23:04 +0100 > Samuel Thibault <[email protected]> escribió: > > Jose Luis Alarcon Sanchez, le dim. 16 nov. 2025 12:26:48 +0100, a > > ecrit: > > > El Sat, 15 Nov 2025 21:49:39 +0100 > > > Samuel Thibault <[email protected]> escribió: > > > > Jose Luis Alarcon Sanchez, le sam. 15 nov. 2025 21:30:42 +0100, a > > > > ecrit: > > > > > $ sudo service exim4 restart > > > > > Stopping MTA for restart: exim4_listener. > > > > > Restarting MTA: exim4. > > > > > ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, > > > > > mail system possibly broke > > > > > $ > > > > > > > > > > It's possible to avoid this alert?. Because every time i delete > > > > > the file > > > > > /var/log/exim4/paniclog is re-created very soon, in the next > > > > > time the service exim4 is up. Why happen this?. > > > > > > > > You need to look at its content to see what is getting from. > > > > > > Yesterday the file /var/log/exim4/paniclog was full of messages, > > > but i did a "truncate" over it for let it empty, today, after boot > > > the system, this is the content: > > > > > > 2025-11-16 12:04:16 daemon_notifier_socket bind: Address already in > > > use > > > > So somehow you have something already listening on port 25 or such. > > > > Samuel > > > > Hi, Samuel, and thanks: > > $ telnet localhost 25 > Trying ::1... > Connected to localhost. > Escape character is '^]'. > 220 debian ESMTP Exim 4.99 Sun, 16 Nov 2025 19:31:00 +0100 > ^] > > As you can see, 'telnet' says port 25 is available for connect, > however, every time service exim4 is stopped and/or started add a new > line > daemon_notifier_socket bind: Address already in use > to the /var/log/exim4/paniclog file . I'm baffled by this.
Probably need to check how exim is getting started, whether the start script actually correctly finds out the pid, etc. Samuel
