"Return code of 139" for drive letters E, F, etc.

[nsclient@…]

I'm using NSClient++ on a few Windows hosts to monitor (amongst other things) disk space utilisation with a Nagios back-end. On one particular system I'm having a problem monitoring two specific drive letters (E & F). In each case I'm getting a response of "Return code of 139 is out of bounds". The same host returns quite happily for driver letters C & D and I have other hosts returning E & F drive (using the same Nagios service definition) without problems.

If I place NSClient in test mode on the affected server it successfully returns responses for all drive letters (e.g. the problem goes away). I've also tried updating the version to 0.3.5 with exactly the same symptoms

[anonymous]

I'm having the same problem. I noticed, though, that the disk in question was a Dynamic Disk. The C drive (normal disk) returned fine, as well as services, etc., but the D drive returned that error, as well as flooded the System Event log with pointless alerts

[nsclient@…]

Interesting - I'll check that tomorrow and report.

[nsclient@…]

Hi there,

On my problematic box all the disks are in basic mode so that doesn't explain it for me...

[alpha]

I have the same problem: all HD partitions returned real status (OK), but for drive G: (DVD RAM) returned code 139.

[mickem]

Check NT only works with fixed/networked drives. Use the NRPE command instead!