/var/run/network not created soon enough

Bug #367171 reported by Sean McNeil
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

/etc/init.d/networking will fail when /etc/network/interfaces has anything in it that is not auto. This is because ifup/ifdown looks for a file ifstate in /var/run/network and the directory doesn't exist yet. As a temporary solution, I added the following like to /etc/init.d/networking:

[ -d /var/run/network ] || mkdir -p /var/run/network

Without this change and /etc/network/interfaces with something other than auto, startup will hang in nfs-*.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: lsb-base 3.2-20ubuntu4
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: lsb
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
Sean McNeil (sean-mcneil) wrote :
Revision history for this message
ChrisDavaz (cdavaz) wrote :

I can confirm this also happened to me. I had upgrade my 8.04 server to 8.10 and then immediately upgraded to 9.04. The upgrade from 8.10 to 9.04 caused this problem. Creating /var/run/network solves the problem but it needs to happen on every boot. Sean's fix works.

Revision history for this message
wires (jelle-defekt) wrote :

We are running into the same problem when creating a proxmox appliance (± openvz template);
To complicate matters we cannot modify /etc/init.d/networking by hand, because the machine is setup in a script.

See also https://bugs.launchpad.net/ubuntu/+bug/377432

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Thanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

tags: added: jaunty
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
Revision history for this message
michael brenden (mike-brenden) wrote :
Revision history for this message
amichair (amichai2) wrote : Stop dropping cash in the stock market.

Quit losing money in the stock market.
Last year our penny stock picks returned over 600% combined!
Time to make a change in your investment strategies.

Totally Free Newsletter.

--->>> www.awesomebeststocksnow.com

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.