With systemd 219-4ubuntu6, ifup fails on startup
Bug #1434020 reported by
Michael Marley
on 2015-03-19
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | systemd (Ubuntu) |
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/
| Michael Marley (mamarley) wrote : | #1 |
| Didier Roche (didrocks) wrote : | #2 |
@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) |
| Michael Marley (mamarley) wrote : | #3 |
219-4ubuntu7 fixes the problem. Thanks!
| Changed in systemd (Ubuntu): | |
| status: | New → Fix Released |
| Scott Moser (smoser) wrote : | #4 |
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.


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.