Web lists-archives.com

Re: Exim4 problem?




On 14/04/2017, songbird <songbird@xxxxxxxxxxx> wrote:
> Charlie wrote:
>> Received this on attempted upgrade:
>>
>> systemctl status exim4.service
>> ● exim4.service - LSB: exim Mail Transport Agent
>>    Loaded: loaded (/etc/init.d/exim4; generated; vendor preset: enabled)
>>    Active: failed (Result: resources) since Fri 2017-04-14 10:24:05
>> AEST; 4min 44s ago
>>      Docs: man:systemd-sysv-generator(8)
>>   Process: 9436 ExecStart=/etc/init.d/exim4 start (code=exited,
>> status=0/SUCCESS)
>>
>> Assume nothing I can do? Something that needs to be done higher up the
>> scale?
>>
>> Can't uninstall or purge exim4 either.
>
>   hmm...
>
>   i'm assuming this is on testing/stretch version?
>
>
>   is there something still running?  as it looks
> like to me that it tried to restart when perhaps
> another instance was running or something like
> that...
>
>   why would you need to uninstall or purge?  did
> you interrupt the upgrade?  are your apt/dpkg
> files inconsistent or showing dependency problems?
>
>   what does systemctl status exim4 say
> after you do a systemctl stop exim4
>
>   ?
>
>   and then a start?
>
>   does it restart?
>
>   check /var/log/apt/term.log
>   and /var/log/dpkg.log
>
>   or does something show up in the systemd
> journal from that timeframe?
>
>   see if there are any messages in those that may
> give an idea of what is going on.
>
>   i had exim4 upgrade go through today too.
> because there were so many processes still
> out of date according to checkrestart i
> rebooted before doing anything else.
>
>   i didn't see any errors in the upgrade or
> in the reboot and my exim4 has been chugging
> along all day.
>
>
>   songbird

Thanks Songbird,

Debian testing is correct.

Posted the top part of what systemctl status exim4 in the first email.

Hadn't done systemctl stop exim4

After systemctl stop exim4 reads like this:

systemctl status exim4
● exim4.service - LSB: exim Mail Transport Agent
   Loaded: loaded (/etc/init.d/exim4; generated; vendor preset: enabled)
   Active: failed (Result: resources) since Fri 2017-04-14 16:22:17
AEST; 1min 41s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1489 ExecStart=/etc/init.d/exim4 start (code=exited,
status=0/SUCCESS)

Apr 14 16:22:13 taogypsy systemd[1]: Starting LSB: exim Mail Transport Agent...
Apr 14 16:22:17 taogypsy exim4[1489]: Starting MTA: exim4.
Apr 14 16:22:17 taogypsy exim4[1489]: ALERT: exim paniclog
/var/log/exim4/paniclog has non-zero size, mail system possibly broken
Apr 14 16:22:17 taogypsy systemd[1]: exim4.service: PID file
/run/exim4/exim.pid not readable (yet?) after start: No such file or
directory
Apr 14 16:22:17 taogypsy systemd[1]: exim4.service: Daemon never wrote
its PID file. Failing.
Apr 14 16:22:17 taogypsy systemd[1]: Failed to start LSB: exim Mail
Transport Agent.
Apr 14 16:22:17 taogypsy systemd[1]: exim4.service: Unit entered failed state.
Apr 14 16:22:17 taogypsy systemd[1]: exim4.service: Failed with result
'resources'.

/var/log/exim4/paniclog says:

2017-04-14 10:13:04 IPv6 socket creation failed: Address family not
supported by protocol

ipv6 has been disabled for the 6 years or so I have had this regularly
upgraded Debian system installed.
/etc/default/grub
GRUB_CMDLINE_LINUX="ipv6.disable=1"

The reason: I have a router that doesn't do ipv6. Also I was told that
satellite, which I am locked into, does not do ipv6 I have never
required it and have never changed it.

Then did: systemctl start exim4

 systemctl start exim4

Job for exim4.service failed because of unavailable resources or
another system error.
See "systemctl status exim4.service" and "journalctl -xe" for details.

journalctl -xe

Apr 14 16:40:15 taogypsy systemd[1]: Starting LSB: exim Mail Transport Agent...
-- Subject: Unit exim4.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit exim4.service has begun starting up.
Apr 14 16:40:17 taogypsy exim4[2209]: Starting MTA: exim4.
Apr 14 16:40:17 taogypsy exim4[2209]: ALERT: exim paniclog
/var/log/exim4/paniclog has non-zero size, mail system possibly broken
Apr 14 16:40:17 taogypsy systemd[1]: exim4.service: PID file
/run/exim4/exim.pid not readable (yet?) after start: No such file or
directory
Apr 14 16:40:17 taogypsy systemd[1]: exim4.service: Daemon never wrote
its PID file. Failing.
Apr 14 16:40:17 taogypsy systemd[1]: Failed to start LSB: exim Mail
Transport Agent.
-- Subject: Unit exim4.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit exim4.service has failed.
-- 
-- The result is failed.
Apr 14 16:40:17 taogypsy systemd[1]: exim4.service: Unit entered failed state.
Apr 14 16:40:17 taogypsy systemd[1]: exim4.service: Failed with result
'resources'.
Apr 14 16:40:29 taogypsy kernel: iptables denied: IN=eth0 OUT=
MAC=01:00:5e:00:00:01:08:86:3b:89:13:c6:08:00 SRC=192.168.2.1
DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1
Apr 14 16:40:32 taogypsy kernel: iptables denied: IN=eth0 OUT=
MAC=01:00:5e:00:00:01:08:86:3b:89:13:c6:08:00 SRC=192.168.2.1
DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1
Apr 14 16:41:29 taogypsy kernel: iptables denied: IN=eth0 OUT=
MAC=01:00:5e:00:00:01:08:86:3b:89:13:c6:08:00 SRC=192.168.2.1
DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1
Apr 14 16:41:32 taogypsy kernel: iptables denied: IN=eth0 OUT=
MAC=01:00:5e:00:00:01:08:86:3b:89:13:c6:08:00 SRC=192.168.2.1
DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1

This is something that has happened after the last upgrade. Won't
upgrade now with this error.

I wanted to remove or purge exim4 if it was a problem. That's why.
Would have reinstalled when it was fixed.

So do I need to use ipv6 now? If so why?