lockd cannot talk to statd??

[Tapani Tarvainen]

What could be the cause when file locking over NFS fails and rpc.lockd
(on the NFS server) complains that

"Cannot contact status monitor!!"

rpc.statd is running, it in turn complains that

"statd cannot talk to statd at ..."

Everything else seems to be working normally, NFS mounts succeed and files can be read and written but not locked. On the client side I see no error messages other than individual programs hanging or complaining
"No locks available".

This is under HP-UX 11.11.

Any ideas would be appreciated.

[Shahul]

Hi

Please check up whether rpc.lockd and rpc.statd daemons are running or not by issuing these commands.

#ps -ef | grep statd
#ps -ef | grep lockd

If it is not running please restart those.

#/usr/sbin/rpc.lockd
#/usr/sbin/rpc.statd

Best of luck

Shahul

[Tapani Tarvainen]

rpc.lockd and rpc.statd are running (and continue logging error messages). I already tried stopping and restarting them, even tried rebooting - they come up as they should but don't work (can't talk to each other, apparently).

Any other ideas?

[Hartmut Lang]

Check your Patch-Status:
rpc.lockd was patched with PHNE_22878 and PHNE_23502.
I had a NFS-locking problem which was solved after installing PHNE_22878.

[Tapani Tarvainen]

I have PHNE_23502 installed
(I believe it was part of June Gold Bundle). Any other ideas?

[Todd Morgan · Accepted solution]

You can try restarting lockd statd with the following steps.
ps -aef |grep lockd
ps -aef |grep statd
kill theses processes
1) cd /var/statmon/sm
ls This will show hostnames that are having the problem also ls /var/statmon/sm.bak this also will show hostnames
You will need to remove the hostnames thats having the problem
from theses directories stated above
rm xx xx being the hostname to remove
then restart lockd statd
/usr/sbin/rpc.statd &
/usr/sbin/rpc.lockd &
good luck, Todd

[Tapani Tarvainen]

Resolved! Removing /var/statmon/sm and restarting the daemons made the problem go away.

Phew! :-)