lockd: cannot monitor although all rpc processes are runnig

Discussion in 'Linux Networking' started by Jan =?ISO-8859-15?Q?L=FChr?=, Nov 12, 2003.

  1. 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
     
    Jan =?ISO-8859-15?Q?L=FChr?=, Nov 12, 2003
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.