You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/03/17 12:55:38 UTC

[jira] [Commented] (AMBARI-10086) ZooKeeper Server Process alert always checks default port

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

Hudson commented on AMBARI-10086:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #2054 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2054/])
AMBARI-10086 ZooKeeper Server Process alert always checks default port (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ff711095e1e3300798af8fa5bcef49ff8dd97176)
* ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/alerts.json


> ZooKeeper Server Process alert always checks default port
> ---------------------------------------------------------
>
>                 Key: AMBARI-10086
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10086
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.0
>
>
> **STR:**  
> 1) Deploy Ambari  
> 2) Change `zoo.cfg/clientPort`
> ZooKeeper Server Process Alert shows "Connection failed: Errno 111 Connection
> refused"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)