topic NIS client problem in Operating System - HP-UX

NIS client problem

V. Nyga — Mon, 14 Apr 2003 07:09:23 GMT

Hi all,

I've a problem with a NIS client at UX 11.0.
I've one NIS server at UX 10.20 and a NIS slave server at UX 10.20.
My client always take the slave server as NIS server but he don't get the NIS infos.

What can I do to direct it to the right server?

Do you need more infos?

Volkmar

Re: NIS client problem

Robert-Jan Goossens_1 — Mon, 14 Apr 2003 07:26:46 GMT

Hi Volkmar,

take a look at next docs,

How to use ypinit -c on HP NIS client to bind to specific server

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062922422

After upgrade to 11.0 - ypbind will not bind to remote NIS Server

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063248506

Hope this is what you are looking for,

Robert-Jan.

Re: NIS client problem

S.K. Chan — Mon, 14 Apr 2003 07:32:57 GMT

Is your client's binding at broadcast level ? If it is then it's perfectly normal, ie which ever slave or master that responded to the ypbind request first would serve it. At broadcast level the broadcast ip addr for the slave and client show be the same.
# ifconfig lan0
on the slave & client would show you that. Check you slave to see if it's getting the latest distributed maps or not (/var/yp/domainname>). How's your slave binding to the master ? Attach the /etc/rc.config/namesvrs file would be of help.

Re: NIS client problem

V. Nyga — Mon, 14 Apr 2003 08:12:55 GMT

Hi again,

sorry one mistake: client is also UX10.20.
Attached namesrvs of the slave NIS server.
I think I twisted NIS at the slave last week.

How do I use ypinit so the slave gets its NIS infos again?

Volkmar

Re: NIS client problem

Ravi_8 — Mon, 14 Apr 2003 09:28:14 GMT

Hi,

set the IP of server at YPSET_ADDR="x.x.x.x" in namesvrs file.

#sbin/init.d/nis.client stop/start
should do

Re: NIS client problem

S.K. Chan — Mon, 14 Apr 2003 10:07:42 GMT

If your slave resides in the same subnet as your master there is no need to do anything to the file "namesvrs". What you can do is rebuild the NIS DB on your slave. On your slave server run ..
# /sbin/init.d/nis.client stop
# /sbin/init.d/nis.server stop
# cd /var/yp
# mv foo foo.old
==> Renaming the existing dir where the NIS db sits.
# domainname foo
# /usr/sbin/ypinit -s
==>> Copy the DBs from Master
# ll foo
=> Make sure DBs are there.
# /sbin/init.d/nis.server start
# /sbin/init.d/nis.client start
Check the processes and you should have 3 processes running. There are ..
o /usr/lib/netsvc/yp/ypserv
o /usr/sbin/ypxfrd
o /usr/lib/netsvc/yp/ypbind

Re: NIS client problem

S.K. Chan — Mon, 14 Apr 2003 10:12:21 GMT

I'm sorry .. continuation to the above..
If your slave is NOT in the same subnet as your master then you need to make additional edit to "namesvrs" on the slave to look like this ..
..
YPBIND_OPTIONS="-ypset"
......
YPSET_ADDR=""
...
Then repeat the above procedure to rebuild your NIS DBs.

Re: NIS client problem

V. Nyga — Mon, 14 Apr 2003 10:58:47 GMT

Hi S.K. Chan,

thanks a lot slave and client is running again.
foo.old can be removed?
One error message:
ypxfr: can't get order number for map ethers.byaddr from ypserv at 160.1.3.22
reason: no such map in server's NIS domain

Do you know what it means?
Something serious?

Thanks again
Volkmar

Re: NIS client problem

S.K. Chan — Mon, 14 Apr 2003 13:21:47 GMT

Hi Volkmar, yes you can remove the old NIS db "foo.old". When you run ypinit -s to trnafer or copy the DB from the master it could not find ether.byaddr map in the master and hence that map is not transferred. If you lok at the sript /usr/sbin/ypinit you'll see what maps are managed by NIS. See settings in "MASTER_MAPS" and "ALL_MAPS". This is not a problem and I bet you're not using that file at all.

Re: NIS client problem

Jatinder Cheema — Thu, 01 May 2003 14:48:17 GMT

Hi All,

Sorry its solved, what had happened was that the masters config was copied over, /etc/passwd/ was infact for the master server, it was missing the +::0:0::: string at the end of the file. So it was infact looking at the local passwd file only.

Thanks for all the speedy help.

Jat

Re: NIS client problem

V. Nyga — Thu, 21 Sep 2006 04:30:18 GMT

solution above