Bug#805385: systemd: Systemd does not wait for ifup to finish before starting services

[Claudio Zumbo]

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp


2015-11-17 16:50 GMT+01:00 Michael Biebl <biebl at debian.org>:

> Am 17.11.2015 um 16:39 schrieb Claudio:
> > Package: systemd
> > Version: 215-17+deb8u2
> > Severity: important
> >
> > Dear Maintainer,
> >
> > Systemd does not wait for the ifup process to finish before starting the
> services.
> > This is particularly relevant when having multiple interfaces and
> services configured to bind only to a specific ip/interface.
> >
> > Example from journalctl:
> >
> > Nov 17 16:08:16 $my_host ifup[332]: Listening on
> LPF/eth0/e8:9a:8f:73:a9:d4
> > Nov 17 16:08:16 $my_host ifup[332]: Sending on
>  LPF/eth0/e8:9a:8f:73:a9:d4
> > Nov 17 16:08:16 $my_host ifup[332]: Sending on   Socket/fallback
> > Nov 17 16:08:16 $my_host ifup[332]: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 6
> > Nov 17 16:08:16 $my_host minissdpd[367]: Starting UPnP devices daemon:
> MiniSSDPd.
> > Nov 17 16:08:16 $my_host nginx[360]: nginx: [emerg] bind() to
> $public_ip:$port failed (99: Cannot assign requested address)
> >
> > ### later ###
> > Nov 17 16:08:21 $my_host dhclient[340]: bound to $public_ip -- renewal
> in 2147483648 seconds.
>
> Can you attach your /etc/network/interfaces configuration file.
>
> Thanks.
>
>
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151117/c208f499/attachment-0002.html>