From: Bian Naimeng <biannm@cn.fujitsu.com>
To: Dan Wallis <mrdanwallis@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: statd: server localhost not responding, timed out; lockd: cannot monitor <client>
Date: Mon, 02 Aug 2010 17:12:39 +0800 [thread overview]
Message-ID: <4C568C07.6080308@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTinZN+uhDShmg8aKiSEA8M3pr_RXu58OyyLPapxm@mail.gmail.com>
> Hello list :)
>
> This is my first post here, so if it's in the wrong place, or if I've
> not read the appropriate documentation, please feel free to send me a
> link to the relevant bits. I've tried searching the archives, and the
> internet at large, but haven't yet come across anything that's helped.
... snip ...
> I'm seeing these messages in the file server's system log:
>
> Jul 30 09:37:17 fs0 kernel: [1810036.560046] statd: server localhost
> not responding, timed out
> Jul 30 09:37:17 fs0 kernel: [1810036.560053] nsm_mon_unmon: rpc
> failed, status=-5
> Jul 30 09:37:17 fs0 kernel: [1810036.560064] lockd: cannot monitor node2
> Jul 30 09:38:22 fs0 kernel: [1810101.384027] statd: server localhost
> not responding, timed out
> Jul 30 09:38:22 fs0 kernel: [1810101.384033] nsm_mon_unmon: rpc
> failed, status=-5
> Jul 30 09:38:22 fs0 kernel: [1810101.384044] lockd: cannot monitor node0
>
It looks like that nfslock service(statd) not running, please try run the
followed command,
# service rpcbind start
# service nfslock restart
--
Regards
Bian Naimeng
prev parent reply other threads:[~2010-08-02 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 7:47 statd: server localhost not responding, timed out; lockd: cannot monitor <client> Dan Wallis
2010-08-02 9:12 ` Bian Naimeng [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C568C07.6080308@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mrdanwallis@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.