topic Re: nis issues - in Operating System - HP-UX

nis issues -

lawrenzo — Thu, 12 Aug 2004 14:16:00 GMT

Hello,

very urgent!

NIS master # ypcat passwd |wc -l

output is 23

# cat /etc/passwd |wc -l
output is 1107

the nis master files seem to have become corrupt and we have many users not able to login

has anyone got any tips please

Re: nis issues -

Dave Olker — Thu, 12 Aug 2004 14:30:20 GMT

I assume the "cat /etc/passwd" output was from the NIS master, and that this system is configured to build the NIS passwd tables from the /etc/passwd file and not some other source. If that is the case, I'd try:

# touch /etc/passwd
# /var/yp/ypmake

Make sure the passwd maps are re-built and pushed to any slaves.

Dave

Re: nis issues -

Rick Garland — Thu, 12 Aug 2004 14:38:49 GMT

Also check to ensure that the /etc/passwd file is the passwd file used for NIS. Could be named passwd.yp or something else. Check your yp scripts that do the make and find out what is being pushed out to the slaves

Re: nis issues -

lawrenzo — Thu, 12 Aug 2004 16:10:04 GMT

The issue is that someone pushed out the maps from a client server corrrupting the environment.

We have logged a call with HP and they have advised to run ypinit -m,

during this process the system is asking for slaves

what commnad can be run to identify slave servers form the master>?

Thanks

Re: nis issues -

Dave Olker — Thu, 12 Aug 2004 16:17:53 GMT

The way I typically determine which systems were configured as slaves during the previous incarnation of "ypinit -m" is to un-makedbm the ypservers map.

Try this:

# cd /var/yp/
# makedbm -u ypservers

On my NIS master, this returns:

hpatcux1 hpatcux1
hpatcux2 hpatcux2
hpatcux4 hpatcux4
YP_LAST_MODIFIED 1092346033
YP_MASTER_NAME hpatcux1

This shows the master is "hpatcux1" and the slaves are "hpatcux2" and "hpatcux4".

Good luck,

Dave

Re: nis issues -

lawrenzo — Thu, 12 Aug 2004 20:37:49 GMT

Thanks everone,

After running commands with ypservers, it was evident that the master NIS was pointing to a slave server.

this happened because the ypmake was used on a server other than the master

To prevent this would I have to add something to the ypmake script to determine which server the command is being run on?

Many thanks

Re: nis issues -

Rick Garland — Fri, 13 Aug 2004 09:58:44 GMT

You could add to the ypmake script some logic that is testing the hostname value.
if [ `hostname` != ]
then
echo "not here!"
exit
fi

Could be as simple as this or as elaborate as you want.

Re: nis issues -

lawrenzo — Mon, 16 Aug 2004 01:19:30 GMT

Thank you all