Description of problem: At shutdown, "Stopping NFS locking:" fails. If I'm not mistaken, this is associated with rpc.lockd which belongs to the nfs-utils package. Version-Release number of selected component (if applicable): nfs-utils-1.0.7-8 How reproducible: always Steps to Reproduce: 1. Clean workstation install of FC4. 2. Boot and then shutdown. Actual results: "Stopping NFS locking:" returns [FAILED]. Expected results: Should return [OK].
Forgot to mention that the error persists even with all current updates applied.
Created attachment 116334 [details] output of "strace -f rpc.lockd"
I'm having the same issue. I have all updates applied. Note, that I'm not using NFS though...
Neither am I. I've done clean FC4 installs on 2 different machines and have the same problem on both. My father also has the problem on his machine with a clean FC4 install. All of these are workstation installs and none of them use NFS. The strace I attached is short and the problem probably very simple. But since this service is enabled by default, even if it's not used, the error should be fixed.
agreed... its being looked into...
I am having the same 'fail' message from nfslock at shutdown. NFS is running properly. All updates have been applied. Please fix!
I am using NFS and noticed that I have to do a service nfs restart after bootup to get the nfs export to appear to other machines on my network. The Stopping error occurs when I do the restart. Subsequent restarts show no errors.
I've just compared the script /etc/init.d/nfslock from FC4 with the one from FC3: FC4: ----------------- <snip> stop() { # Stop daemons. echo -n $"Stopping NFS locking: " if [ "$USERLAND_LOCKD" ]; then killproc lockd else killproc lockd -KILL fi echo echo -n $"Stopping NFS statd: " killproc rpc.statd RETVAL=0 echo [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/nfslock return $RETVAL } <snip> FC3: ----------------- <snip> stop() { # Stop daemons. if [ "$USERLAND_LOCKD" ]; then echo -n $"Stopping NFS locking: " killproc lockd echo fi echo -n $"Stopping NFS statd: " killproc rpc.statd RETVAL=0 echo [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/nfslock return $RETVAL } <snip> Please note: The variable $USERLAND_LOCKD is empty on a non-modified FC4 installation. So why does the lockd process need to be stopped when it isn't started? if [ "$USERLAND_LOCKD" ]; then killproc lockd else killproc lockd -KILL <- This is the line which causes the failed message. What is this line for? It was missing in FC3. fi Maybe this could help...
Should be fixed in nfs-utils-1.0.7-16
When will a fix be released for FC4? The problem still exists for nfs-utils-1.0.7-12.FC4. Kind Regards André Fettouhi
Stopping the nfs service also stops lockd so I just commented out this section of /etc/init.d/nfslock to get rid of the annoying [ERROR] message: # Stop daemons. #echo -n $"Stopping NFS locking: " #if [ "$USERLAND_LOCKD" ]; then # killproc lockd #else # killproc lockd -KILL #fi #echo