Nagios Support Forum

I am monitoring some Windows 2012 R2 VM's with our Nagios Core deployment. It monitors the C: perfectly, but I have two other drives E: and F: says they are invalid.


define service{
use generic-service
host_name <hostname>
service_description E:\ Drive Space
check_command check_nt!USEDDISKSPACE!-l e -w 80 -c 90
}


define service{
use generic-service
host_name <hostname>
service_description F:\ Drive Space
check_command check_nt!USEDDISKSPACE!-l f -w 80 -c 90
}

root@nagios:/etc/nagiosql/hosts# /usr/local/nagios/libexec/check_nt -H x.x.x.x -p 12489 -v USEDDISKSPACE -l c -w 80
c:\ - total: 79.66 Gb - used: 19.51 Gb (24%) - free 60.14 Gb (76%) | 'c:\ Used Space'=19.51Gb;63.72;0.00;0.00;79.66

root@nagios:/etc/nagiosql/hosts# /usr/local/nagios/libexec/check_nt -H x.x.x.x -p 12489 -v USEDDISKSPACE -l e -w 80
free disk space : Invalid drive

root@nagios:/etc/nagiosql/hosts# /usr/local/nagios/libexec/check_nt -H x.x.x.x -p 12489 -v USEDDISKSPACE -l f -w 80
Free disk space : Invalid drive

Any ideas here?

Hello,

Here is a quote from a thread I found with a similar issue.

syappstech wrote:Since I see a few people are having the same issue and I've found no resolution, I wanted to share what I found and how I fixed this.

This issue was impacting us on one single Windows 2008 Server R2 server. All of our other servers E:\ drives could be monitored without issue. On a whim, I checked the security settings at the root of the drive.

The drive permission at the root of the E:\ drive was restricted to the Domain Admins group and Domain Users only.

I looked at the same permissions on the F:\ drive, which was able to be monitored by nagios correctly. That drive had the same, but also have \Everyone, \CREATOR OWNER and \SYSTEM.

I added the \SYSTEM back to the root permissions on the E:\ drive and bam, nagios was able to now see that drive and report on it's free disk space.

This is now resolved, at least, for me. Hopefully this will help others who have run in to this issue as well.

I saw that one, in my case the permissions are all set correctly.

Is it a network drive?

No, vm virtual drive on Hyper-V...so is the C:\ that registers just fine....

What version of nsclient are you running on the windows system?
Can you check the nsclient.log file on the windows system for any errors?

NSClient++ 0,4,1,73 2012-12-17

There are only these two log entries....

2015-09-23 12:11:01: e:..\..\..\..\trunk\modules\CheckSystem\PDHCollector.cpp:139: Failed to query performance counters: PdhCollectQueryData failed: : -2147481643: No data to return.

2015-09-25 09:41:49: e:..\..\..\..\trunk\modules\CheckSystem\PDHCollector.cpp:139: Failed to query performance counters: PdhCollectQueryData failed: : -2147481643: No data to return.

Can you upgrade to the latest stable version and let us know if that fixes this?

No Change..still says invalid drive....but it detects the C:\ just fine.....it is just the E:\ and F:\ drive that are listing as invalid....

Are the "E:" and "F:" drives "detected" by check_nrpe?