ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "amarnath reddy pappu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21538) Zeppelin quick links and service check failing in SSL enabled environment.
Date Thu, 20 Jul 2017 19:50:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

amarnath reddy pappu updated AMBARI-21538:
------------------------------------------
    Description: 
>From Ambari documentation (https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_support-matrices/content/ch_matrices-ambari.html),
we confirm HDP-2.6.1 compatibility with Ambari 2.5.0. However, when HDP 2.6.1 is deployed
using Ambari 2.5.0.3 and upon enabling SSL for Zeppelin, we observe that Zeppelin service
check and quick link would fail. This may be due to introduction of two distinct properties
for a secure (SSL enabled) and non secure links as described here, https://issues.apache.org/jira/browse/ZEPPELIN-1321
. The two properties are,

"zeppelin.server.port". This property is by default set to 9995 which is used to access the
server via a webUI

"zeppelin.server.ssl.port". This property was introduced to be used when SSL was enabled.
Hence, UI would have to accessed for the port that was defined for this property. Default
is 8443.


With default settings, we see that.
Zeppelin Quick links would point to 9995 port. But, the service would be listening on 8443
port.

Zeppelin service check fails with below stack trace,


{code:java}
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/service_check.py",
line 40, in <module>
    ZeppelinServiceCheck().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 314, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/service_check.py",
line 37, in service_check
    logoutput=True)
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__
    self.env.run()
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160,
in run
    self.run_action(resource, action)
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124,
in run_action
    provider_action()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line
262, in action_run
    tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, in inner
    result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in
checked_call
    tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in
_call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in
_call
    raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o /dev/null -w'%{http_code}'
--negotiate -u: -k https://<HOSTNAME>:9995 | grep 200' returned 1.
{code}


In Summary:
Ambari is always using "zeppelin.server.port" port for Quicklinks where as Zeppelin server
is started on "zeppelin.server.ssl.port" port number. this needs to be fixed. 

Workaround that could be used is to set both the properties, "zeppelin.server.port" and "zeppelin.server.ssl.port"
to 8443.

  was:
>From Ambari documentation (https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_support-matrices/content/ch_matrices-ambari.html),
we confirm HDP-2.6.1 compatibility with Ambari 2.5.0. However, when HDP 2.6.1 is deployed
using Ambari 2.5.0.3 and upon enabling SSL for Zeppelin, we observe that Zeppelin service
check and quick link would fail. This may be due to introduction of two distinct properties
for a secure (SSL enabled) and non secure links as described here, https://issues.apache.org/jira/browse/ZEPPELIN-1321
. The two properties are,

"zeppelin.server.port". This property is by default set to 9995 which is used to access the
server via a webUI

"zeppelin.server.ssl.port". This property was introduced to be used when SSL was enabled.
Hence, UI would have to accessed for the port that was defined for this property. Default
is 8443.

With default settings, we see that.
Zeppelin Quick links would point to 9995 port. But, the service would be listening on 8443
port.

Zeppelin service check fails with below stack trace,


{code:java}
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/service_check.py",
line 40, in <module>
    ZeppelinServiceCheck().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 314, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/service_check.py",
line 37, in service_check
    logoutput=True)
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__
    self.env.run()
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160,
in run
    self.run_action(resource, action)
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124,
in run_action
    provider_action()
  File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line
262, in action_run
    tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, in inner
    result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in
checked_call
    tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in
_call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in
_call
    raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o /dev/null -w'%{http_code}'
--negotiate -u: -k https://<HOSTNAME>:9995 | grep 200' returned 1.
{code}



Workaround that could be used is to set both the properties, "zeppelin.server.port" and "zeppelin.server.ssl.port"
to 8443.


> Zeppelin quick links and service check failing in SSL enabled environment.
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-21538
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21538
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Krishnama Raju K
>              Labels: easyfix
>
> From Ambari documentation (https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_support-matrices/content/ch_matrices-ambari.html),
we confirm HDP-2.6.1 compatibility with Ambari 2.5.0. However, when HDP 2.6.1 is deployed
using Ambari 2.5.0.3 and upon enabling SSL for Zeppelin, we observe that Zeppelin service
check and quick link would fail. This may be due to introduction of two distinct properties
for a secure (SSL enabled) and non secure links as described here, https://issues.apache.org/jira/browse/ZEPPELIN-1321
. The two properties are,
> "zeppelin.server.port". This property is by default set to 9995 which is used to access
the server via a webUI
> "zeppelin.server.ssl.port". This property was introduced to be used when SSL was enabled.
Hence, UI would have to accessed for the port that was defined for this property. Default
is 8443.
> With default settings, we see that.
> Zeppelin Quick links would point to 9995 port. But, the service would be listening on
8443 port.
> Zeppelin service check fails with below stack trace,
> {code:java}
> Traceback (most recent call last):
>   File "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/service_check.py",
line 40, in <module>
>     ZeppelinServiceCheck().execute()
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 314, in execute
>     method(env)
>   File "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/service_check.py",
line 37, in service_check
>     logoutput=True)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155,
in __init__
>     self.env.run()
>   File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line
160, in run
>     self.run_action(resource, action)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line
124, in run_action
>     provider_action()
>   File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 262, in action_run
>     tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72,
in inner
>     result = function(command, **kwargs)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102,
in checked_call
>     tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150,
in _call_wrapper
>     result = _call(command, **kwargs_copy)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303,
in _call
>     raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -s -o /dev/null
-w'%{http_code}' --negotiate -u: -k https://<HOSTNAME>:9995 | grep 200' returned 1.
> {code}
> In Summary:
> Ambari is always using "zeppelin.server.port" port for Quicklinks where as Zeppelin server
is started on "zeppelin.server.ssl.port" port number. this needs to be fixed. 
> Workaround that could be used is to set both the properties, "zeppelin.server.port" and
"zeppelin.server.ssl.port" to 8443.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message