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-20115) Ambari reports grafana service is down when its running causing other services to not start
Date Fri, 24 Feb 2017 13:33:44 GMT

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

Hudson commented on AMBARI-20115:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6842 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6842/])
AMBARI-20115 Ambari reports grafana service is down when its running (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6277a648c44e8f5540adf569cff10d494d3c701c])
* (edit) ambari-common/src/main/python/ambari_commons/network.py
* (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py


> Ambari reports grafana service is down when its running causing other services to not
start
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20115
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20115
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.5.0
>            Reporter: Arpit Gupta
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20115.patch
>
>
> On the node grafana is running.
> {code}
> # cat /var/run/ambari-metrics-grafana/grafana-server.pid
> 26593
>  # ps aux | grep 26593
> root     20057  0.0  0.0   5712   824 pts/0    R+   16:12   0:00 grep 26593
> ams      26593  0.0  0.0 102032 12904 ?        Sl   01:19   0:11 /usr/lib/ambari-metrics-grafana/bin/grafana-server
--pidfile=/var/run/ambari-metrics-grafana/grafana-server.pid --config=/etc/ambari-metrics-grafana/conf/ams-grafana.ini
cfg:default.paths.data=/var/lib/ambari-metrics-grafana cfg:default.paths.logs=/var/log/ambari-metrics-grafana
> {code}
> How ever after enabling WE when we tried to start all services ambari reported
> {code}
> Traceback (most recent call last):
>   File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 77, in <module>
>     AmsGrafana().execute()
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 313, in execute
>     method(env)
>   File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 58, in start
>     create_ams_datasource()
>   File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
line 239, in create_ams_datasource
>     response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
>   File "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
line 72, in perform_grafana_get_call
>     raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
> resource_management.core.exceptions.Fail: Ambari Metrics Grafana update failed due to:
[Errno 1] _ssl.c:491: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol
version
> {code}



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

Mime
View raw message