[Bug 377432] Re: ifdown: failed to open statefile /var/run/network/ifstate:

norbie 377432 at bugs.launchpad.net
Sat Dec 10 05:26:33 UTC 2011


I have seen in many previous posts that the BUG was fixed and the issue was closed. In the contrary this one here seems to be relatively fresh/alive and does not suggest that BUG was killed. Although, relatively recent, I have encountered the same problem that exists now for more than 5 years.
After reboot the /var/run/network directory disappears and has to be recreated in order to get networking up and running.  I read about a directory /var/run under root and seems to cause all kinds of problems if incorrect or missing.
In the same token, I believe that it might be very possible that it is related to a particular piece of hardware that is either not captured by the driver or the OS, but may work flawless with other hardware.
Just a thought, and sounds far fetched, because why did it work before the distro upgrade?

Cheer,
Norbert

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/377432

Title:
  ifdown: failed to open statefile /var/run/network/ifstate:

Status in “ifupdown” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ifupdown

  Booting Jaunty, configuring networking interfaces fails, as does

  ~$ sudo /etc/init.d/networking restart
   * Reconfiguring network interfaces...
  ifdown: failed to open statefile /var/run/network/ifstate: No such file or directory
  ifup: failed to open statefile /var/run/network/ifstate: No such file or directory

  If I mkdir  /var/run/network/, then I get my network - for this boot,
  and have the same problem again the next time I boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/377432/+subscriptions




More information about the foundations-bugs mailing list