You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/06/17 18:51:05 UTC
[jira] [Commented] (AMBARI-17299) Ambari Metrics service check
failed exceed timeout
[ https://issues.apache.org/jira/browse/AMBARI-17299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336690#comment-15336690 ]
Hudson commented on AMBARI-17299:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5105 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5105/])
AMBARI-17299 Ambari Metrics service check failed exceed timeout (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=da8195fb839a3ba4090301551c15067cb50a9635])
* ambari-metrics/ambari-metrics-timelineservice/pom.xml
> Ambari Metrics service check failed exceed timeout
> --------------------------------------------------
>
> Key: AMBARI-17299
> URL: https://issues.apache.org/jira/browse/AMBARI-17299
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.4.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17299.patch
>
>
> Service check failed stderr:
> {noformat}
> Python script has been killed due to timeout after waiting 600 secs
> {noformat}
> No phoenix-server.jar in /usr/lib/ams-hbase/lib/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)