NFS Services Administrator's Guide

NIS+ Error Messages
Appendix A382
NIS+ operation failed
This generic error message should be rarely seen. Usually it indicates a
minor software problem that the system can correct on its own. If it
appears frequently, or if it appears to indicate a problem that the system
is not successfully dealing with, call your HP support contact.
This message is generated by the NIS+ error code constant NIS_FAIL.
String-variable: NIS+ server busy try again later.
NIS+ server busy try again later.
Try the command later. See “If a Replica Update Fails” on page 326 or
“To Improve NIS+ Performance” on page 338.
NIS+ server for string-variable not responding still trying
NIS+ server not responding
See “To Improve NIS+ Performance” on page 338.
NIS+ server needs to be checkpointed. Use nisping -C domainname
This message is generated at the LOG_CRIT level on the server’s system
log. It indicates that the log is becoming too large. Use nisping -C
domainname to truncate the log by checkpointing. Checkpoint
immediately! Do not wait.
See “If nisping -C Fails or Transaction Logs Are Not Truncated” on
page 325.
NIS+ servers unreachable
This soft error indicates that a server for the desired directory of the
named table object could not be reached. This can occur when there is a
network failure or the server has crashed. A new attempt may succeed.
See the description of the HARD_LOOKUP flag in the nis_tables(3N) and
nis_names(3N) man pages.
This message is generated by the NIS+ error code constant
NIS_NAMEUNREACHABLE. See the nis_tables(3N) and nis_names(3N)
man pages for additional information.
NIS+ service is unavailable or not installed
This message is generated by the NIS+ error code constant
NIS_UNAVAIL.
NIS+: write ColdStart File: xdr_directory_obj failed
The most likely causes for this message are as follows: