networking fails to start after reboot
In an Alpine 2.5.0 Xen dom0, networking fails to start with the following messages:
* Starting networking … * lo …ifup: can’t open ‘/var/run/ifstate’:
Read-only file system
[ !! ]
* br0 …ifup: can’t open ‘/var/run/ifstate’: Read-only file system
[ !! ]
* br0:0 …ifup: can’t open ‘/var/run/ifstate’: Read-only file system
[ !! ]
* ERROR: networking failed to start
* ERROR: cannot start named as networking would not start
* Loading modules … [ ok ]
* Setting system clock using the hardware clock [UTC] … [ ok ]
* Setting up the Logical Volume Manager … [ ok ]
* Checking local filesystems … [ ok ]
* Remounting root filesystem read/write … [ ok ]
* Remounting filesystems … [ ok ]
* Mounting local filesystems … [ ok ]
Note that /etc/init.d/networking is trying to write to /var/run before it has been remounted rw. I see two possible fixes:
- Make networking depend on the root filesystem being mounted rw; or
- Make /var/run be a symbolic link to /run (which is tmpfs, and therefore rw).
I have classified this as a high priority bug because rebooting a remote system and never regaining network connectivity is quite unpleasant absent a serial console.
(from redmine: issue id 1528, created on 2012-12-19, closed on 2012-12-26)
- Changesets:
- Revision 7815e5d5 by Natanael Copa on 2012-12-21T18:52:30Z:
main/openrc: network service depends on localmount
it needs /var/run for dhcp client
ref #1528
- Revision 60fe017d by Natanael Copa on 2012-12-28T14:48:29Z:
main/openrc: network service depends on localmount
it needs /var/run for dhcp client
ref #1528
(cherry picked from commit 7815e5d5995daa91205471dfd8b2696709f79289)