You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Sebastian Toader (JIRA)" <ji...@apache.org> on 2016/02/24 14:30:18 UTC

[jira] [Created] (AMBARI-15158) Resource Manager fails to start: IOException: /ats/active does not exist

Sebastian Toader created AMBARI-15158:
-----------------------------------------

             Summary: Resource Manager fails to start: IOException: /ats/active does not exist
                 Key: AMBARI-15158
                 URL: https://issues.apache.org/jira/browse/AMBARI-15158
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.2.1
            Reporter: Sebastian Toader
            Assignee: Sebastian Toader
            Priority: Critical
             Fix For: 2.2.1


Resource Manager fails to start when cluster is provisioned with blueprint for the first time. After RM restart it works so it could be a sync issue. Log and blueprint attached.

Config recommendation strategy is ONLY_STACK_DEFAULTS_APPLY



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)