Event ID 12288 — Server for NIS Functionality -- Push Service
Updated: December 16, 2008
Applies To: Windows Server 2008 R2
Server for NIS synchronizes and propagates NIS map changes to UNIX-based NIS subordinate (also known as slave) servers. The NIS master server supports the following transfer modes:
- Periodic transfer of NIS maps
- On-demand transfer of NIS maps to subordinate servers
Typically, NIS maps are transferred to subordinate servers upon change by using the make utility. The Windows-based NIS server does not use make; instead, the server pushes immediately.
Subordinate NIS servers can request transfer of maps at any time. Server for NIS Server Functionality -- Push Service provides information to help you interpret system messages indicating the functional state of the NIS map push service.
|Product:||Windows Identity Management for UNIX|
|Message:||Warning: yppush failure. Domain: %1, Map Name: %2, Server: %3, Status: %4.|
Check connection of UNIX-based subordinate server
This event can be ignored; map updating should occur following the next refresh.
If the problem persists, or updates do not occur after more than one refresh cycle for a particular UNIX-based NIS subordinate server, then on the UNIX-based subordinate server verify the following:
- The power to the server is connected, the server is operational, and it is connected to the network.
- You can ping the Windows-based Server for NIS master server from the UNIX-based subordinate server.
- This UNIX-based computer is properly configured as an NIS subordinate server with a Windows-based computer running Server for NIS as the master server. For more information about properly configuring a UNIX-based subordinate server to work with Server for NIS, see "Configuring a UNIX NIS Server to Use Server for NIS as the Master Server" in the Identity Management for UNIX Help.
Configure a UNIX NIS server to use Server for NIS as the master server
To configure a UNIX NIS server to use Server for NIS as the master server:
- Migrate maps from the UNIX master NIS server.
- Transfer the maps from the old master server to other subordinate NIS servers by providing the name of the new Server for NIS for each map. At a command prompt, type: ypxfr –hnewserver mapname, where newserver is the name of the new NIS master server, and mapname is the name of the map to be transferred.
- Run this command for each map on each subordinate server.
After completing this procedure, UNIX subordinate servers should recognize the new Server for NIS master server.
Server for NIS push service functionality can be verified by pushing maps to subordinate servers.
To test the functionality of the push service, change a map entry for an NIS user (you can use the users nisadmin or AdminUI for the purposes of your test). Wait for the refresh interval to elapse, and then view the NIS map stored on a UNIX-based subordinate of the master server. If your changed values are reflected in the NIS map stored on the UNIX-based NIS subordinate server, then the Server for NIS master server is functioning as expected.
In the absence of any of the following error messages, the push service is functioning normally. If any of these messages occur, the push service can continue working, but warning conditions exist.
- IDMU Server for NIS event 8198
- IDMU Server for NIS event 12288
- IDMU Server for NIS event 12289