Bug#746358: systemd: system boot hangs if /etc/fstab contains an NFS mount: how about wheezy-backports?
Control: reopen -1 I'm not sure what to do with this really. Yesterday I upgraded my wheezy system and come to this very issue there. Because I had systemd installed from wheezy-backports, and now this bug reappeared in a backported version, ofcourse initscripts in wheezy is not patched. At least, either systemd should have a Breaks: initscripts fixed-version, or the same fix should be provided in wheezy initscripts. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: Boot hangs if fstab contains NFS entries
On 14/06/14 06:32, Michael Biebl wrote: Am 08.06.2014 00:37, schrieb Jason Alavaliant: I've just tested the latest initscripts package (2.88dsf-53.1) Jason, could you please test again with 2.88dsf-53.2? 53.1 had an embarrasing formatting error. I've retested with 2.88dsf-53.2 and confirmed that the /etc/network/if-up.d/mountnfs script in that version of the package successfully boots my machine without it hanging.So from my perspective that version of the package fixes this bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: Boot hangs if fstab contains NFS entries
Am 08.06.2014 00:37, schrieb Jason Alavaliant: I've just tested the latest initscripts package (2.88dsf-53.1) Jason, could you please test again with 2.88dsf-53.2? 53.1 had an embarrasing formatting error. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#746358: systemd: system boot hangs if /etc/fstab contains an NFS mount
Hi Michael, How do you configure your network? Do you use ifupdown vi /etc/network/interfaces and if so, is the interface marked as auto or allow-hotplug. this is quite new installation which uses NetworkManager. So my /etc/network/interfaces configures just lo: $ cat /etc/network/interfaces auto lo iface lo inet loopback It don't use ifupdown: $ cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile [ifupdown] managed=false It's configured via file /etc/NetworkManager/system-connections/Wired\ connection\ 1. I have another Debian installation with systemd 204-10, where I use /etc/network/interfaces and don't have NetworkManager: $ cat /etc/NetworkManager/NetworkManager.conf auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp allow-hotplug eth0 iface br0 inet static address 127.0.1.1 netmask 255.255.255.0 bridge_ports eth0 Both installations didn't have a problem with upgrade. Best regards, Petr Vorel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: Bug reappears
Unfortunately the new version of initscripts (2.88dsf-53.1) has a modified mountnfs script which reintroduces this bug. The patch in an earlier post had fixed it. I don't know enough to be able to patch the new script so i hope somebody here will be able to come up with something. --- Sent from a computer.
Bug#746358: Bug reappears
Are you sure you are using the new script? What kind of error do you still encounter? On 7. Juni 2014 23:08:06 MESZ, david davce...@keyworld.net wrote: Unfortunately the new version of initscripts (2.88dsf-53.1) has a modified mountnfs script which reintroduces this bug. The patch in an earlier post had fixed it. I don't know enough to be able to patch the new script so i hope somebody here will be able to come up with something. --- Sent from a computer.
Bug#746358: Boot hangs if fstab contains NFS entries
I've just tested the latest initscripts package (2.88dsf-53.1) Unfortunately the lines in adds to /etc/network/if-up.d/mountnfs ; -- # Skip the mountnfs hook when being triggered by the networking SysV init # script and instead use the systemd built-in mechanisms to mount remote # file systems. # This avoids a deadlock caused by the rpcbind SysV init script depending # on $network and the $network LSB facility being provided by the networking # SysV init script. if [ -d /run/systemd/system ]; then systemctl list-jobs | grep -q network.target exit 0 fi - Do not fix the problem for me and my boot started sitting on configuring network interfaces again (I only waited 5minutes before giving up, so I'm unsure if it was just being very slow or if it would never have completed) I ended up swapping out the above lines for --- if [ -d /run/systemd/system ] ; then systemctl status network.target /dev/null || exit 0 fi --- the same as I'd been using after a previous suggestion in this bug, they continues to work and my system now finishes configuring network interfaces and boots successfully again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: Boot hangs if fstab contains NFS entries
Am 08.06.2014 00:37, schrieb Jason Alavaliant: I've just tested the latest initscripts package (2.88dsf-53.1) Unfortunately the lines in adds to /etc/network/if-up.d/mountnfs ; -- # Skip the mountnfs hook when being triggered by the networking SysV init # script and instead use the systemd built-in mechanisms to mount remote # file systems. # This avoids a deadlock caused by the rpcbind SysV init script depending # on $network and the $network LSB facility being provided by the networking # SysV init script. if [ -d /run/systemd/system ]; then systemctl list-jobs | grep -q network.target exit 0 fi - Do not fix the problem for me and my boot started sitting on configuring network interfaces again (I only waited 5minutes before giving up, so I'm unsure if it was just being very slow or if it would never have completed) I ended up swapping out the above lines for --- if [ -d /run/systemd/system ] ; then systemctl status network.target /dev/null || exit 0 fi --- the same as I'd been using after a previous suggestion in this bug, they continues to work and my system now finishes configuring network interfaces and boots successfully again. Yeah, sorry. Messed up the formatting pretty badly. 2.88dsf-53.2, which I just uploaded, should work better -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#746358: systemd: system boot hangs if /etc/fstab contains an NFS mount
Am 06.06.2014 14:01, schrieb Petr Vorel: Package: systemd Followup-For: Bug #746358 Dear Maintainer, I have NFS mounted by default in my /etc/fstab and I didn't suffer to this bug after upgrade. How do you configure your network? Do you use ifupdown vi /etc/network/interfaces and if so, is the interface marked as auto or allow-hotplug. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#746358:
I ran into this problem and the patch in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746358#20 fixed it. Commenting out my NFS mounts worked also, but I couldn't figure out how to get to an editor short of using a rescue CD. (i.e. even in a recovery mode boot, I'd get stuck at Raise network interfaces.) I have br0 in /etc/network/interfaces, I have NetworkManager running for whatever reason, I have by-default NFS mounts in /etc/fstab, and the systemd package is version 204-10.
Bug#746358: Boot hangs if fstab contains NFS entries
I think I hit the the same bug, but I don't have any NFS mounts or bridge interfaces. It started happening afer upgrade to 204-10 (I skipped 204-9) and is also present in 208-1. 204-8 works fine and that is the version I'm currently running. My system sometimes starts normally, sometimes it hangs (loops) continuously printing Ordering cycle found, skipping Network. I haven't modified any init scripts. I'm willing to dig deeper if you want, but I'll need instructions how to debug this problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: Boot hangs if fstab contains NFS entries
I want to clarify one thing: 204-8 works fine, described behavior applies only to 204-10 and 208-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: Boot hangs if fstab contains NFS entries
A few extra cents worth may help here. 1. I can confirm that the patch given earlier fixes the boot time bug. 2. For a long time I have had a delay, say 30 sec, during startup. Now during that delay the message Starting a job for LSB: Raising Network Interfaces appears. (That's not the exact text but I don't wan to reboot this PC at this time) 3. There is a new behaviour pattern at shutdown. I have 5 mount points to a second machine. The 4th one takes a long time to unmount or even does not at all. I don't know if this is related to the bug under discussion. I will try to understand what comment=systemd.automount means and does :-) Thanks and keep up the good work Michael. Refards Davcefai --- Sent from a computer.
Bug#746358: Boot hangs if fstab contains NFS entries
Hi, I also have some NFS entries in my /etc/fstab and I manually patched /etc/network/if-up.d/mountnfs as suggested after I upgraded the system. However: the system still hangs on startup for 1-2 minutes saying: [ OK ] Started LSB: NFS support files common to client and server [ **] (X of Y) A start job is running for location The good thing though is, it is not a deadlock. But of course I don't want to wait several minutes for my system to boot. Your patch doesn't fix *this* issue. I'm using the network-manager package to connect to my local network. Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: Boot hangs if fstab contains NFS entries
Hi Daniel, Am 04.05.2014 11:20, schrieb Daniel Leidert: I also have some NFS entries in my /etc/fstab and I manually patched /etc/network/if-up.d/mountnfs as suggested after I upgraded the system. However: the system still hangs on startup for 1-2 minutes saying: [ OK ] Started LSB: NFS support files common to client and server [ **] (X of Y) A start job is running for location The good thing though is, it is not a deadlock. But of course I don't want to wait several minutes for my system to boot. Your patch doesn't fix *this* issue. I'm using the network-manager package to connect to my local network. The issue you are seeing is a slightly different one. I'll try to explain the reasons for it. We switched to native remote mount handling (previously, we relied on the mountnfs ifup.d hook for that). We also added support for LSB defined facilities in 204-9. That means, with 204-9, the /etc/init.d/networking init script will activate the network.target. As soon as that target is active, systemd will mount the remote file systems defined in /etc/fstab. In your case, you do not actually use ifupdown to bring up the network. As a result, when systemd tries to mount the NFS share, the network is not yet up and the mount request will time out. Unfortunately, we can't easily make NetworkManager.service pull in network.target, because with our current support for rcS type services this would create a dependency loop. I would suggest, that if you are using NetworkManager, you switch your NFS mount to use comment=systemd.automount to delay the actual mount request until it is accessed. Regards, Michael signature.asc Description: OpenPGP digital signature
Bug#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
severity 746358 serious thanks Am 30.04.2014 11:58, schrieb Aurelien Jarno: Given that systemd is now the default, if every persons with an NFS entry in fstab will get their systems broken, it might be a good idea to increase the severity of this bug. It's not yet the default (via the sysvinit meta-package), but I agree. Marking this bug as RC to prevent testing migration. I've sent a patch for sysvinit, let's hope it get's uploaded soon. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
On Tue, Apr 29, 2014 at 03:10:02PM +0200, Michael Biebl wrote: Am 29.04.2014 13:10, schrieb Jason Alavaliant: On 2014-04-29 22:36, Michael Biebl wrote: Am 29.04.2014 11:31, schrieb Jason Alavaliant: Do you have an NFS / remote fs configuration in your /etc/fstab? Yes I've got a nfs4 mounted home directory server.local:/ /home nfs4defaults0 0 I suspect the hang to be caused by the NFS fstab entry. Can you comment out the entry and reboot so we have confirmation? I got the same issue, and I don't have a bridge interface, but I do have a NFS entry in /etc/fstab. Disabling it makes the reboot to succeed. Given that systemd is now the default, if every persons with an NFS entry in fstab will get their systems broken, it might be a good idea to increase the severity of this bug. If so, can you please try the following patch for /etc/network/if-up.d/mountnfs with the NFS mount re-enabled. --- a/network/if-up.d/mountnfs +++ b/network/if-up.d/mountnfs @@ -7,6 +7,10 @@ #Also mounts SMB filesystems now, so the name of #this script is getting increasingly inaccurate. +if [ -d /run/systemd/system ] ; then + systemctl status network.target /dev/null || exit 0 +fi + PATH=/sbin:/bin . /lib/init/vars.sh This patch works for me, thanks. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
On 30/04/14 01:10, Michael Biebl wrote: Am 29.04.2014 13:10, schrieb Jason Alavaliant: On 2014-04-29 22:36, Michael Biebl wrote: Am 29.04.2014 11:31, schrieb Jason Alavaliant: Do you have an NFS / remote fs configuration in your /etc/fstab? Yes I've got a nfs4 mounted home directory server.local:/ /home nfs4defaults0 0 I suspect the hang to be caused by the NFS fstab entry. Can you comment out the entry and reboot so we have confirmation? If so, can you please try the following patch for /etc/network/if-up.d/mountnfs with the NFS mount re-enabled. --- a/network/if-up.d/mountnfs +++ b/network/if-up.d/mountnfs @@ -7,6 +7,10 @@ #Also mounts SMB filesystems now, so the name of #this script is getting increasingly inaccurate. +if [ -d /run/systemd/system ] ; then + systemctl status network.target /dev/null || exit 0 +fi + PATH=/sbin:/bin . /lib/init/vars.sh I've tested as requested and can confirm that if I restored the bridge interface lines in my /etc/network/interfaces but comment out the nfs mount in my fstab then the system boots without hanging. (Interestingly nfs mount in fstab doesn't cause a hang without the bridge network setup being there as well so in my case it seems to require both factors together to trigger the hang). Booting with mountnfs patched while the nfs mount and bridged network interface are in place also is successful so it looks like that patch does indeed fix the problem. Thank you for the quick fix. -J -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
Am 30.04.2014 11:58, schrieb Aurelien Jarno: On Tue, Apr 29, 2014 at 03:10:02PM +0200, Michael Biebl wrote: Am 29.04.2014 13:10, schrieb Jason Alavaliant: On 2014-04-29 22:36, Michael Biebl wrote: Am 29.04.2014 11:31, schrieb Jason Alavaliant: Do you have an NFS / remote fs configuration in your /etc/fstab? Yes I've got a nfs4 mounted home directory server.local:/ /home nfs4defaults0 0 I suspect the hang to be caused by the NFS fstab entry. Can you comment out the entry and reboot so we have confirmation? I got the same issue, and I don't have a bridge interface, but I do have a NFS entry in /etc/fstab. Disabling it makes the reboot to succeed. Given that systemd is now the default, if every persons with an NFS entry in fstab will get their systems broken, it might be a good idea to increase the severity of this bug. If so, can you please try the following patch for /etc/network/if-up.d/mountnfs with the NFS mount re-enabled. --- a/network/if-up.d/mountnfs +++ b/network/if-up.d/mountnfs @@ -7,6 +7,10 @@ #Also mounts SMB filesystems now, so the name of #this script is getting increasingly inaccurate. +if [ -d /run/systemd/system ] ; then + systemctl status network.target /dev/null || exit 0 +fi + PATH=/sbin:/bin . /lib/init/vars.sh This patch works for me, thanks. Yeah. In the end though it's an issue in the mountfs / rpcbind interaction. The rpcbing SysV init script has Required-Start: $network. And $network is provided by the /etc/init.d/networking init script. As /etc/network/if-up.d/mountnfs starts the rpcbind SysV init script, this leads to a deadlock if $network (aka network.target) is not yet up. The difference between systemd and sysvinit is, that systemd treats those dependencies dynamically, not statically like sysvinit/insserv at install time. I already poked Roger Leigh, our sysvinit maintainer about this, but haven't heard back from him yet. Let's hope one of our sysvinit maintainers can chime in here. Fwiw, it was pointed out on IRC that the above check is rather heavy-weight, since systemctl status queries the journal, a better check would be systemctl --quiet is-active network.target || exit 0 Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
Am 29.04.2014 11:31, schrieb Jason Alavaliant: Package: systemd Version: 204-10 Severity: important Dear Maintainer, I just updated my system which installed systemd-sysv after I rebooted I found that the system was now hanging on bootup (even in rescue mode) with the stopping point being configuring network interfaces. Do you have an NFS / remote fs configuration in your /etc/fstab? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
On 2014-04-29 22:36, Michael Biebl wrote: Am 29.04.2014 11:31, schrieb Jason Alavaliant: Package: systemd Version: 204-10 Severity: important Dear Maintainer, I just updated my system which installed systemd-sysv after I rebooted I found that the system was now hanging on bootup (even in rescue mode) with the stopping point being configuring network interfaces. Do you have an NFS / remote fs configuration in your /etc/fstab? Yes I've got a nfs4 mounted home directory server.local:/ /home nfs4defaults0 0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746358: systemd: system boot hangs if /etc/network/interfaces contains a bridge interface
Am 29.04.2014 13:10, schrieb Jason Alavaliant: On 2014-04-29 22:36, Michael Biebl wrote: Am 29.04.2014 11:31, schrieb Jason Alavaliant: Do you have an NFS / remote fs configuration in your /etc/fstab? Yes I've got a nfs4 mounted home directory server.local:/ /home nfs4defaults0 0 I suspect the hang to be caused by the NFS fstab entry. Can you comment out the entry and reboot so we have confirmation? If so, can you please try the following patch for /etc/network/if-up.d/mountnfs with the NFS mount re-enabled. --- a/network/if-up.d/mountnfs +++ b/network/if-up.d/mountnfs @@ -7,6 +7,10 @@ #Also mounts SMB filesystems now, so the name of #this script is getting increasingly inaccurate. +if [ -d /run/systemd/system ] ; then + systemctl status network.target /dev/null || exit 0 +fi + PATH=/sbin:/bin . /lib/init/vars.sh Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
