NFS Services Administrator's Guide

NIS+ Error Messages
Appendix A360
This section lists alphabetically the more common NIS+ error messages.
“Common Problems with NIS+” on page 315 describes various types of
problems and their solutions.
Error messages may appear in pop-up windows, shell tool command
lines, user console window, the syslog file, or in log files. You can raise or
lower the severity threshold level for reporting error conditions in your
/etc/syslog.conf file.
Some of the error messages documented in this chapter are documented
more fully in the appropriate man pages.
You may encounter error messages generated by Remote Procedure
Calls. These RPC error messages are not documented here.
In the most cases, the error messages that you see are generated by the
commands you issued or the table or directory your command is
addressing. However, in some cases an error message may be generated
by a server invoked in response to your command. (These messages
usually show in syslog.) For example, a “permission denied” message
most likely refers to you or the host you are using, but it could also be
caused by software on a server not having the correct permissions to
carry out some function passed on to it by your command or your host.
Similarly, some commands cause a number of different NIS+ objects to
be searched or queried. Any one of these objects could return an error
message regarding permissions, read-only state, not available, and so
forth. In such cases the message may or may not be able to inform you of
which object the problem occurred in.
If you cannot trace the cause of an error message to your command or
machine, consider the possibility that the message may have been
generated by a server in response to your command or in response to
some other NIS+ function.
In normal operation, the NIS+ software and servers make routine NIS+
function calls. Sometimes those calls fail and in doing so generate an
error message. It occasionally happens that before a client or server
processes your most recent command, some other NIS+ call fails and you
see the resulting error message. Such a message might appear as if it
were in response to your command, when in fact it is in response to some
other operation entirely.
A single NIS+ error message may have slightly different meanings
depending on which part of the NIS+ software generated the message.
For example, when the message “Not found” is generated by the nisls