ICE for Linux 6.3 Nagios problem

[Allen012]

I have installed and setup HP ICE for Linux on a Red Hat 5.6 system.  Everything seems to be working except for Nagios.

The system name (icelx1) is "sm701".  Nagios insists that the host is called "nh", and fails on connecting to it. 

I have tried adding "nh" as an alias in both the host file and in DNS, with no change.  Because Nagios cannot find "nh" it blocks access to all of the other servers.

How can I change the definition of icelx1 from "nh" to "sm701"?

[Donna Firkser]

Nagios always uses "nh" for the Linux CMS and this cannot be changed.  Can you say more about the error you're seeing. e.g. Does the Nagios UI not come up?

Can you run "shownode info" on your Linux CMS and send me the output.

Can you run "/etc/init.d/nagios status" on your Linux CMS and send me the output.

Thanks,

Donna

[Allen012]

Nagios is trying to connect to server nh - server nh does not exist!  Server sm701 exists!

Nagios show node nh as DOWN and blocking all others

Status is "Failure to lookup host nh"

"shownode info" gives a table with all nodes

icelx1        | [ipaddress of node]  |  [fqdn of node]     | [ip of ilo]   | ILO3

. . .

/etc/init.d/nagios status

Checking for nagios

NAGIOS OK: 1 process, status log updated 15 seconds ago

supermon (pid 31394) is running...

mond (pid 31389) is running...

gathering status for nrpe ... icelx[1-8]

             Ok NRPE v2.12 - sm701 [ and all of the other nodes]

Nagios nsca:

sm701: [ ssh banner]

sm701: 0 data packet(s) sent to host successfully

[Allen012]

Please note:

I have stood up a second instance of ICE for Linux in another network, AND HAVE THE IDENTICAL PROBLEM!

This strikes me as broken software.  It is not working as advertised.  It is not working as noted in the Installation and configuration Manual, and it is not working as outlined in the User's Guide.

[Donna Firkser]

Can you please run the following command on your CMS and send me the output.

# /opt/hptc/nagios/libexec/db_get_node_status nh

Thanks,

Donna

[Donna Firkser]

BTW, I've never seen this problem before.  When you click on "nh" in the Nagios UI does the IP address for "nh" match the IP address in the "shownode info" output for icelx1?

How many NICs do you have on your CMS?  I'm wondering if you have multiple NICs and for some reason that's confusing Nagios.

I'm bringing in another developer to look at this.  We'll figure this out.

Donna

[Allen012]

/opt/hptc/nagios/libexec/db_get_node_status nh

OK - sm701: rta 0.012ms, lost 0%|rta=0.012ms;150.000;200.000;0; pl=0%;10;80;;

[Allen012]

I have two NICs, but the "nh" address is the same as the "shownode info" address. It is also the default route, and the subnet where the other (client) servers are.

I get the same failure message for all of the hosts (CMS and clients) "Failure to lookup host xxx"

DNS is working right - forward and reverse

/etc/hosts is correct, and agrees with the DNS

[Donna Firkser]

I'll work with the developer tomorrow to figure out next steps for troubleshooting this issue.  In the mean time, can you email me the contents of  /opt/hptc/etc/sysconfig/nagios (donna.firkser@hp.com).  And send me a copy of the Nagios UI which shows this error.

Thanks,

Donna