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

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

Post by Bill Finnert » Wed, 04 Dec 1996 04:00:00



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

 
 
 

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

Post by Ofer Inb » Wed, 04 Dec 1996 04:00:00


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


>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".

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.



 "OSI is a beautiful dream, and TCP/IP is living it!"


 
 
 

1. HELP: rpc.lockd: Cannot contact status monitor!

The subject says it all.  What is happenning here?  How do I fix it.
This is on a Tatung COMPstation 40.  I have another one configured just
the same. No problems.

Thanks

Doug

Make your own yard sign.  Perot '92

Ask not what your country can do for you, but what you can do for your
country.  -  JFK

2. only root can log on

3. RPC.LOCKD cannot contact RPC.STATD. HELP!!

4. disk slices

5. lockd: cannot monitor although all rpc processes are runnig

6. kde2beta problems

7. serious bug in SunOS rpc.lockd with hostnames >= 20 chars

8. How to break a Samba connection at server end?

9. SunOS rpc.lockd problem resolution

10. rpc.lockd (or lockd) on Linux ?

11. Problem with rpc.lockd [lockd] process

12. rpc.statd & rpc.lockd?