You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2015/10/26 18:29:27 UTC
[jira] [Resolved] (AMBARI-13565) Oozie alert appears after enabling
NN HA, moving NameNode and enabling security
[ https://issues.apache.org/jira/browse/AMBARI-13565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk resolved AMBARI-13565.
--------------------------------------
Resolution: Fixed
Committed to trunk and branch-2.1
> Oozie alert appears after enabling NN HA, moving NameNode and enabling security
> -------------------------------------------------------------------------------
>
> Key: AMBARI-13565
> URL: https://issues.apache.org/jira/browse/AMBARI-13565
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.3
>
>
> Steps:
> 1. Deploy cluster.
> 2. Enable NameNode HA.
> 3. Move NameNode to another host.
> 4. Enable Security.
> Result: Oozie has CRIT "Oozie Server Status" alerts, appearing and
> disappearing with period about 5 minutes. Message of alert:
>
>
>
> Execution of 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -oozie http://ambari-us-rhe6-haenabling-2.novalocal:11000/oozie -status' returned 255. Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server. No of retries = 1. Exception = Could not authenticate, GSSException: No valid credentials provided (Mechanism level: Ticket expired (32))
>
> Cluster: <http://172.22.89.94:8080/>, lifetime: +120h.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)