I never tried it, but take a quick, short view into code, where I saw the following:
If you do not specifies a parameter, the C: drive is automatically used. This
could simply fail, if there is no C: drive.
You have not told anything about your environment, so I just can
only make this type of speculation.
May be, it helps.
br++mabra
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
as stated earlier Misconfiguration is the most likely source
turn on Verbose logging in the startup.cfg and extra event log entries
should help at debuging the command NC_Net is recieving.
getFreeDisk uses WMI to fetch the results
Sometimes Hardware drivers/firmware are corrupt and not properly reporting properly to WMI
however that is more likely on a desktop than a server
or some removable disks do not always have the items availible.
it islooking for:
cimv2:win32_logicalDisk.deviceid="#:"
where # is the specified drive letter
it then fetches both:
cimv2:win32_logicalDisk.Device[#}.FreeSpace
cimv2:win32_logicalDisk.Device[#}.Size
Tony
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everyone.
On some win2k3 servers with sp2 and .net 2.0 with german language pack i get this error message all the time when nagios checks the services on them:
Ereignistyp: Fehler
Ereignisquelle: NC_Net
Ereigniskategorie: Keine
Ereigniskennung: 14001
Datum: 25.05.2010
Zeit: 13:38:53
Benutzer: Nicht zutreffend
Computer: ****
Beschreibung:
Exeption occured getfree disk space :Nicht gefunden
The strange thin is, that it displays the correct data in nagios.
Any way to fix this?
You ever find anything on this? We have a similar issue on 2k8
Hi !
I never tried it, but take a quick, short view into code, where I saw the following:
If you do not specifies a parameter, the C: drive is automatically used. This
could simply fail, if there is no C: drive.
You have not told anything about your environment, so I just can
only make this type of speculation.
May be, it helps.
br++mabra
Sorry for the inconvience,
as stated earlier Misconfiguration is the most likely source
turn on Verbose logging in the startup.cfg and extra event log entries
should help at debuging the command NC_Net is recieving.
getFreeDisk uses WMI to fetch the results
Sometimes Hardware drivers/firmware are corrupt and not properly reporting properly to WMI
however that is more likely on a desktop than a server
or some removable disks do not always have the items availible.
it islooking for:
cimv2:win32_logicalDisk.deviceid="#:"
where # is the specified drive letter
it then fetches both:
cimv2:win32_logicalDisk.Device[#}.FreeSpace
cimv2:win32_logicalDisk.Device[#}.Size
Tony