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

[michael brenden]

2011-07-03 - Another prolonged PEPCO outage (25 miles outside of DC)
brought down another Ubuntu 6.06 LTS 2 server today.  Did I mention
PEPCO is shit, and if DC power is any indication we are in severe
jeopardy as a country...Anyway...

This missing /var/run/network/ifstate issue remains an issue, even with
these lines added (after "start)" line) in following two files:

lines:
[ -d /var/run/network ] || mkdir /var/run/network
[ -f /var/run/network/ifstate ] || touch /var/run/network/ifstate

files:
/etc/init.d/networking
/etc/init.d/loopback

I'll surely follow up here as soon as I find the right fix.
Temporary workaround is to, after machine boots without networking, manually create /var/run/networking/ifstate and then run ifup -a

-- 
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