[
https://issues.apache.org/jira/browse/AMBARI-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180685#comment-14180685
]
Hudson commented on AMBARI-7700:
--------------------------------
SUCCESS: Integrated in Ambari-branch-1.7.0 #178 (See
[https://builds.apache.org/job/Ambari-branch-1.7.0/178/])
(AMBARI-7700, 7701, 7703) - Ambari alerts for Hive metastore, Oozie, and ZK not
right (abaranchuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b0dfa7d9ef00e4c376ec2902da8d6c4d4097f50e)
* contrib/addons/src/addOns/nagios/plugins/sys_logger.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/NAGIOS/package/files/sys_logger.py
* contrib/addons/test/nagios/plugins/test_sys_logger.py
> Hivemetastore alert for hadoop 2.4 and 2.5 needs updating
> ----------------------------------------------------------
>
> Key: AMBARI-7700
> URL: https://issues.apache.org/jira/browse/AMBARI-7700
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.6.0
> Environment: Hadoop branch-2 release 2.4 or 2.5.
> Reporter: Nicholas Yao
> Assignee: Artem Baranchuk
>
> /var/log messages is not getting the proper alert message. we are seeing
> HADOOP_UNKNOWN_MSG instead of "hive_metastore_process_down",
> example of what we are seeing below:
> Sep 30 11:40:09 pitH1 nagios[20764]: Critical: Hadoop: HADOOP_UNKNOWN_MSG#
> Event Host=pitH1.td.teradata.com Service Description=HIVE-METASTORE::Hive
> Metastore process(CRITICAL), Connection refused
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
