Nagios Support Forum

root@nagios:/usr/local/nagios/libexec# ./check_nrpe -H x.x.x.x -p 5666 -c alias_disk
OK: All drives within bounds.|'C:\ %'=76%;10;5 'C:\'=19.54G;7.96;3.98;0;79.65

It looks like all it sees is the C:\

Can you run the following commands from the CMD prompt on the Windows box and show the output?

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 D SQLServer CDFS DVD-ROM 3826 MB Healthy
Volume 1 System Rese NTFS Partition 350 MB Healthy System
Volume 2 C NTFS Partition 79 GB Healthy Boot
Volume 3 E SQL NTFS Partition 126 GB Healthy
Volume 4 F Data NTFS Partition 19 GB Healthy

DISKPART>

Let's double check the permissions - from the CMD prompt, run the following command and show the output:

This looks promising....

C:\Windows\system32>icacls c: & icacls e: & icacls f:
c: NT SERVICE\TrustedInstaller:(F)
NT SERVICE\TrustedInstaller:(CI)(IO)(F)
NT AUTHORITY\SYSTEM:(M)
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
BUILTIN\Administrators:(M)
BUILTIN\Administrators:(OI)(CI)(IO)(F)
BUILTIN\Users:(RX)
BUILTIN\Users:(OI)(CI)(IO)(GR,GE)
CREATOR OWNER:(OI)(CI)(IO)(F)
APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX)
APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)

Successfully processed 1 files; Failed processing 0 files
e: BUILTIN\Administrators:(OI)(CI)(F)
NT AUTHORITY\SYSTEM:(OI)(CI)(F)
CREATOR OWNER:(OI)(CI)(IO)(F)
BUILTIN\Users:(OI)(CI)(RX)
BUILTIN\Users:(CI)(AD)
BUILTIN\Users:(CI)(IO)(WD)
Everyone:(RX)

Successfully processed 1 files; Failed processing 0 files
f: BUILTIN\Administrators:(OI)(CI)(F)
NT AUTHORITY\SYSTEM:(OI)(CI)(F)
CREATOR OWNER:(OI)(CI)(IO)(F)
BUILTIN\Users:(OI)(CI)(RX)
BUILTIN\Users:(CI)(AD)
BUILTIN\Users:(CI)(IO)(WD)
Everyone:(RX)

Successfully processed 1 files; Failed processing 0 files

C:\Windows\system32>

I am not a 100% sure, but I think the "E:" and "F:" drive should have the same permissions for the "SYSTEM" as the "C:" drive. The only differences that I see are these:
Frankly, I haven't seen this problem before but I am pretty sure, this is a permissions issue.

On my workstation, for drive "d" I have:
and my check against "d" drive works fine.

I don't see how it can be permissions. I have another machine with same OS and all with an E: drive and it detects it fine. It is just this box.

The icacls settings on both boxes are identical.

I even removed and reinstalled the client.

Vm #2

C:\Windows\system32>icacls c: & icacls e:
c: NT SERVICE\TrustedInstaller:(F)
NT SERVICE\TrustedInstaller:(CI)(IO)(F)
NT AUTHORITY\SYSTEM:(M)
NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
BUILTIN\Administrators:(M)
BUILTIN\Administrators:(OI)(CI)(IO)(F)
BUILTIN\Users:(RX)
BUILTIN\Users:(OI)(CI)(IO)(GR,GE)
CREATOR OWNER:(OI)(CI)(IO)(F)
APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX)
APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)

Successfully processed 1 files; Failed processing 0 files
e: BUILTIN\Administrators:(OI)(CI)(F)
NT AUTHORITY\SYSTEM:(OI)(CI)(F)
CREATOR OWNER:(OI)(CI)(IO)(F)
BUILTIN\Users:(OI)(CI)(RX)
BUILTIN\Users:(CI)(AD)
BUILTIN\Users:(CI)(IO)(WD)
Everyone:(RX)

Successfully processed 1 files; Failed processing 0 files

C:\Windows\system32>

All fixed.

Now time to swallow some humility and admit my dumb a** had a mis-configuration in the Nagios cfg file and the IP was wrong......

I have not made a rookie mistake like that in a very long time.

smh

Oh man, same as the other thread? These are becoming easier and easier to 'resolve'

Should I lock this one up?

Dumb a**ed mistakes are the best. They make you think thrice before posting the next time.