SUMMARY - rpc.lockd problem

From: Andrew F. Mitchell (
Date: Thu Aug 22 1996 - 09:27:28 CDT

My original post:

        I have an older Sun4 running 4.1.3 that has recently started giving
me problems. I keep getting the message:
rpc.lockd: Cannot contact status monitor!
I checked for residual files in /etc/sm* but everything is clean - no lock
files hanging about. Killing rpc.lockd and rpc.statd then restarting
statd followed by lockd yields the same error. I managed to get things
working a couple weeks ago, but do not know what I did (didn;t know then
either ;-( If anyone out there has an idea what the problem might be or
where to look, I'd be much obliged....


I received replies from three people. None hit the nail on the
head directly, but the reponses were useful in that they nudged
me in the right direction. I had focused too closely on a problem
with rpc.lockd - in fact, the problem was that the machine had not
been ifconfig'd correctly and was not on the net at all! I did not
see the ifconfig error message at boot time due to my preoccupation
with rpc.lockd error messages. TO fix the problem I simply took
the interface down, brought it up manually with a correct config
command, and restarted rpc.lockd. Worked like a charm.

Thanks to the following for their help:

Guy Freeman <> (Ed Mehlschau)
Rick Kelly <>


Andrew F. Mitchell, Network Systems Administrator,
The University of Florida Biotechnology Program, (352) 846-1733

"I don't like it, and I'm sorry I ever had anything to do with it."
                                                   - Erwin Schrodinger

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:08 CDT