Actually Mark I think you were on to something. I did have to add the third
argument variable onto that because some of the other checks DO have a third
argument, however after modifying my check to the one above, it worked fine.

Thanks for the help though dude.

On Thu, Mar 24, 2011 at 4:16 PM, Mark A. Lappin <ma...@lmfj.com> wrote:

> Jarred, I don’t know that I would consider myself as an expert in Nagios,
> but more of somebody who can definitely get myself into trouble with it.
>
>
>
> I think you need to remove ‘$ARG3$’ from the end of your command line
> directive.  Your service’s check_command is not passing a 3rd parameter,
> and based on my understanding, you are then passing an argument string of ‘’
> which even though its blank, it sees a literal that it doesn’t know how to
> handle.  I don’t have quotes in my Nagios config so maybe it does not like a
> blank string, its essentially seeing:
>
> …/check_nt -H 10.0.10.10 -p 12489 -v USEDDISKSPACE -l d ‘’
>
>
>
>         command_line    /usr/lib/nagios/plugins/check_nt -H '$HOSTADDRESS$'
> -p 12489 -v '$ARG1$' '$ARG2$' *'$ARG3$'*
>
>
>
> …and I don’t think it likes what is on the end is my suspicion.
>
>
>
> Try changing your debug mode in Nagios to have more verbose logging so you
> can see what exactly Nagios is executing and then you can diagnose your
> problem better to;  you don’t want to leave this on for long because it
> generates a lot of information very very quickly.  I usually use an
> alternative configuration if I need to do this that does not have a lot of
> my normal checks enabled.
>
>
>
> If you’re excluding warning and critical levels, make sure you know how the
> check is going to come back in all cases or force it OK using service
> tricks; it does have default levels.
>
>
>
> All of my disk space service checks are  simply:
>
> check_command           check_nt!USEDDISKSPACE!-l e -w 80 -c 90
>
>
>
> With the command setup as:
>
> define command{
>
>         command_name    check_nt
>
>         command_line    $USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -s
> mySuperSecretPasswordHere -v $ARG1$ $ARG2$
>
>         }
>
>
>
> I use NSClient++ as well although the end-user client I don’t think it will
> make to much a difference until the check command will execute;  how the
> client responds to the argument string is entirely different.  I have a
> similar config to Keith on my machines which you can deploy and centrally
> manage through a GPO.  I use allowed hosts and also passwords on the client.
>
>
>
> ML
>
> **
>
> *Mark A. Lappin, CCNA, MCITP: Enterprise Administrator | Lee Michaels Fine
> Jewelry *
> Director of Information Technology
> 11314 Cloverland Ave | Baton Rouge, LA 70809
>
> Ph: 225.368.3645 | Fax: 225.368.3675  | Mobile: 225-362-2770
> ma...@lmfj.com * |  *www.lmfj.com
>
>
> ------------------------------
> This communication is privileged and confidential.  If you are not the
> intended recipient, please notify the sender by reply e-mail and destroy all
> copies of this communication .
>
> _______________________________________________
> General mailing list
> General@brlug.net
> http://brlug.net/mailman/listinfo/general_brlug.net
>
>


-- 
"The world's my oyster, a hotel room's my prison cell..."
_______________________________________________
General mailing list
General@brlug.net
http://brlug.net/mailman/listinfo/general_brlug.net

Reply via email to