lockd: cannot monitor although all rpc processes are runnig

lockd: cannot monitor although all rpc processes are runnig

Post by Jan Lüh » Fri, 14 Nov 2003 02:46:25



Greetings,

I've some problems locking files on an nfs-Server (Debian Woody stable) I
tried v2, v3 and I haven even established a direkt LAN Connection between
the server and the client, but I it won't work. Thus, I'm unable to start
KDE with NFS-mounted homedirs.

Ok, heres my error-output.

ksymoops/20030318062531.ksyms:c018d640 lockd_up_Rf6933c48
ksymoops/20030318062531.ksyms:c018d750 lockd_down_Ra7b91a7b
ksymoops/20030319062518.ksyms:c018d640 lockd_up_Rf6933c48
...

messages:Nov 12 09:32:13 epsilon kernel: lockd: server 192.168.1.200 not
responding, still trying
messages:Nov 12 09:32:13 epsilon kernel: lockd: server 192.168.1.200 not
responding, still trying
messages:Nov 12 09:34:08 epsilon kernel: lockd: server 192.168.1.200 OK
messages:Nov 12 09:38:31 epsilon kernel: lockd: server 192.168.1.200 not
responding, still trying
messages:Nov 12 09:39:23 epsilon kernel: lockd: server 192.168.1.200 OK
messages:Nov 12 09:39:26 epsilon kernel: lockd: server 192.168.1.200 not
responding, still trying
messages:Nov 12 09:39:27 epsilon kernel: lockd: server 192.168.1.200 not
responding, still trying
messages:Nov 12 09:42:43 epsilon kernel: lockd: server 192.168.1.200 not
responding, still trying
messages:Nov 12 09:53:24 epsilon kernel: lockd: cannot unmonitor 192.168.3.1
messages:Nov 12 09:53:49 epsilon kernel: lockd: cannot monitor 192.168.3.1
messages:Nov 12 09:53:49 epsilon kernel: lockd: failed to monitor
192.168.3.1
messages:Nov 12 09:53:49 epsilon kernel: lockd: cannot monitor 192.168.3.1
messages:Nov 12 09:53:49 epsilon kernel: lockd: failed to monitor
...

Running rpc processes on the server:
ps -A | grep rpc
  226 ?        00:00:00 rpc.rquotad
  229 ?        18:08:41 rpc.statd
  241 ?        00:00:00 rpc.yppasswdd
  244 ?        00:00:00 rpc.ypxfrd
  618 ?        00:00:00 rpciod
  620 ?        00:00:00 rpc.mountd

Running rpc processes on the client:
ps -A | grep rpc
  115 ?        00:00:00 rpciod
  283 ?        00:00:01 rpc.nfsd
  285 ?        00:00:00 rpc.mountd
  809 ?        00:00:00 rpc.statd

What's wrong here? I don't use firewalling or other techniques. It's just a
direct connection between two of our servers...

Keep smiling
yanosz

--
Die Datenschtzer bitten um Mithilfe
https://www.ccc.de/updates/2003/files/poster.big.jpg

 
 
 

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

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

2. HTTP Port not being forwarded using rc.firewall...why??

3. Problem with rpc.lockd [lockd] process

4. IP Masquerading does not work!!!

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

6. .htaccess help!

7. Problem with rpc.lockd [lockd] process

8. select problems

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

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

11. rpc.lockd hangs process locking files on NeXT NFS server

12. rpc.statd & rpc.lockd?

13. Need help with rpc.statd and rpc.lockd messages (AIX 3.2)