Error: AAI startup fails with Kerberos KrbException (63) and JGit directory creation failure
search cancel

Error: AAI startup fails with Kerberos KrbException (63) and JGit directory creation failure

book

Article ID: 445165

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

Automation Analytics & Intelligence (AAI) fails to initialize during the startup process.
The logs indicate failures in creating internal configuration directories for JGit and an inability to acquire Kerberos service credentials for the database connection.

The following errors appear in the AAI logs:

text
ERROR [org.eclipse.jgit.util.FS$FileStoreAttributes] Cannot save config file 'FileBasedConfig[/ms/dist/environ/####/common/.config/jgit/config]': java.io.IOException: Creating directories failedERROR [org.jboss.stdio.AbstractLoggingWriter] KrbException: Fail to create credential. (63) - No service credsERROR [KerberosPrivilegedExceptionAction] JZ0GS: A Generic Security Services API exception occurred. The major error code is 13.

 

Environment

  • Product: Automic Automation Intelligence
  • Operating System: Linux / UNIX
  • Authentication: Kerberos / SSL

Cause

  1. The AAI service account lacks the necessary file system permissions to create or write to the .config/jgit directory within the application's home path.
  2. The application cannot acquire the Kerberos service credentials (TGT) required for the secure database connection.

Resolution

Follow these steps to resolve the startup failure:

  1. Verify Directory Permissions: Ensure the service account running the AAI process has full write access to the following path: /ms/dist/environ/####/common/.config/jgit Use chmod or chown to correct permissions if the directory cannot be created.

  2. Validate Kerberos Credentials:

    • Log in as the AAI service account.
    • Run klist to confirm a valid Ticket-Granting Ticket (TGT) exists.
    • Ensure the krb5.conf file is correctly referenced and accessible.
  3. Check SSL Key Accessibility: Verify that the SSL key file (e.g., tls_bare.pk8) is readable by the AAI process and is not corrupt.