shutdown hangs *stopping enhanced syslogd: rsyslogd*

[enle]

Does anyone have more information or a permanent solution to this problem?

If your PC hangs on shutdown with "stopping enhanced syslogd: rsyslogd" caused by NFS that cannot be unmounted, then there is a workaround.
Have a look at:
https://bugs.launchpad.net/ubuntu/+sour ... bug/859075

Stevan Kew Ell (slql) wrote on 2011-10-29: #41

I have a hack that works for me. I should say that I have a very incomplete understanding of the way the umount* files work with each other, but I don't think the hack is likely to affect anything else.

I have edited the file /etc/init.t/umountnfs.sh

Somewhere around line 84, alter the following line:-
fstab-decode umount $FLAGS $DIRS
to

fstab-decode /sbin/umount.nfs $DIRS $FLAGS

Note that the two options need to be switched around to $DIRS $FLAGS

This works on Wheezy too.

S

Regards

[nilssn]

Thanks for the tip. Unfortunately it didn't work. Probably because I mount nfs using /etc/rc.local and not fstab.

[patryk007]

I have identical problem.
If someone has already found nice workaround then share with us, please.

[riptorn]

Sorry if I'm too late to this thread, but did not see a solution posted.
On my system it seems that wicd is killed before umountnfs.sh in file rc0.d and rc6.d, causing the system to hang
I have remote nfs mounts that are auto mounted in fstab that hang on shutdown.
I cannot find an easy way to change the order in rc0.d, and rc6.d with with update-rc.d
but if i manually change it it shuts down correctly, so it seems the order is the culprit.

probably a better way is to add:
umount -a -t nfs

below do_stop() in the wicd script in /etc/init.d
then it shuts down quickly without having to change script orders.
I'm sure there must be a better solution.
Would there be a automated way to change wicd kill order to after umountnfs.sh ?

[rzr]

wasnt this issue reported on bugtracker ?

--
http://rzr.online.fr/q/nfs

[go4linux]

After further investigation I think the problem is that the network is taken down (network-manager/wicd killed) before nfs is unmounted causing the umount command to hang.
As a temporary fix I have disabled network-manager and configured my wireless with the interfaces file.

I have the same problem, and I agree on the cause. So I looked at /etc/rc0.d, and I don't understand a couple of things:

- why is network-manager called before umountnfs.sh?
- why is sendsigs not called at last? and why is rpcbind one of the processes excluded from the list of processes to kill?

[Christopher888]

Hi,

I am experiencing this problem on wheezy and cannot shutdown my system.

I can confirm that this is related to nfs. Any word on a fix?

[jpaulb]

I did an update and the problem went away.

[nilssn]

Still having this problem with an updated Testing.

[jpaulb]

I have done a couple updates and the problem has gone away for the time being

[layr]

Still no solution for this issue?
EDIT: my workaround:
being root, create file unmount_nfs.sh in /etc/init.d/ with the following contents and make it executable.

Code: Select all

#!/bin/bash
#script for automatic unmounting of nfs drive on reboot and shutdown
umount /mnt/server
exit

( /mnt/server should be replaced by your mount point)

Then in terminal, also being root, run

Code: Select all

update-rc.d unmount_nfs.sh start 20 0 6 .

(including the period)

[cuda]

I also have this issue with a NFS drive and wireless/network-manager connection on my laptop.

I've been having good luck with this network-manager script which I put in the /etc/NetworkManager/dispatcher.d directory. I called it 00nfs and made it executable. It simply mounts or unmounts all the NFS shares whenever the connection goes up or down. I still kept all of my NFS mount information in /etc/fstab.

/etc/NetworkManager/dispatcher.d/00nfs

Code: Select all

#!/bin/sh

# mount/unmount NFS shares on network-manager up/down events.

case "$2" in
   up)
      mount -a -t nfs4
      ;;
   down)
      umount -a -t nfs4
      ;;
esac

Note that the -t option seems to be finicky about whether you specify nfs or nfs4. If I specify nfs as the filesystem type in fstab, I am able to mount all of my NFS4 shares with -t nfs, but to unmount them I have to use -t nvf4. For consistency, I specify nfs4 everywhere.

[parmenion]

I've had a similar problems having a some cifs filesystems mounted.
I've solved the problem by renaming the kill-scripts to change the order of execution:

Code: Select all

mv /etc/rc0.d/K04rsyslog /etc/rc0.d/K05rsyslog
mv /etc/rc0.d/K05umountnfs.sh /etc/rc0.d/K04umountnfs.sh
mv /etc/rc6.d/K04rsyslog /etc/rc6.d/K05rsyslog
mv /etc/rc6.d/K05umountnfs.sh /etc/rc6.d/K04umountnfs.sh


But i'm not sure if this the right way to fix the problem.

[llivv]

Have any of the first three posters int his thread tried installing the testing default kernel to see if it works?

[parmenion]

I've to begdown: the renaming did not fix it. I don't know why but the effekt reoccured.

I've investigated a bit further:
My network connection is via WLAN and read about problems with unmounting file systems when the network-manager has already stop.