Stopping NFS locking failure

BMBeeman · #1 31st August 2005, 02:47 AM

Stopping NFS locking [FAIL]

I get that everytime my computer shuts down, should this worry me and it there a way to fix it?

trinitymx04 · #2 9th November 2005, 12:31 AM

I've the same problem, any suggestion?

Zakarth · #3 11th November 2005, 03:50 PM

Its probably not anything to worry about. In fact, unless you intend to mount a network file system (its kind of a type of share online that unix-type OS'es use) then I would recommend just disabling NFS utilities from the startup/shutdown altogether. You can do this from any console by typing "setup" and going to "System Services" and unchecking any NFS related utilities.

nokollonzo · #4 15th November 2005, 10:02 PM

Even if I'm a proud Fedora user, I think that it's better to know how to use LInux without being to stick to a particular distro's tool.
To disable NFS client from command line:
be root

Code:

cd /etc/rc5.d 
mv S57netfs K57netfs 
mv S20nfs K20nfs
mv S86nfslock K86nfslock

in this way you disable not only the lock daemon, but olso nfs client and nfs server. Notice that depending on your installed packages you may not have all the three services present: no problem.
If your default tunlevel is not "5" (raaaaaaaare case,) edit another directory. To know your def runlevel:

Code:

cat /etc/inittab |grep ^id.*initdefault

you should see something like:

Code:

id:5:initdefault:

I want to say that I'm a Unix sysadmin from 2 years, I run FC on my client machines, and I never knew about the "setup" commandline utility. (very similar to the Slackware's one, I now see)

Zakarth · #5 15th November 2005, 10:07 PM

nokollonzo:

I, like you, came from a very specific background in Slackware which didn't have any of the nifty utilities that Redhat had. Unfortunately, Redhat based distros seem to be going through an unfortunate trend of forcing you more and more to progress towards their services.

Your method of disabling the service from starting up works, but you're doing the "back end" way of doing it. Theres an even easier CLI solution and thats to do:

chkconfig --del nfs

This will take care of the symbolic link management.

or chkconfig nfs off

Will remove it from starting up.

nokollonzo · #6 15th November 2005, 11:56 PM

I've always used Fedora.
But I think is better to stay compatible. Anyway slack has a config tool very similar to "setup".
I'm not sure that the command chkconfig prevents both nfs server, client and lock daemon to start at boot. Are you sure?

If talking about Fedora's tools then...why don't we use system-config-services? I've just finished translating it in italian

Always be part of the project guys!

wbishop311 · #7 17th November 2005, 09:46 PM

If one were to disable NFS related utilities, does that mean we would have to re-enable them to connect another pc to it (for file or internet connection sharing)?

Zakarth · #8 18th November 2005, 01:04 AM

For filesharing using NFS, yes, for Internet Connection Sharing, i'd certainly hope not. If you're planning on sharing files from linux, you're better off using Samba anyways-- it has a much wider range of support for authentication schemes and what not. NFS is kind of outdated but its supported by a vast array of *nixes so its kept with all distributions.

robatino · #9 29th November 2005, 12:11 AM

This has been fixed in Rawhide but hasn't been pushed to users yet. In the meantime it seems harmless.

https://bugzilla.redhat.com/bugzilla....cgi?id=162446

traveller · #10 29th November 2005, 04:14 PM

nokollonzo and Zakarth:

Thanks for your advice. I have read some of the threads that gave me different approaches to fix this problem such as check /etc/init.d/nfslock to see what it does, I also read some papers how to config NFS on server and client.

My current system with FC4 is a testing server. There is no any client will access and mount file system on it. I have checked /etc/rc5.d/, I even do not have S57netfs, K57netfs, S20nfs, S86nfslock, K86nfslock files. But I do have K20nfs over there. When I boot system, I can see that starting NFS stated OK. Does this mean that NFS locking has been started whth the system booting? Why can not system automatically stopping NFS locking? I do think your way might work for this problem. I just want to make sure this is at least the better way than others. Please give me more tips on this. Thanks a lot.

nokollonzo · #11 9th December 2005, 09:22 AM

You should get:

Code:

bash$ ls /etc/rc5.d |grep nfs
K20nfs
S14nfslock

bjh · #12 22nd January 2006, 07:19 PM

Zakarth-
I'm relatively new to linux, running FC4 (kernel 2.6.11), and was having the NFS locking problem as well...your fix took care of it, thanks!
btw...nfs services are successfully started at boottime, but locking problem on shutdown is avoided!

sej7278 · #13 22nd January 2006, 10:24 PM

well none of those really fix the problem, they just prevent the service starting, so it won't error as it never has to stop!

i am actually using the nfs server, and i get the error.

nothing has been done about it so far according to bugzilla, although it looks like it is harmless - possibly just an error in the init.d script.

GoodOmens · #14 23rd January 2006, 03:03 AM

As someone pointed out the bugzilla code ... I would assume changing:

file: /etc/init.d/nfslock

Code:

<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
}

to:

Code:

        echo -n $"Stopping NFS locking: "
        if [ "$USERLAND_LOCKD" ]; then
           killproc lockd
        #else
        #   killproc lockd -KILL
        fi

Would fix the problem. I havent tried it so dont blame me if it doesnt work =p