From: Bernd Schubert <bernd-schubert@web.de>
To: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>,
"NFS Mailing List" <nfs@lists.sourceforge.net>
Subject: Re: Problems with statd and lockd
Date: Sat, 5 Apr 2003 15:45:42 +0200 [thread overview]
Message-ID: <200304051545.43063.bernd-schubert@web.de> (raw)
In-Reply-To: <20030405015638.5118fbb9.philippe.gramoulle@mmania.com>
On Saturday 05 April 2003 01:56, Philippe Gramoullé wrote:
> Hi,
>
> Recently we started to get the following error messages on an Linux NFS
> server, running 2.4.21-pre5 vanilla, Debian unstable
>
> > statd: server localhost not responding, timed out
> > nsm_mon_unmon: rpc failed, status=-5
> > lockd: cannot monitor <Client IP here>
>
> A restart of nfs-kernel-server cleared the problem.
>
> We have filesystems that are exported sync, other are exported async.
>
Hi,
we also see those messages when we use the rpc.statd from debian packages. I
think the debian nfs-utils packages got "--enable-secure-statd" as configure
option. After recompiling the nfs-utils without this option and starting the
new rpc.statd on the clients, those messages should disappear, even without
restarting the nfs-server.
(I discovered this odd behaviour by accident.)
Best regards,
Bernd
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-04-05 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 23:56 Problems with statd and lockd Philippe Gramoullé
2003-04-05 10:14 ` Trond Myklebust
2003-04-05 11:18 ` Philippe Gramoullé
2003-04-05 11:50 ` Trond Myklebust
2003-04-05 12:05 ` Philippe Gramoullé
2003-04-05 13:45 ` Bernd Schubert [this message]
2003-04-05 14:27 ` Trond Myklebust
2003-04-05 16:31 ` Bernd Schubert
2003-04-05 23:06 ` Philippe Gramoullé
2003-04-06 12:16 ` Trond Myklebust
2003-04-06 13:09 ` Bernd Schubert
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=200304051545.43063.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=nfs@lists.sourceforge.net \
--cc=philippe.gramoulle@mmania.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.