Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35811 - [networkmanager][systemd] race condition at shutdown with mounted NFS drive
Attached to Project:
Arch Linux
Opened by Stefan Förster (HotblackDesiato) - Sunday, 16 June 2013, 06:59 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 24 December 2013, 21:06 GMT
Opened by Stefan Förster (HotblackDesiato) - Sunday, 16 June 2013, 06:59 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 24 December 2013, 21:06 GMT
|
DetailsDescription:
I recently recently switched my three Arch Linux machines to systemd. All three machines mount an NFS drive (/media/data) within my LAN on startup. Two of the machines are notebooks. That's why I use NetworkManager to manage network access. The third machine is a desktop. On this machine I use netcfg for networking. At shutdown, I get on both notebooks the following race condition: [** ] A stop job is running for /media/dataNetworkManager[1716]: <error> [1371362286.799529] [nm-dbus-manager.c:278] nm_dbus_manager_init_dbus(): Could not get the system bus. Make sure the message bus daemon is running! Message: failed to connect to socket /run/dbus/system_bus_socket: Verbindungsaufbau abgelehnt ("Verbindungsaufbau abgelehnt" means "connection refused".) I get hundreds of the same error messages, only the number in brackets [] changes, with the "[*** ]" at the beginning of each line in red. It seems that some processes can't handle the unmounting of the NFS drive properly and run into a race condition. This error appeared first when I switched to systemd and is 100% reproducible. When I unmount the drive /media/data manually before shutdown, the shutdown is flawless. On the desktop where I use netcfg instead of NetworkManager, the shutdown is also flawlees, with mounted NFS drive. Thus it seems that the shutdown procedure of NetworkManager is buggy. Additional info: The machines are up-to-date (June 16): extra/network-manager-applet 0.9.8.2-1 [installed] extra/networkmanager 0.9.8.2-1 [installed] community/networkmanager-dispatcher-netfs 1.0-2 [installed] core/systemd 204-3 [installed] core/systemd-sysvcompat 204-3 (base) [installed] core/nfs-utils 1.2.8-6 [installed] Steps to reproduce: Connect to a network via NetworkManager and mount a NFS drive. Try to shutdown the machine w/o unmounting the NFS drive first. |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 24 December 2013, 21:06 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#35671
Tuesday, 24 December 2013, 21:06 GMT
Reason for closing: Duplicate
Additional comments about closing:
The problem appears to be a cycle in the shutdown process, which systemd will break by removing one of the services. I have attached the output of journalctl during shutdown to show what it is doing: it is breaking the cycles by removing the NFS mount stop services. This causes the shutdown to hang since it ends up shutting down the network before something else tries to unmount the NFS drives.
My guess is when it spews dbus errors it's because of a different service being removed to break the cycle.
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=1722928c-e30e-4b79-96b8-ad3c12324fd0 swap swap defaults 0 0
UUID=605efaf2-a19b-479d-8d0f-e5e02fcf8368 /boot ext4 defaults,data=writeback,noatime 0 1
UUID=72695d97-55f4-4493-92d6-086e005b0eea / btrfs defaults,ssd,ssd_spread,noatime,compress 0 1
192.168.1.99:/public /media/data nfs rw,suid,dev,exec,auto,user,sync,_netdev,rsize=32768,wsize=32768,hard,intr,timeo=4,retrans=5 0 0
/dev/sr0 /media/cdrom auto noauto,user 0 0
/dev/sr0 /media/dvd auto noauto,user 0 0
adding "x-systemd.automount" in /etc/fstab solved it.
excerpt from my fstab:
192.168.0.13:/ /network/zw106 nfs defaults,noauto,user,intr,_netdev,x-systemd.automount 0 0
The option is supposed to work like autofs - mounting the folder on demand, so perhaps the user option is not necessary, but I was too lazy to try it out
EDIT: this option breaks most KDE applications when the server is not available
FS#35671