topic Re: NIS: server not responding in Operating System - HP-UX

NIS: server not responding

Alan Meyer_4 — Mon, 18 Jul 2005 09:09:15 GMT

I am encountering a problem where ypset does not seem to be working.. I have a server which does not have an NIS slave server on it’s subnet, so I have forced the NIS binding with the following in /etc/rc.config.d/namesvrs:

YPBIND_OPTIONS="-ypsetme"
YPSET_ADDR="10.48.154.18"

Ocassionally, I encounter a problem where the server does not resolve NIS users and the following error appears on the system console:

NIS: server not responding for domain “domname”; still trying
07.18 08:13:46 nodename pid=2814 /usr/lib/netsvc/yp/bind

When this occurs login’s become disabled to the server and the only work around is to login to the console and stop/start nis.client

Has anyone run across this? What is causing this?

Thank you,
-alan

Re: NIS: server not responding

Ermin Borovac — Mon, 18 Jul 2005 21:15:34 GMT

It looks like your network connection was temporarily down and when the connection was restored ypbind went back to the broadcast method.

You can try the following instead.

* Run 'ypinit -c' on the client to create /var/yp/binding//ypservers file which should contain the list of NIS servers this client should bind to.
* Remove ypsetme from YPBIND_OPTIONS and IP address from YPSET_ADDR in /etc/rc.config.d/namesvrs

This will make ypbind on the client bind to IP addresses in ypservers file. Make sure ypbind is not started with ypset/ypsetme or broadcast options. With this method when network connection goes down you shouldn't need to restart NIS client processes.

Re: NIS: server not responding

Alan Meyer_4 — Tue, 19 Jul 2005 07:11:17 GMT

The problem though is that this subnet does not have a slave server. So wouldn't I need to hard code a bind address then?

Re: NIS: server not responding

Paul Cross_1 — Tue, 19 Jul 2005 07:49:12 GMT

That's what ermin was explaining how to do. You need to create and populate the ypservers file using his procedure.

Re: NIS: server not responding

Alan Meyer_4 — Tue, 19 Jul 2005 08:00:22 GMT

Is this something that has to be done when the NIS client is down?

I tried the ypinit -c command and it did not work returning messages that only ypinit -m or -s were viable switches.

Re: NIS: server not responding

Alan Meyer_4 — Wed, 20 Jul 2005 13:23:42 GMT

The key is to use ypinit -c as specified above. But, the version of ypinit that is loaded in /usr/sbin does not allow for ypinit -c functionality. According to HP Document id: UNFSKBRC00008619, you need to copy the file /usr/newconfig/usr/sbin/ypinit to /usr/sbin in order for ypinit -c to work.

You also have to have the following patches loaded in order to have this functionality.

11.0 PHNE_24034
11.11 PHNE_24910

Thanks for your help