From: Salvador Peralta <speralta@willamette.edu>
To: nfs@lists.sourceforge.net
Subject: Recent intermittent problem authenticating clients against NFS.
Date: Wed, 30 Oct 2002 15:26:05 -0800 [thread overview]
Message-ID: <3DC06A8D.8020706@willamette.edu> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all,
We are experiencing an (apparently) recent phenomenon involving
intermittent problem authenticating clients against NFS.
Clients can generally connect, but periodically, a random given client
will attempt to authenticate against NFS, and will fail with (example)
"Oct 30 14:02:46 info-1 rpc.mountd: refused mount request from lib-ncd9
for /home (/): no export entry" logged in /var/log/messages.
Once first client fails to authenticate, each subsequent attempt to
authenticate from any client fails causing a cascading effect until each
parent process managing connection is killed and/or client system is
hard rebooted which is now taking down our ncd900 terminals on an
all-too regular basis.
Previous admin tells me that the wildcard option in /etc/exports has
been in place for a few years before these problems started occuring.
Problem does not appear to affect xterminals running telnet on the same
network using os.350.
Many thanks for any insights people can provide.
Relevent Info:
(Red Hat Linux 7.1 2.96-98)
Linux version 2.4.7-10smp
clients: ncd900 / os.900
nfs-utils-0.3.1-13
$ cat /etc/exports
/export *(ro)
/home/ncbridge *(ro)
/home/tekxp *(ro)
$ netstat -a | grep lib-ncd5
tcp 0 0 158.104.2.149:42992 lib-ncd5:x11
ESTABLISHED tcp 0 0 158.104.2.149:42399
lib-ncd5:x11 ESTABLISHED tcp 0 0
158.104.2.149:42400 lib-ncd5:x11 ESTABLISHED tcp
0 0 158.104.2.149:42401 lib-ncd5:x11 ESTABLISHED
tcp 0 0 158.104.2.149:42357 lib-ncd5:x11
ESTABLISHED tcp 0 0 info-1:xfs
lib-ncd5:1026 ESTABLISHED
$ /usr/sbin/rpcinfo -p localhost
~ program vers proto port
~ 100000 2 tcp 111 portmapper
~ 100000 2 udp 111 portmapper
~ 100024 1 udp 32768 status
~ 100024 1 tcp 32768 status
~ 391002 2 tcp 32769 sgi_fam
~ 100011 1 udp 701 rquotad
~ 100011 2 udp 701 rquotad
~ 100011 1 tcp 704 rquotad
~ 100011 2 tcp 704 rquotad
~ 100005 1 udp 32769 mountd
~ 100005 1 tcp 32770 mountd
~ 100005 2 udp 32769 mountd
~ 100005 2 tcp 32770 mountd
~ 100005 3 udp 32769 mountd
~ 100005 3 tcp 32770 mountd
~ 100003 2 udp 2049 nfs
~ 100003 3 udp 2049 nfs
~ 100021 1 udp 32770 nlockmgr
~ 100021 3 udp 32770 nlockmgr
~ 100021 4 udp 32770 nlockmgr
- --
Salvador Peralta
Systems Administrator
Mark O. Hatfield Library
Willamette University
http://www.willamette.edu/~speralta
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9wGqMNmBW4SNQemURAi/fAKDrzZVkI242rfmllI/FRiVmLH+AcwCgu454
0ViI3Th+MJfjYdvSgpaHXhg=
=VE4/
-----END PGP SIGNATURE-----
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-10-30 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 23:26 Salvador Peralta [this message]
2002-10-31 0:12 ` Recent intermittent problem authenticating clients against NFS Neil Brown
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=3DC06A8D.8020706@willamette.edu \
--to=speralta@willamette.edu \
--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.