string

NIS+ authentication failure
Cause
This is a Federated Naming Service message. The operation could not be completed
because the principal making the request could not be authenticated with the name
service involved.
Action
Run the nisdefaults(1) command to verify that you are identified as the correct
NIS+ principal. Also check that the system has specified the correct public key source.
See Also
For more information, see the authentication and authorization overview in the NIS+
and FNS Administration Guide.
nis_cachemgr: Error in reading NIS
cold start file :
’/var/nis/NIS_COLD_START’
Cause
After installing patches 104331-04 and 103612-33, nis_cachemgr(1M) failed to
come up. The symptoms are as follows during the reboot:
Sep 11 16:34:00 nis_cachemgr: Error in reading NIS cold start file :
’/var/nis/NIS_COLD_START’
and nis_cachemgr(1M) isn’t there after logging in. Trussing nis_cachemgr(1M)
showed that it is reading /var/nis/NIS_COLD_START and immediately reporting
an error. Neither reinitializing the client nor copying NIS_COLD_START helps.
Action
This is a timing problem. Put a sleep(1) before the NIS+ initialization in
/etc/init.d/rpc, after rpc.bind has been started. rpc.bind is slow about
128 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998