NFS Services Administrator's Guide

NIS+ Error Messages
Appendix A368
Could not generate netname
The secure RPC software could not generate the secure RPC netname for
your user ID when performing a keylogin. This could be due to the
following causes:
• You do not have Local credentials in the NIS+ cred table of the host’s
home domain.
• You have a local entry in /etc/passwd with a user ID that is
different from the user ID you have in the NIS+ passwd table.
String-variable: could not get secret key for 'name'
Possible causes are as follows:
• You may have incorrectly typed the password.
• There may be no entry for name in the cred table.
• NIS+ could not decrypt the key (possibly because the entry might be
corrupt).
•The /etc/nsswitch.conf file may have the wrong publickey policy.
It may be directing the query to a local password in an /etc/passwd
file that is different from the NIS+ password recorded in the cred
table.
See “If You Have Authentication or Permissions Problems” on page 318.
Couldn’t fork a process!
The server could not fork a child process to satisfy a callback request.
This is probably caused by your system reaching its maximum number of
processes. You can kill some unneeded processes, or increase the number
of processes your system can handle. See “If You Receive an “Unable to
Fork” Message” on page 322.
Couldn't parse access rights for column string-variable
This message is usually returned by the nistbladm -u command when
something other than a plus sign (+), a minus sign (-), or an equal sign
(=) is entered as the operator. Other possible causes are failure to
separate different column rights with a comma, or the entry of
something other than r, d, c, or m for the type of permission. See the
nistbladm(1) man page to check the syntax for this type of entry error. If
everything is entered correctly and you still get this error, the table
might have been corrupted.