NFS Services Administrator's Guide

NIS+ Error Messages
Appendix A 361
command, it means that there are no NIS+ objects that have the
specified name, but when it is generated by the nismatch command it
means that no table entries were found that meet the search criteria.
The error messages in this appendix are sorted alphabetically according
to the following rules:
• Capitalization is ignored. Thus, messages that begin with “A” and “a”
are alphabetized together.
• Nonalphabetic symbols are ignored. Thus, a message that begins
with _svcauth_des is listed with the other messages that begin with
the letter “S”.
• Many messages contain variable strings such as user IDs, domain
names, host names, and so forth. Variables are ignored when sorting
the messages. For example, the message Sales: is not a table
would be listed in this appendix as name: is not a table and
would be alphabetized under the letter ‘I’ for the first non-variable
letter.
• Error messages that begin with asterisks, such as **ERROR:
domainname does not exist are generated by the NIS+
installation and setup scripts. They are alphabetized according to
their first letter, ignoring the asterisks.
abort_transaction: Failed to action NIS+_objectname
The abort_transaction routine failed to back out of an incomplete
transaction due to a server crash or some other unrecoverable error.
abort_transaction: Internal database error
abort_transaction: Internal error, log entry corrupt NIS+_objectname
These two messages indicate corruption in a namespace database or log.
add_cleanup: Cant allocate more rags.
add_pingitem: Couldn’t add directoryname to pinglist (no memory)
These messages indicate that your system is running low on available
memory. See “If You Have Insufficient Memory or Disk Space” on
page 321.
add_update: Attempt add transaction from read only child.
add_update Warning: attempt add transaction from read only child
An attempt by a read-only child rpc.nisd process to add an entry to a
log. An occasional appearance of this message in a log is not serious. If
this message appears frequently, call your HP support contact.