Page 1 of 1

UNKNOWN when using WMI--failed to bind uuid

Posted: Thu Nov 10, 2011 6:42 pm
by cwscribner
Hi all.

I switched all of my windows servers over to WMI monitoring. I thought I was all set but apparently not....Nagios is throwing this error for every service

Code: Select all

UNKNOWN: Could not retrieve all required data. Failed to bind to uuid 4d9f4ab8-7d1c-11cf-861e-0020af6e7c57 - NT_STATUS_NET_WRITE_FAULT
With the exception of a few listed as "Plugin timeout". The u:p pair that's supposed to be used to access these is located in Active Directory and is a domain user so I should have access to all the servers. How do I fix these errors? Are there additional permissions needed at the Active Directory level?

Re: UNKNOWN when using WMI--failed to bind uuid

Posted: Fri Nov 11, 2011 2:39 pm
by yancy
Hi cwscribner,

is the domain user a member of the administrators group? I would use wbemtest and try a wmi query to ensure you can connect in a windows environment.

for example,

start > run > wbemtest > connect

namespace = \\remotemachine\root\cimv2
username=<username of domain user>
password=<password>

if wbemtest can't connect, nagiosxi won't be able to monitor either.

-Yancy

Re: UNKNOWN when using WMI--failed to bind uuid

Posted: Thu Dec 01, 2011 11:17 am
by cwscribner
SOLVEDSOLVEDSOLVEDSOLVEDSOLVEDSOLVEDSOLVEDSOLVEDSOLVED

The username needs the domain before the username. e.g. [domain]/\[user] mydomain/\Nagios Forward slash is needed for escaping the backslash.
Ex: ./check_wmi_plus.pl -H 192.168.1.23 -m checkcpuq -u domain/\Nagios -p password
OK - Average CPU Queue Length 0.0 (3 points with 1 sec delay gives values: 0, 0, 0)|'Avg CPU Queue Length'=0.0;

Re: UNKNOWN when using WMI--failed to bind uuid

Posted: Sun Dec 04, 2011 7:40 pm
by Box293
This might be a good one to add to the FAQs

Re: UNKNOWN when using WMI--failed to bind uuid

Posted: Mon Dec 05, 2011 12:59 pm
by cwscribner
Box 293, I 100% agree. Such a simple solution that has sucked up weeks of time.