You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2016/01/29 20:41:39 UTC
[jira] [Updated] (AMBARI-14847) Concurrent kinit Commands Cause
Alerts To Randomly Trigger
[ https://issues.apache.org/jira/browse/AMBARI-14847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-14847:
-------------------------------------
Attachment: AMBARI-14847.patch
> Concurrent kinit Commands Cause Alerts To Randomly Trigger
> ----------------------------------------------------------
>
> Key: AMBARI-14847
> URL: https://issues.apache.org/jira/browse/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
>
> Attachments: AMBARI-14847.patch
>
>
> 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:
> {noformat}
> 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)
> {noformat}
> 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
(v6.3.4#6332)