On 14-01-16 23:55, Marc Haber wrote:
On Thu, Jan 14, 2016 at 11:13:34PM +0100, Manuel Bilderbeek wrote:
I have no idea what to investigate and how.
Check whether you have ::1 and/or 127.0.0.1 on lo.
/etc/networks has:
loopback 127.0.0.0
Not sure how to check this in detail, I never had to do this in 15 years
of using Debian.
Stop exim.
Use netstat to see who is listening on port 25.
Interesting:
sonata@23:17:~$ sudo /etc/init.d/exim4 stop
[ ok ] Stopping exim4 (via systemctl): exim4.service.
sonata@23:17:~$ sudo netstat -napt | grep :25
tcp 0 0 127.0.0.1:25 0.0.0.0:*
LISTEN 8769/exim4
Although I stop it, it's still running...?
root 8769 1 0 23:16 ? 00:00:00 /usr/sbin/exim4 -bd -q30m
So, something else also started it?
Looks like it's already started then, outside of systemd... what could
it be?
As I said before, even though it gives that error, it is still able to
send the e-mail that the paniclog has grown. I guess that can be
explained by the fact that there was already an exim4 running indeed.
This is what systemd logging says about my boot today:
$ sudo journalctl --unit=exim4.service
-- Logs begin at vr 2016-01-15 19:02:54 CET, end at vr 2016-01-15
23:12:00 CET. --
jan 15 19:02:56 sonata systemd[1]: Starting LSB: exim Mail Transport
Agent...
jan 15 19:02:56 sonata exim4[537]: Starting MTA: exim4.
jan 15 19:02:56 sonata exim4[537]: ALERT: exim paniclog
/var/log/exim4/paniclog has non-zero size, mail system
jan 15 19:02:56 sonata systemd[1]: Started LSB: exim Mail Transport Agent.
So, it still says it started the service.
Is it possible this has to do with the automatic removal of 'ifupdown'?
It started when installing/upgrading several packages as listed in my
original report.
Check whether this is a legitimate process.
For basic Unix administration skills, you might want to refer to the
relevant -user mailing lists.
Do you really think that's a helpful remark?
--
Kind regards,
Manuel
