check_wmi_plus

An open discussion forum for obtaining help with Nagios Core. Nagios Core users of all experience levels are welcome here. Subforum have been created for the discussion of Nagios Core and Nagios Plugin development.

NOTE: The SourceForge.net mailing lists have been deprecated in favor of this forum in order to expedite support and provide additional features not available on the old mailing list.

check_wmi_plus

Postby delboy1966 » Tue Jan 02, 2018 9:45 am

We've been having some issues with wmi checks on Windows 2008 boxes, its happened across different servers.
A check will timeout or give a Windows error and then the next check it will check fine.

I've looked into it as much as I can and found mention of a possible memory leak in WMI on Windows 2008 boxes but the suggested hotfix has already been applied to our Windows 2008 boxes as part of our regular updates.

Just wondered if anyone else has encountered this and if they found out what the issue was.

I think maybe its the Windows boxes being under load and not enough resources available to answer the request.
But I've no way of proving this or debugging it as it happens to random servers throughout the day.

Thanks
Tony
delboy1966
 
Posts: 72
Joined: Thu Oct 22, 2015 5:26 am

Re: check_wmi_plus

Postby mcapra » Wed Jan 03, 2018 10:53 am

A lot of the default check_wmi_plus queries use the LIKE conditional which can (though certainly not as a rule) be significantly more expensive than the = conditional. These queries exist in your check_wmi_plus.ini file and the plugin is fairly liberal with allowing you to modify/alter/create them (just back the file up before you mess with it). Not sure if that will solve your problem, but in the case of checking processes/services the change might be meaningful as those classes can get quite bloated. I'm guessing if you're aggressively monitoring a couple dozen processes/services on a given 2008 machine that using = in the queries could save some time.

You might also fiddle around with the -d flag for check_wmi_plus and get some additional output to better identify bottlenecks. All of the above assumes the bottleneck is with the remote WMI system rather than the local check_wmi_plus execution environment.
Former Nagios employee
http://www.mcapra.com/
User avatar
mcapra
 
Posts: 2980
Joined: Thu May 05, 2016 3:54 pm

Re: check_wmi_plus

Postby npolovenko » Wed Jan 03, 2018 1:05 pm

Thanks, @mcapra! @delboy1966, Let us know if you have more questions regarding this issue. Also, have you considered increasing the -t timeout value inside the check command?
User avatar
npolovenko
Support Tech
 
Posts: 941
Joined: Mon May 15, 2017 5:00 pm

Re: check_wmi_plus

Postby delboy1966 » Fri Jan 12, 2018 9:08 am

Tried all that was suggested and still no different.
I think it must just be the Windows boxes being a pain.

Thanks anyway
delboy1966
 
Posts: 72
Joined: Thu Oct 22, 2015 5:26 am

Re: check_wmi_plus

Postby lmiltchev » Fri Jan 12, 2018 4:22 pm

So you used the "-d" flag to enable debugging, but you didn't find any clues in the output of what could be causing the timeouts?
Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
lmiltchev
QA Manager
 
Posts: 9693
Joined: Mon May 23, 2011 12:15 pm

Re: check_wmi_plus

Postby delboy1966 » Wed Jan 17, 2018 5:47 am

I believe we found the issue with the timeouts.
It was a network issue.
Thanks for your help.

Thread can be closed.
delboy1966
 
Posts: 72
Joined: Thu Oct 22, 2015 5:26 am


Return to Nagios Core

Who is online

Users browsing this forum: Bing [Bot] and 12 guests