<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Hi,<o:p></o:p> <o:p> </o:p> I’ll try to elaborate<o:p></o:p> <o:p> </o:p> The problem is when I scan a drive off a particular server it doesn’t work. <o:p></o:p> <o:p> </o:p> 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)<o:p></o:p> <o:p> </o:p> The client version that is running on all servers is 0.2.7<o:p></o:p> <o:p> </o:p> I have verified that all servers is hard drives being scanned not cd drives.<o:p></o:p> <o:p> </o:p> Antonio Pereira National IT Coordinator<o:p></o:p> 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. : <a href="mailto:apereira@duocom.ca" title="mailto:apereira@duocom.ca apereira@duocom.ca">apereira@duocom.ca</a><o:p></o:p> <o:p></o:p> Duocom Canada Inc. 10000, Cavendish Blvd. Ville St. Laurent (Québec) H4M 2V1 <a href="http://www.duocom.ca/" target="_blank" title="http://www.duocom.ca/ www.duocom.ca">www.duocom.ca</a><o:p></o:p> <o:p> </o:p> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From: nagios-users-bounces@lists.sourceforge.net [mailto:nagios-users-bounces@lists.sourceforge.net] On Behalf Of Anthony Montibello Sent: Tuesday, September 11, 2007 7:45 PM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Problems with check_nt<o:p></o:p> </div> <o:p> </o:p> <div> I am not sure I understand the problem correctly,<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> is the error in question intermittent where it is there then not there <o:p></o:p> </div> <div> or,<o:p></o:p> </div> <div> every time you try that particular drive on that particular server.<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> if the latter have you tried check_nt from the command line to test the command before adding to your configuration.<o:p></o:p> </div> <div> what is the entire error output?<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> Did your make sure the Windows Host has that drive installed?<o:p></o:p> </div> <div> for example if it is a CDROM drive it may cause an error (not sure what error) since it does not have freespace <o:p></o:p> </div> <div> <o:p></o:p> </div> <div> What is the Windows client installed, <o:p></o:p> </div> <div> run check_nt -v CLIENTVERSION <o:p></o:p> </div> <div> 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.<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> Tony (Author of NC_NEt)<o:p></o:p> </div> <div> <o:p></o:p> </div> <div> On 9/11/07, Antonio Pereira <<a href="mailto:apereira@duocom.ca">apereira@duocom.ca</a>> wrote: <o:p></o:p> 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.: <a href="mailto:apereira@duocom.ca">apereira@duocom.ca </a> Duocom Canada Inc. 10000, Cavendish Blvd. Ville St. Laurent (Québec) H4M 2V1 <a href="http://www.duocom.ca">www.duocom.ca</a> -----Original Message----- From: Andreas Ericsson [mailto:<a href="mailto:ae@op5.se"> ae@op5.se</a>] Sent: Tuesday, September 11, 2007 4:27 PM To: Antonio Pereira Cc: <a href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net</a> 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 <a href="mailto:andreas.ericsson@op5.se">andreas.ericsson@op5.se</a> OP5 AB <a href="http://www.op5.se">www.op5.se</a> Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. <a href="http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/">http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net </a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null<o:p></o:p> </div> <o:p> </o:p> </div>  <hr color='#D2D3D2' noshade> Avis Le présent message n'est destiné qu'à la personne ou à l'entité à qui il est adressé et peut contenir des renseignements de nature privilégiée et confidentielle. Si le lecteur du présent message n'est pas le destinataire prévu ou encore la personne chargée de remettre ce message au destinataire prévu, veuillez nous aviser immédiatement. Toute diffusion, distribution ou reproduction des renseignements contenus dans ce message ou des documents qui lui sont joints est strictement interdite. ________________________________________ Notice This message is intended only for the use of individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient or the person responsible for delivering the message to the intended recipient, please notify us immediately. Any disclosure, distribution or copying of this message or the information contained herein or attached hereto is strictly prohibited. </body></html>