Nagios Support Forum

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

Crap.....the ultimate rookie mistake.....I have checked everything ten times over...everything except the command IP.

Wow.......

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 SERVI...

C:\Windows\system32>tasklist /SVC |find "sqlservr.exe"
sqlservr.exe 3940 MSSQLSERVER

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\User...

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...

Looks like normal start up logging. I forced a check in the nagios console and the log didn't even register activity. 2015-10-01 13:47:02: debug:D:\source\nscp\service\NSClient++.cpp:330: On crash: restart: nscp 2015-10-01 13:47:02: debug:D:\source\nscp\service\NSClient++.cpp:342: Archiving crash du...

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:\

Could this be a permissions issue with the NSClient because the service is running as an NT Service? Ideas anyone?

I upgraded to 4.3 and it still does the same thing....I opened a post on NSClient++ support page...