Failed to start ifup for eth1 when not using ifupdown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
vivid booted with systemd, and mobo with eth1 used only. Journalctl shows:
networking[443]: * Configuring network interfaces...
apparmor[445]: * Starting AppArmor profiles
console-setup[444]: Loading /etc/console-
console-setup[444]: ...done.
systemd[1]: Started LSB: Set console keymap.
systemd[1]: Started Create Volatile Files and Directories.
systemd[1]: Starting Update UTMP about System Boot/Shutdown...
systemd[1]: Started Update UTMP about System Boot/Shutdown.
networking[443]: ...done.
systemd[1]: Started LSB: Raise network interfaces..
systemd[1]: Starting ifup for eth0...
systemd[1]: Starting ifup for eth1...
systemd[1]: <email address hidden>: control process exited, code=exited status=1
ifdown[617]: /sbin/ifdown: interface eth0 not configured
systemd[1]: <email address hidden>: control process exited, code=exited status=1
systemd[1]: Failed to start ifup for eth0.
systemd[1]: Unit <email address hidden> entered failed state.
systemd[1]: <email address hidden> failed.
ifdown[621]: /sbin/ifdown: interface eth1 not configured
systemd[1]: Failed to start ifup for eth1.
systemd[1]: Unit <email address hidden> entered failed state.
systemd[1]: <email address hidden> failed.
systemd[1]: Stopped LSB: Start NTP daemon.
Is that a conflict with apparmor or a race ? (as i'm getting eth1 stream later)
also get ntpdate errors logged some lines later (but can be the same problem as above)
ntpdate[648]: Can't find host 0.ubuntu.
ntpdate[648]: Can't find host 1.ubuntu.
ntpdate[648]: Can't find host 2.ubuntu.
ntpdate[648]: Can't find host 3.ubuntu.
ntpdate[648]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
ntpdate[648]: no servers can be used, exiting
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 218-5ubuntu2
ProcVersionSign
Uname: Linux 3.19.0-2-generic i686
NonfreeKernelMo
ApportVersion: 2.15.1-0ubuntu2
Architecture: i386
BootDmesg: (Nothing has been logged yet.)
CurrentDesktop: GNOME
Date: Sun Jan 25 11:48:58 2015
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5W DH Deluxe
dmi.product.
dmi.sys.vendor: ASUSTEK COMPUTER INC
Changed in systemd (Ubuntu): | |
status: | Triaged → Fix Committed |
I confirm this, this happens if you use NetworkManager to bring up interfaces instead of ifupdown. Lars, you pointed this out to me at FOSDEM, this is the bug.