ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <>
Subject [jira] [Created] (AMBARI-14847) Concurrent kinit Commands Cause Alerts To Randomly Trigger
Date Fri, 29 Jan 2016 18:57:39 GMT
Jonathan Hurley created AMBARI-14847:

             Summary: Concurrent kinit Commands Cause Alerts To Randomly Trigger
                 Key: AMBARI-14847
             Project: Ambari
          Issue Type: Bug
          Components: ambari-agent
    Affects Versions: 2.0.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             Fix For: 2.2.2

The alerts framework on each Ambari Agent runs alerts in a threadpool when the job triggers.
This can cause the following error to randomly appear and the alert to go CRITICAL:

 Connection failed to http://nat-rare-21-dvitiiuk-2-5.novalocal:8088 (Execution of '/usr/bin/kinit
-l 5m -c /var/lib/ambari-agent/tmp/web_alert_cc_f3f99363c3b7d1667f1287ce3a35aa52 -kt /etc/security/keytabs/spnego.service.keytab
HTTP/nat-rare-21-dvitiiuk-2-5.novalocal@EXAMPLE.COM > /dev/null' returned 1.

kinit: Internal credentials cache error while storing credentials while getting initial credentials)

The alerts would randomly go CRITICAL at the end of their ticket expiration time only to become
OK again shortly after. 

The cause is that the {{kinit}} command being executed to create new credentials cannot be
run concurrently for the same user. 

This message was sent by Atlassian JIRA

View raw message