[SOLVED] nis master server and slave, client problem

robbtek · 08-23-2013, 04:19 AM

My server/client OS is CentOS.

I have setup a nis master and slave server.
Master and slave server works fine, but I have problem with client configuration.

Test example from client:

Code:

ypcat -h nis.master.my_domain passwd.byname | grep PIPPO
PIPPO:x:6106:6106::/home/PIPPO:/bin/bash

ypcat -h nis.slave.my_domain passwd.byname | grep PIPPO
PIPPO:x:6106:6106::/home/PIPPO:/bin/bash

I have setup a file /etc/yp.conf

Code:

domain my_domain server nis.master.my_domain
domain my_domain server nis.slave.my_domain

After that I restart service ypbind

Code:

/etc/init.d/ypbind restart

The is that client using slave instead of master server .

Code:

ypwhich 
nis.slave.my_domain

netnix99 · 08-26-2013, 09:18 AM

robbtek,

I am not sure I understand the problem... from the information that you posted, it appears the client is using NIS correctly... are you simply wondering why the client is using the slave server instead of the master?

robbtek · 08-26-2013, 10:19 AM

Quote:

Originally Posted by netnix99

are you simply wondering why the client is using the slave server instead of the master?

Yes, all client using slave instead of master nis server .
There is an error on the client configuration ?

Thanks

netnix99 · 08-26-2013, 10:56 AM

No, not at all.... technically, the NIS clients should talk to the slave-servers, and the NIS slave-servers get their information from the NIS master(s). However, if you have only one master and only one slave, and the slave server goes down, an NIS client connected to that server will try to find another NIS server that is up and/or faster, and it will connect to the master at that point.

You can test this by shutting down the interface on the slave-server and checking to see if the client fails over to the NIS master. If this is a production network, I would not suggest doing this when it could affect the users. I am not sure how long it takes for the clients to switch over.