Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-662

Soon after a cluster was (seemingly) successfully deployed, a number of Nagios alerts were sent

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Not A Problem
    • None
    • None
    • None
    • None

    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]

      Attachments

        Activity

          People

            Unassigned Unassigned
            u39kun Yusaku Sako
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: