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/09/01 22:27:45 UTC

[jira] [Commented] (AMBARI-12963) Exceptions in ambari-server.log after ambari-server reset

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

Hudson commented on AMBARI-12963:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3366 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3366/])
AMBARI-12963. Exceptions in ambari-server.log after ambari-server reset. (mpapirkovskyy) (mpapyrkovskyy: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c85f044ff2b2c7f8d13f727f91e230952d96ab17)
* ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertReceivedListener.java


> Exceptions in ambari-server.log after ambari-server reset
> ---------------------------------------------------------
>
>                 Key: AMBARI-12963
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12963
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Myroslav Papirkovskyy
>            Assignee: Myroslav Papirkovskyy
>             Fix For: 2.1.2
>
>
> STR
> Deploy cluster
> Reset ambari server
> start ambari-server
> Result
> Lot's of alerts related exceptions in ambari-server.log



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