Problems with check_nt

[Antonio Pereira]

Hi,

 

I'll try to elaborate

 

The problem is when I scan a drive off a particular server it doesn't work. 

 

Let's say I have 4 servers, I am scanning d: drive on all 4 servers 3 out of the 4 will work and return the fourth one will return an error. (Return code of 139 is out of bounds)

 

The client version that is running on all servers is 0.2.7

 

I have verified that all servers is hard drives being scanned not cd drives.

 

Antonio Pereira
National IT Coordinator

Coordinateur National de Technologies de l'Information
Tél./Tel. : (514) 341-8181, ext./poste 267
Téléc./Fax. : (514) 341-1253
Cell: (514) 514-444-6086
Sans Frais/Toll Free: (888) 338-6266 ext./poste 267
Courriel / E-mail. : apereira at duocom.ca

 

Duocom Canada Inc.
10000, Cavendish Blvd.
Ville St. Laurent (Québec) H4M 2V1
www.duocom.ca <http://www.duocom.ca/> 

 

From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Anthony Montibello
Sent: Tuesday, September 11, 2007 7:45 PM
To: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Problems with check_nt

 

I am not sure I understand the problem correctly,

 

is the error in question intermittent where it is there then not there  

or,

 every time you try that particular drive on that particular server.

 

if the latter have you tried check_nt from the command line to test the command before adding to your configuration.

what is the entire error output?

 

Did your make sure the Windows Host has that drive installed?

for example if it is a CDROM drive it may cause an error (not sure what error) since it does not have freespace 

 

What is the Windows client installed, 

run check_nt -v CLIENTVERSION
 

Since the different windows clients may deal with internal errors differently it is posible that the output of a windows client is giving this error while a different client would give a different output.

 

Tony (Author of NC_NEt)


 

On 9/11/07, Antonio Pereira <apereira at duocom.ca> wrote: 

Hi,

Yes I checked again.

What I did is added other hosts selecting different drives trying c:, d:, e: f:, etc. This differs depending on the server and I still get these random results. It's odd. 

I even tried removing each drive and service and adding one at a time and still the same result.
Every single server that I scan the local c: it works fine. But when I start scanning the next drives I start getting these random results. 

I am scanning 10 servers they all have c: drive. These work fine.

I am scanning 4 servers they all have d: drive. 1 out 4 works

I am scanning 2 servers they have e: drive Both work

I am scanning 2 servers thay have f: drive 1 out 2 work. 

I haven't added all the servers yet but I figure this will do for troubleshooting purposes.



Antonio Pereira
National IT Coordinator
Coordinateur National de Technologies de l'Information 
Tél./Tel.: (514) 341-8181, ext./poste 267
Téléc./Fax.: (514) 341-1253
Cell: (514) 514-444-6086
Sans Frais/Toll Free: (888) 338-6266 ext./poste 267
Courriel / E-mail.: apereira at duocom.ca 

Duocom Canada Inc.
10000, Cavendish Blvd.
Ville St. Laurent (Québec) H4M 2V1
www.duocom.ca


-----Original Message-----
From: Andreas Ericsson [mailto: ae at op5.se <mailto:ae at op5.se> ]
Sent: Tuesday, September 11, 2007 4:27 PM
To: Antonio Pereira
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Problems with check_nt 

Antonio Pereira wrote:
> Hello,
>
>
>
> I am experiencing an issue that I don't understand
>
>
>
> I have defined a check_nt command and I am scanning the disk space on about 2 servers right now. 1 out of the 2 returns a result but then the2nd will return an error message as follows 
>
>
>
> (Return code of 139 is out of bounds)
>

139? Are you absolutely, 100% sure it's 139? It seems odd, because return codes
are given as signed chars, which are normally not capable of handling numbers 
outside the range -128 to 127.

It's done this way because, traditionally, programs return the additive inverse
of the system error that caused the abnormal termination, or -1 if the programmer
was lazy. 

--
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231 



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null

 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070913/63d2bdf6/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null