We had the same problem here today in Washington, DC with a 6.06 server running root on a 3ware RAID5. Problem did not appear until today's snowstorm and PEPCO power outage. A month or so ago we ran the usual apt-get update / apt-get upgrade to keep 6.06 current.
After noticing boot details showed missing /var/run/network/ifstate file, we manually did "mkdir /var/run/network" and then rebooted; everything seemed to work okay. We have the /etc/udev/rules.d/85-ifupdown.rules file. Not content to leave well enough alone, we added the workaround suggested here http://www.fs3.ph/article/ubuntu-904-in-an-openvz-ve -- i.e., adding to /etc/init.d/networking, immediately after "start)" line: [ -d /var/run/network ] || mkdir /var/run/network Again, no problem after we manually created the absent dir + file and rebooted. We modified the "networking" file anyway. Will advise any problem on next forced reboot....next snowstorm, PEPCO outage, or hardware failure. Love, love, love linux! -- ifdown: failed to open statefile /var/run/network/ifstate: https://bugs.launchpad.net/bugs/377432 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
