<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Bitstream Vera Sans">Hello,<br>
<br>
I'm seeing the same bug here now. For some reason did this not
matter in the past, but as of last update does Debian fail to
install exim4 due to the disabled ipv6.<br>
<br>
Why does exim4 all of a sudden require ipv6? I'm not interested in
ipv6 and would appreciate it if Debian didn't make this a
requirement.<br>
<br>
<br>
Setting up exim4-daemon-light (4.89-1) ...<br>
Job for exim4.service failed because of unavailable resources or
another system error.<br>
See "systemctl status exim4.service" and "journalctl -xe" for
details.<br>
invoke-rc.d: initscript exim4, action "start" failed.<br>
● exim4.service - LSB: exim Mail Transport Agent<br>
Loaded: loaded (/etc/init.d/exim4; generated; vendor preset:
enabled)<br>
Active: failed (Result: resources) since Thu 2017-04-13
17:58:50 BST; 5ms ago<br>
Docs: <a class="moz-txt-link-freetext" href="man:systemd-sysv-generator(8)">man:systemd-sysv-generator(8)</a><br>
Process: 4192 ExecStart=/etc/init.d/exim4 start (code=exited,
status=0/SUCCESS)<br>
<br>
Apr 13 17:58:50 debian-linux systemd[1]: Starting LSB: exim Mail
Transport A…...<br>
Apr 13 17:58:50 debian-linux exim4[4192]: Starting MTA: exim4.<br>
Apr 13 17:58:50 debian-linux exim4[4192]: ALERT: exim paniclog
/var/log/exim…ken<br>
Apr 13 17:58:50 debian-linux systemd[1]: exim4.service: PID file
/run/exim4/…ory<br>
Apr 13 17:58:50 debian-linux systemd[1]: exim4.service: Daemon
never wrote i…ng.<br>
Apr 13 17:58:50 debian-linux systemd[1]: Failed to start LSB: exim
Mail Tran…nt.<br>
Apr 13 17:58:50 debian-linux systemd[1]: exim4.service: Unit
entered failed …te.<br>
Apr 13 17:58:50 debian-linux systemd[1]: exim4.service: Failed
with result '…s'.<br>
<br>
...<br>
<br>
2017-04-13 17:58:50 IPv6 socket creation failed: Address family
not supported by<br>
protocol<br>
<br>
Note, this was working in the past and without ipv6. It produced
the error message, but didn't cause an abort of the installation
procedure.<br>
<br>
Could this be a problem of systemd?<br>
<br>
</font>
</body>
</html>