You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2015/09/24 06:37:04 UTC
[jira] [Commented] (AMBARI-13168) Ambari unable to start Yarn or
Hive after Ranger integration
[ https://issues.apache.org/jira/browse/AMBARI-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905800#comment-14905800 ]
Gautam Borad commented on AMBARI-13168:
---------------------------------------
[~harisekhon] If you can provide with the following info it would help to debug this further:
* Whether Ranger service was up and running without any alert during the time of restart of Yarn/HiveServer. Ranger is required to be up, since the agent will try to create Ambari admin user and default repo in Ranger
* Verify the following two properties matches with the Ranger Admin credentials (You can try to login to Ranger Admin with this credentials just to make sure):
** Advanced ranger-env -> admin_username
** Advanced ranger-env -> admin_password
* Attach the file of the request that failed. You can get the path from the popup itself ( the above log is a part of it, if you provide the entire log that would really help)
* Attach the catalina.out and xa_portal.log of Ranger Admin ( will be on the ranger-host@/var/log/ranger/admin OR ranger-host@/usr/hdp/current/ranger-admin/ews/logs)
> Ambari unable to start Yarn or Hive after Ranger integration
> ------------------------------------------------------------
>
> Key: AMBARI-13168
> URL: https://issues.apache.org/jira/browse/AMBARI-13168
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Environment: HDP 2.3 + Kerberos + Ranger
> Reporter: Hari Sekhon
> Priority: Blocker
>
> After deploying Ranger via Ambari and enabling the Yarn Ranger plugin it seems Ambari is no longer able to start the Yarn Resource Manager:
> {code}Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py", line 221, in <module>
> Resourcemanager().execute()
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 218, in execute
> method(env)
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 459, in restart
> self.start(env)
> File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/resourcemanager.py", line 115, in start
> setup_ranger_yarn() #Ranger Yarn Plugin related calls
> File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/setup_ranger_yarn.py", line 41, in setup_ranger_yarn
> api_version = 'v2'
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/setup_ranger_plugin_xml.py", line 82, in setup_ranger_plugin
> policy_user)
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions_v2.py", line 95, in create_ranger_repository
> ambari_ranger_admin, ambari_ranger_password = self.create_ambari_admin_user(ambari_ranger_admin, ambari_ranger_password, format("{admin_uname}:{admin_password}"))
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions_v2.py", line 189, in create_ambari_admin_user
> response = json.loads(result.read())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded{code}
> The Ambari server log shows the following:
> {code}21 Sep 2015 14:54:40,130 INFO [qtp-ambari-agent-9264] HeartBeatHandler:567 - Updating applied config on service YARN, component NODEMANAGER, host <fqdn>
> 21 Sep 2015 14:54:44,623 WARN [qtp-ambari-agent-9264] HeartBeatHandler:603 - Operation failed - may be retried. Service component host: RESOURCEMANAGER, host: <fqdn> Action id113-0
> 21 Sep 2015 14:54:44,623 ERROR [qtp-ambari-agent-9264] ServiceComponentHostImpl:906 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=RESOURCEMANAGER, hostName=<fqdn>, currentState=INSTALLED, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED
> 21 Sep 2015 14:54:44,623 WARN [qtp-ambari-agent-9264] HeartBeatHandler:621 - State machine exception. Invalid event: HOST_SVCCOMP_OP_FAILED at INSTALLED
> 21 Sep 2015 14:54:44,811 WARN [ambari-action-scheduler] ActionScheduler:311 - Operation completely failed, aborting request id:113
> 21 Sep 2015 14:54:44,811 ERROR [ambari-action-scheduler] ServiceComponentHostImpl:906 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=APP_TIMELINE_SERVER, hostName=<fqdn>, currentState=STARTED, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED
> 21 Sep 2015 14:54:44,811 ERROR [ambari-action-scheduler] ServiceComponentHostImpl:906 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=NODEMANAGER, hostName=<fqdn>, currentState=STARTED, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED
> 21 Sep 2015 14:54:44,811 ERROR [ambari-action-scheduler] ServiceComponentHostImpl:906 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=RESOURCEMANAGER, hostName=<fqdn>, currentState=INSTALLED, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED
> 21 Sep 2015 14:54:44,811 ERROR [ambari-action-scheduler] ServiceComponentHostImpl:906 - Can't handle ServiceComponentHostEvent event at current state, serviceComponentName=YARN_CLIENT, hostName=<fqdn>, currentState=INSTALLED, eventType=HOST_SVCCOMP_OP_FAILED, event=EventType: HOST_SVCCOMP_OP_FAILED
> 21 Sep 2015 14:54:44,814 INFO [ambari-action-scheduler] ActionDBAccessorImpl:176 - Aborting command. Hostname <fqdn> role YARN_CLIENT requestId null taskId 792 stageId null{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)