Ralf W. Grosse-Kunstleve wrote, On 12/10/2008 10:58 AM:
Q1: network up before starting NIS? (watch out for NetworkMangler^H^H^H^Hager starting only after someone logs in.)
Yes. -- I had another machine in the past where this was a problem. NIS didn't work after boot, but when I manually restarted ypbind it started working. No such luck this time.
Q2: can you ping the NIS server or its backups?
Yes.
Q3: portmapper running?
chkconfig --list portmap
No, but it looks like portmap was superseded by rpcbind, which is running:
# /etc/init.d/rpcbind status
rpcbind (pid 2828) is running...
Also, rpcinfo reports several portmapper services.
another command to add to your yp test suite: ypwhich
# /etc/init.d/ypbind status
SIOCADDRT: File exists
ypbind (pid 22270) is running...
# ypwhich
ypwhich: Can't communicate with ypbind
This doesn't change if I stop both iptables and ip6tables (and then restart ypbind).
Another thing I tried: /etc/init.d/portreserve stop and chkconfig portreserve off
but that didn't make a difference either.
I also ran yum install ypserv, without actually turning it on. No luck still.
Ralf
top of a google[ ypwhich: Can't communicate with ypbind ]
http://docs.sun.com/app/docs/doc/802-3884/6i7ogkaot?a=view
I think you are at the "NIS Service Is Unavailable" stage of the document...
try the following, even if `/etc/init.d/ypbind status` returns a pid:
ps aux | grep ypbind
`/etc/init.d/ypbind status` may be reading a file from /var instead of
checking for a physically running program.
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
