You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2012/07/30 03:52:33 UTC
[jira] [Created] (AMBARI-662) As soon as a cluster is started, a
Nagios alert is sent due to Templeton status check failing
Yusaku Sako created AMBARI-662:
----------------------------------
Summary: As soon as a cluster is started, a Nagios alert is sent due to Templeton status check failing
Key: AMBARI-662
URL: https://issues.apache.org/jira/browse/AMBARI-662
Project: Ambari
Issue Type: Bug
Reporter: Yusaku Sako
Below is the Nagios alert that I got as soon as I successfully deployed a cluster.
During the cluster install, I did not choose to enable Kerberos Security. Yet it seems that a check is being performed for "kinit". Also, the realm EXAMPLE.COM is bogus.
***** Nagios *****
Notification Type: PROBLEM
Service: TEMPLETON::Templeton status check
Host: domu-12-31-39-17-2e-a7.compute-1.internal
Address: domu-12-31-39-17-2e-a7.compute-1.internal
State: CRITICAL
Date/Time: Sun Jul 29 21:47:30 EDT 2012
Additional Info:
CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network address for KDC in realm EXAMPLE.COM while getting initial credentials]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMBARI-662) Soon after a cluster was (seemingly)
successfully deployed, a number of Nagios alerts were sent
Posted by "Yusaku Sako (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMBARI-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yusaku Sako updated AMBARI-662:
-------------------------------
Description:
Below are some of the Nagios alerts that I got soon after I successfully deployed a cluster.
During the cluster install, I did not choose to enable Kerberos Security. Yet it seems that a check is being performed for "kinit". Also, the realm EXAMPLE.COM is bogus.
###
Subject: ** PROBLEM Service Alert: domu-12-31-39-17-2e-a7.compute-1.internal/TEMPLETON::Templeton status check is CRITICAL **
Body:
***** Nagios *****
Notification Type: PROBLEM
Service: TEMPLETON::Templeton status check
Host: domu-12-31-39-17-2e-a7.compute-1.internal
Address: domu-12-31-39-17-2e-a7.compute-1.internal
State: CRITICAL
Date/Time: Sun Jul 29 21:47:30 EDT 2012
Additional Info:
CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network address for KDC in realm EXAMPLE.COM while getting initial credentials]
###
Subject: ** PROBLEM Service Alert: domu-12-31-39-17-2e-a7.compute-1.internal/DATANODE::Process down is UNKNOWN **
Body:
***** Nagios *****
Notification Type: PROBLEM
Service: DATANODE::Process down
Host: domu-12-31-39-17-2e-a7.compute-1.internal
Address: domu-12-31-39-17-2e-a7.compute-1.internal
State: UNKNOWN
Date/Time: Sun Jul 29 21:47:40 EDT 2012
Additional Info:
check_tcp: Port must be a positive integer
###
Subject: ** PROBLEM Service Alert: ip-10-140-10-213.ec2.internal/DATANODE::Storage full is UNKNOWN **
Body:
***** Nagios *****
Notification Type: PROBLEM
Service: DATANODE::Storage full
Host: ip-10-140-10-213.ec2.internal
Address: ip-10-140-10-213.ec2.internal
State: UNKNOWN
Date/Time: Sun Jul 29 21:47:50 EDT 2012
Additional Info:
Usage: 0 -h host -p port -w warn% -c crit%
###
Subject: ** PROBLEM Service Alert: domu-12-31-39-17-2e-a7.compute-1.internal/HIVE-METASTORE::HIVE-METASTORE status check is CRITICAL **
Body:
***** Nagios *****
Notification Type: PROBLEM
Service: HIVE-METASTORE::HIVE-METASTORE status check
Host: domu-12-31-39-17-2e-a7.compute-1.internal
Address: domu-12-31-39-17-2e-a7.compute-1.internal
State: CRITICAL
Date/Time: Sun Jul 29 21:47:50 EDT 2012
Additional Info:
CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network address for KDC in realm EXAMPLE.COM while getting initial credentials]
###
Subject: ** PROBLEM Service Alert: domu-12-31-39-17-2e-a7.compute-1.internal/OOZIE::Oozie status check is CRITICAL **
Body:
***** Nagios *****
Notification Type: PROBLEM
Service: OOZIE::Oozie status check
Host: domu-12-31-39-17-2e-a7.compute-1.internal
Address: domu-12-31-39-17-2e-a7.compute-1.internal
State: CRITICAL
Date/Time: Sun Jul 29 21:48:00 EDT 2012
Additional Info:
CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network address for KDC in realm EXAMPLE.COM while getting initial credentials]
was:
Below is the Nagios alert that I got as soon as I successfully deployed a cluster.
During the cluster install, I did not choose to enable Kerberos Security. Yet it seems that a check is being performed for "kinit". Also, the realm EXAMPLE.COM is bogus.
***** Nagios *****
Notification Type: PROBLEM
Service: TEMPLETON::Templeton status check
Host: domu-12-31-39-17-2e-a7.compute-1.internal
Address: domu-12-31-39-17-2e-a7.compute-1.internal
State: CRITICAL
Date/Time: Sun Jul 29 21:47:30 EDT 2012
Additional Info:
CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network address for KDC in realm EXAMPLE.COM while getting initial credentials]
Priority: Critical (was: Major)
Summary: Soon after a cluster was (seemingly) successfully deployed, a number of Nagios alerts were sent (was: As soon as a cluster is started, a Nagios alert is sent due to Templeton status check failing)
> Soon after a cluster was (seemingly) successfully deployed, a number of Nagios alerts were sent
> -----------------------------------------------------------------------------------------------
>
> Key: AMBARI-662
> URL: https://issues.apache.org/jira/browse/AMBARI-662
> Project: Ambari
> Issue Type: Bug
> Reporter: Yusaku Sako
> Priority: Critical
>
> Below are some of the Nagios alerts that I got soon after I successfully deployed a cluster.
> During the cluster install, I did not choose to enable Kerberos Security. Yet it seems that a check is being performed for "kinit". Also, the realm EXAMPLE.COM is bogus.
> ###
> Subject: ** PROBLEM Service Alert: domu-12-31-39-17-2e-a7.compute-1.internal/TEMPLETON::Templeton status check is CRITICAL **
> Body:
> ***** Nagios *****
> Notification Type: PROBLEM
> Service: TEMPLETON::Templeton status check
> Host: domu-12-31-39-17-2e-a7.compute-1.internal
> Address: domu-12-31-39-17-2e-a7.compute-1.internal
> State: CRITICAL
> Date/Time: Sun Jul 29 21:47:30 EDT 2012
> Additional Info:
> CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network address for KDC in realm EXAMPLE.COM while getting initial credentials]
> ###
> Subject: ** PROBLEM Service Alert: domu-12-31-39-17-2e-a7.compute-1.internal/DATANODE::Process down is UNKNOWN **
> Body:
> ***** Nagios *****
> Notification Type: PROBLEM
> Service: DATANODE::Process down
> Host: domu-12-31-39-17-2e-a7.compute-1.internal
> Address: domu-12-31-39-17-2e-a7.compute-1.internal
> State: UNKNOWN
> Date/Time: Sun Jul 29 21:47:40 EDT 2012
> Additional Info:
> check_tcp: Port must be a positive integer
> ###
> Subject: ** PROBLEM Service Alert: ip-10-140-10-213.ec2.internal/DATANODE::Storage full is UNKNOWN **
> Body:
> ***** Nagios *****
> Notification Type: PROBLEM
> Service: DATANODE::Storage full
> Host: ip-10-140-10-213.ec2.internal
> Address: ip-10-140-10-213.ec2.internal
> State: UNKNOWN
> Date/Time: Sun Jul 29 21:47:50 EDT 2012
> Additional Info:
> Usage: 0 -h host -p port -w warn% -c crit%
> ###
> Subject: ** PROBLEM Service Alert: domu-12-31-39-17-2e-a7.compute-1.internal/HIVE-METASTORE::HIVE-METASTORE status check is CRITICAL **
> Body:
> ***** Nagios *****
> Notification Type: PROBLEM
> Service: HIVE-METASTORE::HIVE-METASTORE status check
> Host: domu-12-31-39-17-2e-a7.compute-1.internal
> Address: domu-12-31-39-17-2e-a7.compute-1.internal
> State: CRITICAL
> Date/Time: Sun Jul 29 21:47:50 EDT 2012
> Additional Info:
> CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network address for KDC in realm EXAMPLE.COM while getting initial credentials]
> ###
> Subject: ** PROBLEM Service Alert: domu-12-31-39-17-2e-a7.compute-1.internal/OOZIE::Oozie status check is CRITICAL **
> Body:
> ***** Nagios *****
> Notification Type: PROBLEM
> Service: OOZIE::Oozie status check
> Host: domu-12-31-39-17-2e-a7.compute-1.internal
> Address: domu-12-31-39-17-2e-a7.compute-1.internal
> State: CRITICAL
> Date/Time: Sun Jul 29 21:48:00 EDT 2012
> Additional Info:
> CRITICAL: Error doing kinit for nagios [kinit(v5): Cannot resolve network address for KDC in realm EXAMPLE.COM while getting initial credentials]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira