Red Hat Bugzilla – Bug 210862
Last modified: 2008-08-02 19:40:32 EDT
Description of problem:
mountd dumps core
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start mountd
2. mount any filesystem (from another host of course)
Crash with core dump
Mounted file system
Remote login via rsh fails too.
Reverting to glibc-2.4-8 resolved the problem with mountd and rsh.
Stack trace of the crashed mountd
#0 0x006b2893 in strdup () from /lib/libc.so.6
#1 0x00f50b5f in nis_list () from /lib/libnsl.so.1
#2 0x00d9762e in _nss_nisplus_setnetgrent () from /lib/libnss_nisplus.so.2
#3 0x0072dd05 in innetgr () from /lib/libc.so.6
#4 0x00b6063f in mount_dispatch () from /usr/sbin/rpc.mountd
#5 0x00b60a17 in mount_dispatch () from /usr/sbin/rpc.mountd
#6 0x00b5e12f in mount_dispatch () from /usr/sbin/rpc.mountd
#7 0x00b5ca27 in ?? () from /usr/sbin/rpc.mountd
#8 0x00b5ce4f in ?? () from /usr/sbin/rpc.mountd
#9 0x00b66032 in mount_dispatch () from /usr/sbin/rpc.mountd
#10 0x00b5dfaf in mount_dispatch () from /usr/sbin/rpc.mountd
#11 0x00736f39 in svc_getreq_common_internal () from /lib/libc.so.6
#12 0x007368df in svc_getreqset_internal () from /lib/libc.so.6
#13 0x00b602cd in mount_dispatch () from /usr/sbin/rpc.mountd
#14 0x00b5d8f5 in main () from /usr/sbin/rpc.mountd
Are you using netgroups in the maps and don't have NIS+ configured at all
(likely neither NIS)?
If yes, then this was fixed recently:
2006-10-10 Ulrich Drepper <firstname.lastname@example.org>
* nis/nis_subr.c (nis_getnames): Add trailing dot to NIS_PATH
components which lack them.
* nis/nis_subr.c (nis_getnames): Make sure that we always return
at least one entry consisting of the parameter concatenated with
As a workaround, don't use nisplus for netgroup in nsswitch.conf if you don't
have NIS+ configured (e.g. change
in /etc/nsswitch.conf), or set some NIS/NIS+ domainname.
I am using nis.
Removing nisplus from the netgroup line solves the problem I had with mountd and
The line is now:
netgroup: nisplus nis
print on your box?
The problem should occur only if there is no dot in the domain name, not counting
the optional dot at the end.
The domainname is ase
So no dots whatsoever.
*** Bug 216195 has been marked as a duplicate of this bug. ***
*** Bug 234611 has been marked as a duplicate of this bug. ***
FC5 is no longer supported and FC6 updates and F7 have this fixed.