ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-4954) After configuring NNHA, nn process alerts don't work
Date Wed, 05 Mar 2014 15:11:43 GMT
Vitaly Brodetskyi created AMBARI-4954:
-----------------------------------------

             Summary: After configuring NNHA, nn process alerts don't work
                 Key: AMBARI-4954
                 URL: https://issues.apache.org/jira/browse/AMBARI-4954
             Project: Ambari
          Issue Type: Bug
          Components: agent
            Reporter: Vitaly Brodetskyi
            Assignee: Vitaly Brodetskyi
            Priority: Critical


1) Configure NN HA
2) stack 2.0.6 (but check stack 2.1 as well)
3) Two alerts show" check_tcp: Port must be a positive integer"

NameNode process on c6401.ambari.apache.org
NameNode process on c6402.ambari.apache.org

4) Looked at /etc/nagios/objects/hadoop-services.cfg
5) Saw:

{code}
define service {
        host_name               c6401.ambari.apache.org
        use                     hadoop-service
        service_description     NAMENODE::NameNode process on c6401.ambari.apache.org
        servicegroups           HDFS
        check_command           check_tcp_wrapper!//test!-w 1 -c 1
        normal_check_interval   0.5
        retry_check_interval    0.25
        max_check_attempts      3
}
define service {
        host_name               c6402.ambari.apache.org
        use                     hadoop-service
        service_description     NAMENODE::NameNode process on c6402.ambari.apache.org
        servicegroups           HDFS
        check_command           check_tcp_wrapper!//test!-w 1 -c 1
        normal_check_interval   0.5
        retry_check_interval    0.25
        max_check_attempts      3
}
{code}

Notice in the above *//test* is the name of my nameservice.

Attaching screen shot of my config. So looks like it's grabbing port from the wrong prop.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message