Failed to start ifup for eth1 when not using ifupdown

Bug #1414426 reported by dino99
12
This bug affects 2 people
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-setup/cached.kmap.gz
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.pool.ntp.org: Name or service not known (-2)
ntpdate[648]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2)
ntpdate[648]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2)
ntpdate[648]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2)
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
ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
Uname: Linux 3.19.0-2-generic i686
NonfreeKernelModules: nvidia
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=/boot/vmlinuz-3.19.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
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.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

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.

summary: - Failed to start ifup for eth1
+ Failed to start ifup for eth1 when not using ifupdown
Changed in systemd (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
status: New → Triaged
Martin Pitt (pitti)
Changed in systemd (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.8 KiB)

This bug was fixed in the package systemd - 218-7ubuntu1

---------------
systemd (218-7ubuntu1) vivid; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
    - Hack to support system-image read-only /etc, and modify files in
      /etc/writable/ instead.
    - Keep our much simpler udev maintainer scripts (all platforms must
      support udev, no debconf).
    - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
      with wait-for-root. Will get applicable to Debian once Debian gets
      wait-for-root in initramfs-tools.
    - initramfs init-bottom: If LVM is installed, settle udev,
      otherwise we get missing LV symlinks. Workaround for LP #1185394.
    - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
      dependencies to "lvm2" which is handled with udev rules in Ubuntu.
    - Provide shutdown fallback for upstart. (LP: #1370329)
    - debian/extra/ifup@.service: Additionally run for "auto" class. We don't
      really support "allow-hotplug" in Ubuntu at the moment, so we need to
      deal with "auto" devices appearing after "/etc/init.d/networking start"
      already ran. (LP: #1374521)
    - ifup@.service: Drop dependency on networking.service (i. e.
      /etc/init.d/networking), and merely ensure that /run/network exists.
      This avoids unnecessary dependencies/waiting during boot and dependency
      cycles if hooks wait for other interfaces to come up (like ifenslave
      with bonding interfaces). (LP: #1414544)
    - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
      Ubuntu we currently keep the setting whether the RTC is in local or UTC
      time in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime.
      (LP: #1377258)
    - Put session scopes into all cgroup controllers. This makes unprivileged
      user LXC containers work under systemd. (LP: #1346734)
    - Lower Breaks: to plymouth version which has the udev inotify fix in
      Ubuntu.
    - Lower libappamor1 dep to the Ubuntu version where it moved to /lib.
    - Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
      This currently fails when being triggered by Jenkins, but is totally
      unreproducible when running this manually on the exact same machine.

    Upgrade fixes, keep until 16.04 LTS release:
    - systemd Conflicts/Replaces/Provides systemd-services.
    - Remove obsolete systemd-logind upstart job.
    - Clean up obsolete /etc/udev/rules.d/README.

systemd (218-7) experimental; urgency=medium

  [ Martin Pitt ]
  * Don't attempt to mount the same swap partition twice through different
    device node aliases. (Closes: #772182, LP: #1399595)
  * logind: handle closing sessions over daemon restarts. (Closes: #759515,
    LP: #1415104)
  * logind: Fix sd_eviocrevoke ioctl call, to make forced input device release
    after log out actually work.
  * debian/rules: Drop obsolete --disable-multi-seat-x and
    --with-firmware-path configure options.
  * debian/udev.README.Debian: Trim the parts which are obsolete, wrong, or
    described in manpages. Only keep the Debian specific bits.
    (Part of #776546)
  * Actually install udev's RE...

Read more...

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.