Bug#791391: NFS mounts and other things fail if DHCP hasn't finished

[Michael Biebl]

Am 04.07.2015 um 11:38 schrieb Daniel Pocock:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: important
> 
> This has been happening on a system that was upgraded from wheezy to jessie
> 
> Sometimes systemd starts the network and then tries to start things that
> depend on the network (e.g. ntpdate, NFS client mounts) before DHCP has
> obtained a lease.
> 
> Sometimes the boot completely stops and asks for root login
> 
> Sometimes it reaches the X login but if a user logs in, it throws them
> out because their home is not mounted.

Is home mounted via NFS?

> journalctl also shows errors from other processes that depend on the
> network.
> 
> 
> Here is the content of /etc/network/interfaces - it was working fine
> with wheezy:
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet dhcp
> #iface eth0 inet6 auto
> iface eth0 inet6 dhcp
>         accept_ra 1
> 
> #allow-hotplug eth1
> #iface eth1 inet dhcp

In the end this is a bug in ifupdown. It should ensure to block until
the network has been configured successfully.

If you change "allow-hotplug" to "auto", does that help?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150704/36e83561/attachment-0002.sig>