Ubuntu
systemd package

  1. Bug #1374521
  2. Comment #7

Comment 7 for bug 1374521

Revision history for this message
Martin Pitt (pitti) wrote : Re: auto interfaces do not come up with r/o images

Further debugging: /etc/init.d/networking just gets redirected through /lib/lsb/init-functions.d/40-systemd. This gets closer to the problem:

networking.service - LSB: Raise network interfaces.
   Loaded: loaded (/etc/init.d/networking)
  Drop-In: /run/systemd/generator/networking.service.d
           `-50-insserv.conf-$network.conf
   Active: active (exited) since Mon 2014-09-29 13:15:31 UTC; 41s ago
  Process: 405 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS)

Sep 29 13:15:31 localhost.localdomain dhclient[486]: For info, please visit https://www.isc.org/software/dhcp/
Sep 29 13:15:31 localhost.localdomain networking[405]: For info, please visit https://www.isc.org/software/dhcp/
Sep 29 13:15:31 localhost.localdomain dhclient[486]:
Sep 29 13:15:31 localhost.localdomain networking[405]: Cannot find device "eth0"
Sep 29 13:15:31 localhost.localdomain networking[405]: Error getting hardware address for "eth0": No such device
Sep 29 13:15:31 localhost.localdomain networking[405]: Failed to bring up eth0.
Sep 29 13:15:31 localhost.localdomain networking[405]: ...done.
Sep 29 13:15:31 localhost.localdomain systemd[1]: Started LSB: Raise network interfaces..
Sep 29 13:15:31 localhost.localdomain ntpdate[566]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Sep 29 13:15:31 localhost.localdomain ntpdate[566]: no servers can be used, exiting

Running "sudo systemctl start networking.service" manually works, so somehow this is running at a time when there's no eth0 yet. This also explains why adding --allow=auto to the job works, as then it gets re-run when eth0 is detected.