Bug#766943: systemd: server no longer gets networking after switching to systemd

Michael Biebl biebl at debian.org
Mon Oct 27 12:51:44 GMT 2014


Control: reassign -1 ifupdown

Am 27.10.2014 um 06:56 schrieb Christoph Anton Mitterer:
> I did however find what is likely to be the issue:
> Changing "allow-auto eth0" to "allow-hotplug eth0" in /e/n/interfaces...
> and the system did come up again every time (and I did like 5-8 reboots
> with all my tests, also the one with netfilter-persistent above - just
> to make sure that it's no coincidence).
> 
> I switched back to "allow-auto eth0" for verification,... (with several
> tests)... and again it usually didn't get networking.

allow-auto is a synonym for auto.
The ifup at .service unit, as shipped by systemd, only deals with
"allow-hotplug" interfaces.
"auto" interfaces are handled by /etc/init.d/networking, which is
shipped by ifupdown. Therefore re-assigning to ifupdown.

Regarding logs: It would probably be helpful to boot with
systemd.log_level=debug and attach the output of journalctl -alb and
specifically the output of systemctl status networking.service.
-- 
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/20141027/3a586e7b/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list