ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21012) Livy service check fails with wire encryption setup
Date Wed, 17 May 2017 04:10:05 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013482#comment-16013482
] 

Hudson commented on AMBARI-21012:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1534 (See [https://builds.apache.org/job/Ambari-branch-2.5/1534/])
AMBARI-21012. Fix Livy service check and alerts script with SSL enabled (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b6bc82b77766c2351cbaeec7760d44f006de2d7e])
* (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/alerts/alert_spark2_livy_port.py
* (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py
* (edit) ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/params.py
* (edit) ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/alerts/alert_spark_livy_port.py
* (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/service_check.py
* (edit) ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/service_check.py


> Livy service check fails with wire encryption setup
> ---------------------------------------------------
>
>                 Key: AMBARI-21012
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21012
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.5.1
>            Reporter: Yesha Vora
>            Assignee: Saisai Shao
>            Priority: Blocker
>             Fix For: 2.5.1
>
>
> Livy service check fails after enabling Wire encryption.  This issue exist for Livy_server
and Livy2_server both.
> STR:
> 1) Set up below properties in livy.conf to enable WE.
> {code}
> livy.ssl.trustStore <Truststore File>
> livy.ssl.trustStorePassword <Trustore passwd>
> livy.key-password <keypassword>
> livy.keystore <keystore file>
> livy.keystore.password <keystore passwd>{code}
> 2) Run Spark Service check.
> Spark service check with fail to validate Livy. It is using http port to connect to livy.
When Wire encryption is enabled, it should use https protocol to connect to livy. 
> {code:title=stderr}
> Traceback (most recent call last):
>   File "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
line 62, in <module>
>     SparkServiceCheck().execute()
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 322, in execute
>     method(env)
>   File "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/service_check.py",
line 59, in service_check
>     raise Fail(format("Connection to all Livy servers failed"))
> resource_management.core.exceptions.Fail: Connection to all Livy servers failed{code}
> {code:title=stdout}
> 2017-05-12 21:21:08,531 - Using hadoop conf dir: /usr/hdp/current/hadoop-client/conf
> 2017-05-12 21:21:08,551 - Execute['kinit -kt /etc/security/keytabs/xxx.headless.keytab
xxx@XXX; '] {'user': 'spark'}
> 2017-05-12 21:21:08,683 - Execute['kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
xxx@XXX; '] {'user': 'livy'}
> 2017-05-12 21:21:08,809 - Execute['curl -s -o /dev/null -w'%{http_code}' --negotiate
-u: -k https://xxxx:18481 | grep 200'] {'logoutput': True, 'tries': 5, 'try_sleep': 3}
> 200
> 2017-05-12 21:21:09,010 - Execute['curl -s -o /dev/null -w'%{http_code}' --negotiate
-u: -k http://xxxx:8999/sessions | grep 200'] {'logoutput': True, 'tries': 3, 'user': 'livy',
'try_sleep': 1}
> 2017-05-12 21:21:09,149 - Retrying after 1 seconds. Reason: Execution of 'curl -s -o
/dev/null -w'%{http_code}' --negotiate -u: -k http://xxx:8999/sessions | grep 200' returned
1. 
> 2017-05-12 21:21:10,286 - Retrying after 1 seconds. Reason: Execution of 'curl -s -o
/dev/null -w'%{http_code}' --negotiate -u: -k http://xxxx:8999/sessions | grep 200' returned
1.
> Command failed after 1 tries{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message