SunOS error msg: rpc.lockd: Cannot contact status monitor!

[Bill Finnerty]

I am getting the above error msg coming up on my Sparc5 console on
SunOS4.1.3_U1. I am running OpenWin windows and have multiple xterm
windows 'rlogin' into other Sun servers on my network. I also have
multiple Perfmeter windows monitoring remote servers' status.

Where is this error message coming from ? Is it my local host server
or one of the remote servers I am monitoring ?
How do I fix it so that the error msg stops. It's a real pain because
each time it messes up my Openwin windows and I have to "refresh".
Thx

[Ofer Inbar]

Note the crosspost and Followup-To: header.
This is more appropriate for the Sun group.

It's probably coming from the local host, but if you're doing remote
syslogging and the host you're on is the loghost, then it might be
coming from elsewhere. If so, the hostname should be logged with the
error - look in /var/adm/messages or /var/log/syslog.

Anyway, once you've figured out which host it is, the actual problem
is that you're running rpc.lockd without rpc.statd. You must either
run both of these daemons, or neither. They're used for NFS, so if
you're not doing NFS you might as well run neither. If you are doing
NFS, you need both. If the rpc.statd died, restart it. Also, check
your inetd.conf to see if you commented out statd but not lockd.

-- Cos (Ofer Inbar) -- c...@leftbank.com c...@cs.brandeis.edu
-- The Left Bank Operation -- l...@leftbank.com http://www.leftbank.com/
"OSI is a beautiful dream, and TCP/IP is living it!"
-- Einar Stefferud <St...@nma.com>, IETF mailing list, 12 May 1992