SUMMARY: NIS binding problem on Solaris 8

From: Homan, Charles (NE) <Charles.Homan_at_GDC4S.Com>
Date: Thu Jun 27 2002 - 09:27:12 EDT
As usual, the blinding speed of this list is amazing!  I appreciate the fast
responses by John F Mclaughlin, Adrian Jones, Paul Guglielmino, and Charles
Gagnon.  Charles gave me the clue I needed, which was to change the
servername in /var/yp/binding/{domain}/ypservers from "nissvr" to
"localhost".  I did so, re-started ypbind, and everything was fine.  Oddly,
the Solaris 7 NIS server doesn't have this problem using it's regular

Thanks again!


OK, this is a weird one.  We have a Solaris 8 machine (E220R) which has
recently been set up as a NIS master.  Everything runs fine on the clients
(which are mixed Solaris 7/8) but the master will not bind to itself.  At
system boot time it prints the start of all of the yp processes, then the

  WARNING: Timed out waiting for NIS to come up

This is because when it runs through the /etc/rc2.d/S72inetsvc script it
comes to the section:

	for i in 1 2 3 4 5; do
		server=`/usr/bin/ypwhich 2> /dev/null`
		[ $? -eq 0 -a -n "$server" ] && return 0 || sleep 1
	return 1
domain=`/usr/bin/domainname 2>/dev/null`

[ -z "$domain" ] || [ ! -d /var/yp/binding/$domain ] || wait_nis || \
    echo "WARNING: Timed out waiting for NIS to come up" >& 2

So I have duly checked that:
1) domainname returns the right value ("aaaa.bbbbb.ccc", which is also in
2) /var/yp/binding/aaaa.bbbbb.ccc exists and looks OK

However when I run "ypwhich" I get the message:

"Domain aaaa.bbbbb.ccc not bound on nissvr."

which appears to be the root of the error message.  The question is, why
would that happen?

I compared everything I could think of to my other (Solaris 7) NIS server,
and everything looks the same other than the differences caused by being in
different domains.  I even moved aside /var/yp, created a new one, copied in
my Makefile, and ran "ypinit -m" again.  The clients were still happy after
that, but the master would still not bind.  I killed ypbind and re-started
it with the "-ypbindme" option; ypwhich still returned the same error, but
when I ran "ypset nissvr" it bound properly and ypwhich returned "nissvr" as

Am I missing something here?  Is there anything else I can check?

Thanks, and IWS!
Charles Homan
Systems Administrator
General Dynamics C4 Systems
77 "A" Street
Needham, MA 02494

The content of this e-mail message is not necessarily endorsed by General
Dynamics C4 Systems.
sunmanagers mailing list
Received on Thu Jun 27 09:32:41 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:47 EST