My original message:
>
> We've suddenly developed this problem on our NIS master when nfsd tries
> to start:
>
> Oct 31 16:27:18 /usr/lib/nfs/nfsd[19942]: netdir_getbyname (transport
> udp, host/serv \1/nfs), Bad file number
> Oct 31 16:27:18 /usr/lib/nfs/nfsd[19942]: Cannot establish NFS service
> over /dev/udp: transport setup problem.
> Oct 31 16:27:18 /usr/lib/nfs/nfsd[19942]: netdir_getbyname (transport
> tcp, host/serv \1/nfs), Resource temporarily unavailable
> Oct 31 16:27:18 /usr/lib/nfs/nfsd[19942]: Cannot establish NFS service
> over /dev/tcp: transport setup problem.
> Oct 31 16:27:18 /usr/lib/nfs/nfsd[19942]: Could not start NFS service
> for any protocol. Exiting.
>
> I've seen these messages before, but can't remember what I did to fix
> the problem. :(
>
(The symptom was we were unable to automount directories from a specific
server,
but no other system in the building (400+) had the problem. We thought
the
cause was nfsd dying. -- Ed)
=============================================================================
>From Joel Lee <jlee@thomas.com>
You need to start nfs daemon. /etc/init.d/nfs.server start. If that
fails,
you need to make sure nfsd entry is in /etc/services.
=============================================================================
>From Casper Dik <casper@holland.Sun.COM>
The solaris FAQ says:
5.38) I can't run nfs: netdir_getbyname failure, /dev/udp: bind problem
For some reason the nfs service has disappeared from your
/etc/services file, NIS map or NIS+ table. You need to
have an entry like:
nfsd 2049/udp nfs # NFS server daemon
(clts)
nfsd 2049/tcp nfs # NFS server daemon
(cots)
If you use NIS+, you must make sure that the NIS+ entry is readable
for the machine executing nfsd.
If you used your SunOS 4.x services file, that would explain it:
SunOS 4.x doesn't have an entry for nfsd in /etc/services,
Solaris 2.x requires one.
This will usually not happen until you upgrade to Solaris 2.4 or
a later revision. Solaris 2.3 and earlier would always consult
/etc/services, regardless of what nsswitch.conf said.
/etc/services does contain the right NFS entries.
Solaris 2.4 and earlier don't have an entry for NFS over tcp, so
this error is also likely to occur on 2.5+ NFS servers that are
NIS/NIS+ clients of 2.4- servers. In 2.5 the error message will
look
like:
nfsd: Cannot get address for transport udp host \1 service nfs
nfsd: Cannot establish NFS service over /dev/udp: transport setup
problem.
nfsd: Cannot get address for transport tcp host \1 service nfs
nfsd: Cannot establish NFS service over /dev/tcp: transport setup
problem.
--- end of excerpt from the FAQ
=============================================================================
>From bismark@alta.Jpl.Nasa.Gov (Bismark Espinoza)
Check /etc/services, /etc/rcp, "rpcinfo -p hostname",
and mountd.
=============================================================================
The resolution:
It's true that nfsd and lockd were not in the /etc/services file. The
system
has been running fine for a long time, so I restored the file from 2
months ago.
The entries were missing from the file! I cannot explain this. I added
the
entries and rebooted for good measure. The problem did not go away. We
are
an NIS shop (not NIS+), and I discovered that our /etc/auto_master file
had entries
like this:
/home auto.home -rw,intr
/tools auto.tools -rw,intr
/vobs auto.vobs -rw,intr
/sysadmin auto.sysadmin -rw,intr
/net -hosts
I changed them to this:
/home auto_home -rw,intr
/tools auto_tools -rw,intr
/vobs auto_vobs -rw,intr
/sysadmin auto_sysadmin -rw,intr
/net -hosts
and the problem was corrected, without a reboot.
Thanks for the responses!
Ed
-- Ed Finch UNIX & ClearCase Administrator NASA's Earth Observation System, "Mission To Planet Earth""Of course NT may outsell Unix: It takes a roomful of NTs to match the power of one good Unix."
- Nicholas Petreley
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:08 CDT