With systemd 219-4ubuntu6, ifup fails on startup

Bug #1434020 reported by Michael Marley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Released
Undecided
Scott Moser

Bug Description

After updating to systemd 219-4ubuntu6, the ifup services for both network cards in my system fail to start with "/sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory". My networks still come up because I am using network-manager, but without network-manager, it seems the network would not come up.

Revision history for this message
Michael Marley (mamarley) wrote :

The problem seems to be that ifup@.service currently isn't sequenced to run after systemd-tmpfiles-setup.service (both of those are configured to run after local-fs.target). If I override ifup@.service and set "After=local-fs.target network-pre.target systemd-tmpfiles-setup.service", it starts properly.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

@Michael: did you try with 219-4ubuntu7? I know that scott did some more fixes to the network functionalities following his previous patch.

@Scott: mind having a look?

Changed in systemd (Ubuntu):
assignee: nobody → Scott Moser (smoser)
Revision history for this message
Michael Marley (mamarley) wrote :

219-4ubuntu7 fixes the problem. Thanks!

Changed in systemd (Ubuntu):
status: New → Fix Released
Revision history for this message
Scott Moser (smoser) wrote :

Hi,
  I dont actually know why 219-4ubuntu7 would fix the problem.
  I think it probably just change timing of a very small race window.

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.