NFS Services Administrator's Guide

NIS+ Error Messages
Appendix A 389
replica_update: nis dump result nis_perror error string
This message indicates a problem (identified by the error string) in
carrying out a dump to a replica. See “If a Replica Update Fails” on
page 326.
replica_update: number updates number errors
A status message indicating a successful update.
replica_update: WARNING: last_update (directoryname) returned 0!
An NIS+ process could not find the last update timestamp in the
transaction log for that directory. This will cause the system to perform a
full resync of the problem directory.
Results Sent to callback proc
This is simply a status message. No action need be taken.
This message is generated by the NIS+ error code constant
NIS_CBRESULTS. See the nis_tables(3N) man page for additional
information.
root_replica_update: update failed string-variable: could not fetch
object from master.
This message indicates a problem in carrying out a dump to a replica.
See “If a Replica Update Fails” on page 326.
Security exception on local system. UNABLE TO MAKE REQUEST.
This message may be displayed if a user has the same login ID as a
machine name. See “If a User Cannot Log In” on page 323.
Server busy, try again
The server was too busy to handle your request.
• For the add, remove, and modify operations, this message is returned
when the master server for a directory is either unavailable or in the
process of checkpointing its database.
• This message can also be returned when the server is updating its
internal state.
• In the case of nis_list, this message can be returned if the client
specifies a callback and the server does not have enough resources to
handle the callback.
Retry the command at a later time when the server is available.