[
https://issues.apache.org/jira/browse/AMBARI-20115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878362#comment-15878362
]
Hadoop QA commented on AMBARI-20115:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12853963/AMBARI-20115.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10688//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10688//console
This message is automatically generated.
> 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: Dmytro Sen
> 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)
