NFS Services Administrator's Guide

NIS+ Error Messages
Appendix A 365
The entry returned came from an object cache that has expired. This
means that the time to live value has gone to zero and the entry may
have changed. If the flag NO_CACHE was passed to the lookup function,
then the lookup function will retry the operation to get an unexpired
copy of the object.
This message is generated by the NIS+ error code constant
NIS_CACHEEXPIRED. See the nis_tables(3N) and nis_names(3N) man
pages for more information.
Callback: - select failed message number
CALLBACK_SVC: bad argument
An internal system call failed. In most cases this problem will correct
itself. If it does not correct itself, make sure that rpc.nisd has not been
aborted. If it has, restart it. If the problem reoccurs frequently, call your
HP support contact.
Cannot grow transaction log error string-variable
The system cannot add to the log file. The reason is indicated by the
variable. The most common cause of this message is lack of disk space.
See “If You Have Insufficient Memory or Disk Space” on page 321.
Cannot truncate transaction log file
An attempt has been made to checkpoint the log, and the rpc.nisd
daemon is trying to shrink the log file after deleting the checkpointed
entries from the log. See the ftruncate(2) man page for a description of
various factors that might cause this routine to fail. See also “If You
Have Insufficient Memory or Disk Space” on page 321.
Cannot write one character to transaction log, error message
An attempt has been made by the rpc.nisd daemon to add an update
from the current transaction into the transaction log, and the attempt
has failed for the reason given in the message which has been returned
by the function. Additional information may be obtained from the write
routine’s man page.
Can’t compile regular expression variable
Returned by the nisgrep command when the expression in keypat was
malformed.
Can’t find name’s secret key
Possible causes are as follows: