Hi,
Sorry for the late reponse, I'm on holidays, accessing remotely to the
box it gives:
On 07/22/2016 09:05 AM, Apollon Oikonomopoulos wrote:
Control: tags -1 moreinfo
Hi,
On 21:55 Fri 27 May , zulu wrote:
Package: dovecot-imapd
Version: 1:2.2.24-1
Severity: normal
Dear Maintainer,
At machine startup, dovecot-imap fail telling:
May 27 21:37:51 cop21 dovecot[502]: Error: bind(192.168.0.36, 143) failed:
Cannot assign requested address
May 27 21:37:51 cop21 dovecot[502]: Error: service(imap-login):
listen(192.168.0.36, 143) failed: Cannot assign requested address
May 27 21:37:51 cop21 dovecot[502]: Error: bind(192.168.0.36, 993) failed:
Cannot assign requested address
May 27 21:37:51 cop21 dovecot[502]: Error: service(imap-login):
listen(192.168.0.36, 993) failed: Cannot assign requested address
May 27 21:37:51 cop21 dovecot[502]: Fatal: Failed to start listeners
May 27 21:37:51 cop21 dovecot[502]: master: Error: bind(192.168.0.36, 143)
failed: Cannot assign requested address
May 27 21:37:51 cop21 dovecot[502]: master: Error: service(imap-login):
listen(192.168.0.36, 143) failed: Cannot assign requested address
May 27 21:37:51 cop21 dovecot[502]: master: Error: bind(192.168.0.36, 993)
failed: Cannot assign requested address
May 27 21:37:51 cop21 dovecot[502]: master: Error: service(imap-login):
listen(192.168.0.36, 993) failed: Cannot assign requested address
May 27 21:37:51 cop21 dovecot[502]: master: Fatal: Failed to start listeners
May 27 21:37:51 cop21 systemd[1]: dovecot.service: Control process exited,
code=exited status=89
May 27 21:37:51 cop21 systemd[1]: Failed to start Dovecot IMAP/POP3 email
server.
May 27 21:37:51 cop21 systemd[1]: dovecot.service: Unit entered failed state.
May 27 21:37:51 cop21 systemd[1]: dovecot.service: Failed with result
'exit-code'.
manually restarting the service after boot works
I suppose this is related to systemd not starting the network interface before
starting
the dovecot-imap daemon?
Indeed, it looks like 192.168.0.36 has not been assigned (yet?) to the
interface. Do you use /etc/network/interfaces
here is my /etc/network/interfaces (I installed this box, a arm SOC
wandboard with the debian-stretch
installer a few months ago)
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
or systemd-networkd for
interface configuration? Can you provide the contents of
/etc/network/interfaces or /etc/systemd/network/* respectively?
/etc/systemd/network/ is empty
Also,
can you please provide the output of
systemd-analyze dot dovecot.service network.target
$ systemd-analyze dot dovecot.service network.target
digraph systemd {
"nfs-server.service"->"network.target" [color="green"];
"nfs-server.service"->"network.target" [color="black"];
"networking.service"->"network.target" [color="grey66"];
"shutdown.target"->"dovecot.service" [color="green"];
"nmbd.service"->"network.target" [color="green"];
"network-online.target"->"network.target" [color="green"];
"mysql.service"->"network.target" [color="green"];
"multi-user.target"->"dovecot.service" [color="green"];
"multi-user.target"->"dovecot.service" [color="grey66"];
"rpc-statd.service"->"network.target" [color="green"];
"php5-fpm.service"->"network.target" [color="green"];
"rpc-statd-notify.service"->"network.target" [color="green"];
"ssh.service"->"network.target" [color="green"];
"syncserver.service"->"network.target" [color="green"];
"mpd.service"->"network.target" [color="green"];
"systemd-user-sessions.service"->"network.target" [color="green"];
"postfix.service"->"network.target" [color="green"];
"fail2ban.service"->"network.target" [color="green"];
"rc-local.service"->"network.target" [color="green"];
"nginx.service"->"network.target" [color="green"];
"smbd.service"->"network.target" [color="green"];
"dovecot.service"->"local-fs.target" [color="green"];
"dovecot.service"->"basic.target" [color="green"];
"dovecot.service"->"systemd-journald.socket" [color="green"];
"dovecot.service"->"system.slice" [color="green"];
"dovecot.service"->"-.mount" [color="green"];
"dovecot.service"->"network.target" [color="green"];
"dovecot.service"->"sysinit.target" [color="green"];
"dovecot.service"->"system.slice" [color="black"];
"dovecot.service"->"-.mount" [color="black"];
"dovecot.service"->"sysinit.target" [color="black"];
"dovecot.service"->"shutdown.target" [color="red"];
"network.target"->"ifup@eth0.service" [color="green"];
"network.target"->"networking.service" [color="green"];
"network.target"->"network-pre.target" [color="green"];
"network.target"->"shutdown.target" [color="red"];
"nfs-mountd.service"->"network.target" [color="green"];
}
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
-- You probably want to process this output with graphviz' dot tool.
-- Try a shell pipeline like 'systemd-analyze dot | dot -Tsvg >
systemd.svg'!
As a workaround you could either use non-local binds (echo 1 >
/proc/sys/net/ipv4/ip_nonlocal_bind) or bind to the wildcard address
(0.0.0.0) if that's okay with your setup.
ok, I will try that next week.
Thank you very much for support.
Best regards,
Pierre
