From: Bernd Schubert <bernd-schubert@web.de>
To: nfs@lists.sourceforge.net
Subject: nfs problems since server runs 2.4.19
Date: Fri, 20 Sep 2002 16:27:29 +0200 [thread overview]
Message-ID: <200209201627.29328.bernd-schubert@web.de> (raw)
Hi,
we have some strange problems since we run our server with a patched 2.4.=
19=20
(all the nfs patches that are in 2.4.20 except the 2 tcp ones).=20
Well on the server we rather often get the following lines for several of=
our=20
clients:
Sep 20 13:08:45 coulomb rpc.statd[866]: Received erroneous SM_UNMON reque=
st=20
from coulomb for 192.168.0.1
On some clients we get the following messages:
Sep 20 13:44:28 cauchy kernel: nsm_mon_unmon: rpc failed, status=3D-5
Sep 20 13:44:28 cauchy kernel: lockd: cannot monitor 192.168.0.100
Sep 20 13:44:28 cauchy kernel: lockd: failed to monitor 192.168.0.100
Sep 20 13:44:41 cauchy kernel: statd: server localhost not responding, ti=
med=20
out
Well, when this happens on the client, no kde program is working any long=
er=20
(other window managers that need the home directory as well, work fine). =
The=20
solution for this is to start the rpc.statd on the client.
Well, since all of this happend after we upgraded from 2.4.18 to=20
2.4.19+nfs-patches, I think its in direct connection with the upgrade.
Thanks,
Bernd
--=20
Bernd Schubert
Physikalisch Chemisches Institut
Abt. Theoretische Chemie
INF 229, 69120 Heidelberg
Tel.: 06221/54-5210
e-mail: =09bernd (dot) schubert (at) pci (dot) uni-heidelberg (dot) de=20
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2002-09-20 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200209201627.29328.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=nfs@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox