This section describes problems that do not fit any of the previous categories.
You may need to know whether a given host is running NIS+. A script may also need to determine whether NIS+ is running.
You can assume that NIS+ is running if:
nis_cachemgr is running.
The host has a /var/nis/NIS_COLD_START file.
Error messages indicating that the update was not successfully complete. (Note that the message: replica_update: number updates number errors indicates a successful update.)
Any of the following error messages indicate that the server was busy and that the update should be rescheduled:
These messages indicate that there was some other problem:
replica_update: error result was ...
(If rpc.nisd is being run with the -C (open diagnostic channel) option, additional information may be entered in either the master server or replica server's system log.
These messages indicate possible problems such as:
The server is out of child processes that can be allocated.
A read-only child process was requested to dump.
Another replica is currently resynching.
Check both the replica and server's system log for additional information. How much, if any, additional information is recorded in the system logs depends on your system's error reporting level, and whether or not you are running rpc.nisd with the -C option (diagnostics).
In most cases, these messages indicate minor software problems which the system is capable of correcting. If the message was the result of a command, simply wait for a while and then try the command again. If these messages appear often, you can change the threshold level in your /etc/syslog.conf file. See the syslog.conf man page for details.