WMI checks are failing for a few hosts after upgrade XI2012

[txwomansu]

Hello,

Could you please help with this issue: after the upgrade to NagiosXI 2012, 2 hosts have issues with WMI checks of CPU, disk space, and other things. All WMI checks on these 2 hosts return: "UNKNOWN - Plugin Timed out". The account that queries WMI is a domain account with local admin rights on these 2 hosts, WMI service is running, there is no firewall in between nagiosXI and the hosts. When I give the wrong account WMI interface 'reacts' with failed logon message. I can run WMI queries locally on hosts. What do you suggest that I do? These 2 hosts had working WMI checks before the upgrade.

Thanks,
Svetlana

[lmiltchev]

Can you show us the actual checks that you are running (the failing ones) from the command line and the output of them? What is the exact version that you upgraded Nagios XI to?

[txwomansu]

Working WMI check output:
[root@nagiosxi libexec]# perl check_wmi_plus.pl -H workinghost.abc.com -u somewmiuser -p somepassword -m checkcpu
OK (Sample Period 17 sec) - Average CPU Utilisation 0.24%|'Avg CPU Utilisation'=0.24%;

Broken WMI check output:
[root@nagiosxi libexec]# perl check_wmi_plus.pl -H brokenhost.abc.com -u somewmiuser -p somepassword -m checkcpu
UNKNOWN - Plugin Timed out (15 sec)

I upgraded to NagiosXI 2012R1.6.

The OS of the remote host is Windows 2008 Enterprise 64 bit SP2.

Thanks.

[yancy]

txwomansu,

Try removing the cached data and re-running the query

in the /tmp directory there should be some .state files

Code: Select all

 cd /tmp
ls *.state
[code]

remove any .state files

Thanks,

-Yancy

[txwomansu]

There were no .state files in the /tmp directory...

[txwomansu]

I have noticed that if I query the host by IP, WMI check works (on the non-working server); if I query by hostname - I get timeout error. Maybe the issue is dns-related.

[lmiltchev]

Yes, it is probably DNS-related if checks are working with an IP, but not with a hostname.

[txwomansu]

I found the issue. The 2 hosts that were not working had hostname in the 'Address' field (vs. the IP address). After I changed this field to IP address, the problem resolved. DNS is fine. Thanks for your time.

[slansing]

Ahh, that would certainly do it, thanks for letting us know you got this resolved.