[ Previous | Next | Table of Contents | Index | Library Home | Legal | Search ]

Network Information Services (NIS and NIS+) Guide

Troubleshooting Other NIS+ Problems

This section describes problems that do not fit any of the previous categories.

How to Tell if NIS+ Is Running

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 check if NIS+ is running by any of the following methods:

Replica Update Failure

Symptoms appear as error messages indicating that an update did not complete successfully. (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 are generated by, or in conjunction with, the NIS+ error code constant: NIS_DUMPLATER.)

The following messages indicate that there was some other problem:

(If rpc.nisd is being run with the -v (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:

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 -v 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.

[ Previous | Next | Table of Contents | Index | Library Home | Legal | Search ]