Red Hat Bugzilla – Bug 173496
nfs mount failures when using tcp protocol for nfs
Last modified: 2007-11-30 17:07:09 EST
Description of problem:
When attempting to mount and umount a large number (200+) nfs files systems via
the automounter using the tcp protocol, after approximately 150 sucessful
mounts and umounts, all subsequent mount attempt fail with the following
RPC: Authentication error; why = Client credential too weak
Note that this occurs when running as root.
The following script can be used to reproduce the error:
while read mp
count=`expr $count + 1`
In the example above, /sopt is automounter mount point and the file mp.list is
list of approximately 800+ potential mount points (essentially all available
maps in our nis map "auto.sopt" (below).
Additionally, the problem does not occur when using the udp protocol.
The file auto.master contains the following:
/sopt yp:auto.sopt -proto=tcp,rsize=32768,wsize=32768
Version-Release number of selected component (if applicable):
RHEL 3 WS Update 6
Steps to Reproduce:
1. Attempt to mount and immediately umount 200+ file systems in succesion via
the autmounter using the tcp protocal for nfs.
After about ~150 successful mounts and umounts, all subsequent mount attempts
fail on the automounter mount point for approximately 30 seconds to 1 minute.
The message below appears for each failed mount attempt (with the name of the
file system that was not able to be mounted):
cd: /sopt/exptools: No such file or directory
The message in /var/log/messages is:
Nov 17 11:06:04 machine1 automount: mount(nfs): nfs: mount failure
Nov 17 11:06:04 machine1 automount: failed to mount /sopt/exptools
Nov 17 11:06:04 machine1 automount: >> nfs bindresvport: Address already
Nov 17 11:06:04 machine1 automount: >> mount: RPC: Authentication error;
why = Client credential too weak
Expectation is to be able to successfully mount and umount several hundred file
systems in succession
This is apparently an accidental duplicate report.
*** This bug has been marked as a duplicate of 173495 ***