Nagios Support Forum

Sorry to be late to this. When I updated to Nagios 2014R1.5 I too had this issue and updating the latest CheckWmiPlus did solve this. When I updated to 2014R1.5 it took me a couple of days before I realized the CPU alerts I was getting were bogus. I seem to remember this bug also showed up monitoring 2008R2 servers. I use -m checkeachcpu, btw.

The issue is solvable although sorry to say I am no Perl expert and don't have a step by step to update Perl.I was using the stock VM image downloaded from Nagios and also had to fight to get perl up to date. The long module was also tricky to install but again sorry to say I don't remember why. Also the configuration between the stock XI checkwmiplus and the latest checkwmiplus is different and must be cleaned up to use one or the other method.

I personally feel it's worth the effort to get to the lastest stable of CheckWMIPlus. I used this for windows servers almost exclusively and only load the client when it's absolutely required.

Thanks for the feedback, rseiwert! At least now we know there is a good change that the plugin could solve Frédéric GRANAT's issue.

@Frédéric GRANAT
Let us know if you decide to upgrade perl on your system.

Frédéric,

I have not been able to replicate your problem with check_wmi_plus.pl. I have three servers doing a cpu check on a windows 2012 server.

check_xi_service_wmiplus!'awmiuser'!'paswd4wmiuser'!checkcpu!-w '80' -c '90'

Nagios XI 2014R2.3
CentOS release 5.11 (Final)
check_wmi_plus.pl Version: 1.49

Nagios XI 2014R2.3
CentOS release 6.6 (Final)
check_wmi_plus.pl Version: 1.59

Nagios XI 2014R2.3
CentOS release 6.6 (Final)
check_wmi_plus.pl Version: 1.49

So I am not sure that an upgrade to check_wmi_plus.pl with fix the issue you are having ?

The reason to update the modules is that it *might* be possible to update the modules, and then you *might* be able to force check_wmi_plus.pl to run with the new modules and the old perl ?

Updating Perl outside of the system update process is a quick and easy way to break a lot of stuff on your system. Being there are several modules/plugins/andstuff that use Perl, it is more likely than not, to break the whole system updating Perl outside of the system update process.

If you really need to update your Perl, I would suggest you move to a newer version of CentOS. I know it is fairly easy to update to check_wmi_plus.pl version 1.59 on CentOS release 6.6 .

==>brian.

Hi LMitchev,
If updating perl could be the solution, OK.
But bdgoecke on Fri Jan 09, 2015 12:12 pm said that it's not possible.
Please tell me how to proceed.

I confirm that that problem occurs not only on Windows 2012 servers (also on W2K3,W2K8), so the title of the post could be : "Problem with monitoring CPU"

I said that there was a good change that the plugin could solve your issues, because of the feedback given by "rseiwert":

When I updated to Nagios 2014R1.5 I too had this issue and updating the latest CheckWmiPlus did solve this.

Unfortunately, "rseiwert" didn't give us any details about the upgrade process.
Important: It is not guaranteed that this will work for you the same way as it did for "rseiwert". There is always a risk of something going wrong so I cannot recommend upgrading perl. You will have to make a judgement call here. It would be wiser to upgrade the OS to CentOS 6. First you could try upgrading the perl modules only (as recommended by "bdgoecke").

Hi,

Additional info : the problem occurs always on the same machines (one in W2K3, one in W2K8, one in W2K12).
Don't you have any idea ?

bdgoecke says : "We will help you try to upgrade the modules"
I'm awaiting your help.

Rgds,

Frederic

Frédéric,

I should have documentation on how to upgrade the modules for check_wmic_plus.pl version 1.59 on CentOS 5 soon.

==>brian.

Hi,
Any news ?

Frédéric,

We are testing my document and script to upgrade check_wmi_plus.pl

==>brian.

Hi,
Thanks for the document.
I applied the changes and now :

/usr/local/nagios/libexec/check_wmi_plus_latest.pl -H 172.16.1.13 -u svc_riverbed -p dsisvc -m checkcpu -w 80 -c 90
UNKNOWN - The WMI query had problems. You might have your username/password wrong or the user's access level is too low. Wmic error text on the next line.
[librpc/rpc/dcerpc_util.cdcerpc_pipe_auth_recv()] Failed to bind to uuid 4d9f4ab8-7d1c-11cf-861e-0020af6e7c57 - NT_STATUS_NET_WRITE_FAULT
[librpc/rpc/dcerpc_connect.c:790:dcerpc_pipe_connect_b_recv()] failed NT status (c0000022) in dcerpc_pipe_connect_b_recv
[wmi/wmic.c:196:main()] ERROR: Login to remote object.
NTSTATUS: NT_STATUS_ACCESS_DENIED - Access denied