topic Re: Problem Updating NIS maps in Operating System - HP-UX

Problem Updating NIS maps

Andrew Kaplan — Tue, 10 Nov 2009 19:52:43 GMT

Hi there --

We are running NIS with one master server, and five slave servers in a single domain. I want to add several workstations to the domain, but when I access the netgroups files within SAM on the master server, I get the following error:

The NIS Netgroup source file /etc/netgroup has been modified since the map was built of pushed to slave servers. You cannot modify this map.

Prior to this issue, I have made sure to add new systems to the NIS groups as opposed to the local groups of the server. After each modification was made, a push was initiated within the SAM utility.

What may have caused this situation, and what can I do to correct the problem? Thanks.

Re: Problem Updating NIS maps

Steven E. Protter — Tue, 10 Nov 2009 22:01:07 GMT

Shalom,

Lets see some ypmake output.

Having the actual error message is always helpful.

SEP

Re: Problem Updating NIS maps

TTr — Tue, 10 Nov 2009 23:08:22 GMT

This is the netgroup file and not the group file. It simply is telling you the /etc/netgroup and the netgroup maps are already out of sync and that you have to sync them before modifying this file a second time.

Try "ypmake netgroup" on the master server. Then try editing the file. The error is coming from sam, it is not a standard NIS error, this type of check is not available in the NIS daemons.

Re: Problem Updating NIS maps

Andrew Kaplan — Wed, 11 Nov 2009 16:11:58 GMT

Hi there --

The problem appears to have solved itself because the error message has not re-appeared when I have gone through adding workstations to the domain.

There is one caveat: An e-mail notification was sent to me with the following entries:

Wed Nov 11 10:34:33 EST 2009
netgroup.byhost
nis server not registered at rtp37.
netgroup.byuser
nis server not registered at rtp37.
netgroup
nis server not registered at rtp37.

I checked the configuration of the workstation in question, and it is bound to the correct master server. The ypbind service is running, and nis logins are also connecting without issue on the workstation. I checked the log files on the server and client systems, but there was nothing apparent in either case.

What other steps should I take to correct this issue? Thanks.