Incorrect Kerberos password You entered the wrong password or your password was recently changed and has not yet been propagated to the secondary authentication server you are using. If you incorrectly entered your password, just try again. The recovery action in this situation is to force the propagation of database changes without waiting for the normal cron process. Issue the k4init command, specifying as your principal name any user principal listed in the root user's .klogin file on the primary server. The administrative principal name that was used to set up authentication on the primary server can be used, or any other user principal the administrator has subsequently added to the file.
Successful propagation is reported by a message for each secondary server hostname.
The authentication service also provides commands that can be used to allow background processes to invoke authenticated services, when the k4init command cannot be issued, because no user is logged in to the client AIX system. Various SP installation and system management scripts use the rcmdtgt command to identify themselves to the authentication system and thereby obtain a ticket-granting ticket. You must, if authorized, log in as root and retry the failing task. The server key file does not exist. Versions An administrator running as root can compare the versions of the server keys in the server key file and the database using the ksrvutil or k4list command on the server system and by examining a dump of the authentication database on the primary authentication server, when AFS is not being used.