topic Re: Trouble pushing out new NIS map in Operating System - HP-UX

Trouble pushing out new NIS map

Patrick Carlson — Wed, 12 Jul 2000 13:17:06 GMT

I cannot get a new map out to the slave servers.
I edited the Makefile on the master to build the new map (auto.asgp).
I edited the /etc/auto_master on the master and created the /etc/auto.asgp file on the master.
When I run make i get the following error.
updated auto.asgp
No response from ypxfr on arara
No response from ypxfr on dolphin
No response from ypxfr on margay
No response from ypxfr on odin
pushed auto.asgp

If I try ypxfr from the salve servers I get.
dolphin#>/usr/sbin/ypxfr auto.asgp
ypxfr: can't get master of auto.asgp
reason: no such map in server's NIS domain

From the master I can do a ypcat and get the contents of the auto.asgp map, but the slaves give the following error.

dolphin#>ypcat auto.asgp
ypcat: no such map in server's NIS domain
dolphin#>

Any help would be appreciated...

Re: Trouble pushing out new NIS map

Rick Garland — Wed, 12 Jul 2000 13:22:58 GMT

Are the systems you mentioned setup as slave NIS servers? The ypinit -s command was run on them? Sounds as if you do have the ypservers file setup but that can be from doing the ypinit -m command.

Check the /etc/rc.config.d/namesvrs file to ensure that the NIS services are to start at boot and that you have NIS_MASTER_SERVER, NIS_SLAVE_SERVER, and NIS_CLIENT set accordingly.

Re: Trouble pushing out new NIS map

Brian M. Fisher — Wed, 12 Jul 2000 13:36:24 GMT

Did you modify the /usr/sbin/ypinit script to add your new map to the MASTER_MAPS list?

The steps you need to follow should be similar to those in document ID: KBAN00000049
at:
http://us-support.external.hp.com/cki/bin/doc.pl/

Good Luck,
Brian
<*(((>< er

Re: Trouble pushing out new NIS map

Rick Garland — Wed, 12 Jul 2000 13:40:53 GMT

Forgot to mention, you can run the /sbin/init.d/nis.server start and /sbin/init.d/nis.client start to start up the services. The settings in the /etc/rc.config.d/namesvrs file are for when the system boots. Don't need to boot to get the services running.

For yp slaves, you can do ps -ef | grep yp and see the process for ypbind, ypxfer, and
ypserv - for clients only you will see just ypbind.

Re: Trouble pushing out new NIS map

Patrick Carlson — Wed, 12 Jul 2000 13:41:54 GMT

The slave NIS servers do receive updates of the existing maps (auto.home, auto.prod, etc).

Since the creation of the new map on the Master server I have not run ypinit -s again on the Slave's. Do I need to do this? Why can't I just do a ypxfr from the Slave's to pull the new map over?

Thanks for your quit response

Re: Trouble pushing out new NIS map

Rick Garland — Wed, 12 Jul 2000 13:47:42 GMT

ypinit -s needs to be done to tell the system that it is going to be a NIS slave server. This will transfer the NIS maps to these servers and allow the ypxfer process to keep track and update the NIS maps as they are modified.

You will probably want all systems as NIS_CLIENTS and set the NIS_MASTER_SERVER and NIS_SLAVE_SERVER as needed.