From: Bernd Schubert <bernd-schubert@web.de>
To: nfs@lists.sourceforge.net
Cc: Gavin Hamill <gdh@acentral.co.uk>, Chip Salzenberg <chip@debian.org>
Subject: Re: lockd / statd fun (sorry)
Date: Fri, 23 Apr 2004 13:32:00 +0200 [thread overview]
Message-ID: <200404231332.07891.bernd-schubert@web.de> (raw)
In-Reply-To: <200404231137.29216.gdh@acentral.co.uk>
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Gavin,
> I'm afraid I have to dredge up old ground here...
>
> I'm running about 30 diskless workstations PXE-booting to an NFS-root and
> NFS-homedir with NIS logins, and the workstations are regularly getting t=
he
> familiar
>
> Apr 23 11:17:18 10.0.0.13 kernel: nsm_mon_unmon: rpc failed, status=3D-13
> Apr 23 11:17:18 10.0.0.13 kernel: lockd: cannot monitor 10.0.0.253
> Apr 23 11:17:18 10.0.0.13 kernel: lockd: failed to monitor 10.0.0.253
> Apr 23 11:17:18 10.0.0.13 kernel: nsm_mon_unmon: rpc failed, status=3D-13
> Apr 23 11:17:18 10.0.0.13 kernel: lockd: cannot monitor 10.0.0.253
>
we also use a diskless environment and also see that problem. However, as I=
=20
posted a long time ago to this list, it only happens if the nfs-utils are=20
compiled with the '--secure-statd' confiure option.
So every time we perform a general debian (testing) -update and so when als=
o=20
the nfs-utils become updated, we see that problem. Everytime this happens, =
I=20
fetch the debian nfs-utils source and recompile them without the=20
'--secure-statd' option.
When I posted that workaround, Trond told me, that its not good, since fake=
d=20
packages can be send to the statd-daemon that way. However, for us its bett=
er=20
to have an unsecured statd running than non at all. Also, the rpc.statd=20
manpage says, that the statd can be protected by the 'tcp_wrapper library'.
Cheers,
Bernd
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAiP6zC8BUnAF+ydYRAv6qAJ9XovApFhzLv1E7/EBUxUbstj6UbQCeKW2a
0BIpyiHKUmqYIGnvxIO0JmQ=3D
=3DDGzb
=2D----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-04-23 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 10:37 lockd / statd fun (sorry) Gavin Hamill
2004-04-23 11:32 ` Bernd Schubert [this message]
2004-04-23 11:48 ` Gavin Hamill
2004-04-23 11:57 ` Olaf Kirch
2004-04-27 13:43 ` Gavin Hamill
2004-04-27 15:32 ` Olaf Kirch
2004-04-27 15:47 ` Gavin Hamill
2004-04-27 15:56 ` Olaf Kirch
2004-04-27 16:49 ` Trond Myklebust
2004-04-27 18:15 ` Gavin Hamill
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=200404231332.07891.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=chip@debian.org \
--cc=gdh@acentral.co.uk \
--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 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.