Networking Forums

Networking Forums > Computer Networking > Linux Networking > lockd: cannot monitor although all rpc processes are runnig

Reply
Thread Tools Display Modes

lockd: cannot monitor although all rpc processes are runnig

 
 
Jan =?ISO-8859-15?Q?L=FChr?=
Guest
Posts: n/a

 
      11-12-2003, 05:46 PM
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 Datenschützer bitten um Mithilfe
https://www.ccc.de/updates/2003/files/poster.big.jpg
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: Processes Joe Pfeiffer Linux Networking 0 07-12-2009 11:56 PM
Re: Processes david Linux Networking 0 07-12-2009 11:45 PM
Monitor ports & their processes? Ed Flecko Windows Networking 0 11-02-2005 08:25 PM
NFS statd/lockd warnings Roger Leigh Linux Networking 2 12-22-2004 03:28 PM
Need to get Kerberos runnig Lamar Thomas Windows Networking 1 04-25-2004 04:16 AM



1 2 3 4 5 6 7 8 9 10 11