check_nt configurations/setup

[Bobby Bradshaw]

Thanks!  Now I can get the system uptime with this command "./check_nt
-H (ip address) -v UPTIME -p 1250" from running the command while in
the plugins directory.  BUT, how do I put that in the cfg files and in
which cfg files?

Please advise.  Thanks!



On 8/21/05, Petrucci, Joseph <Joseph.Petrucci at ddiworld.com> wrote:
> 
> Can you check if you can telnet to the machine from the Nagios machine. 
>  
> telnet machineIP 1250
>  
> Also if you change from the default port you need to put that in the command
> or it will try 1248.
>  
> Joseph A. Petrucci
E Systems
> DBA
------------------------------------------------
Desk:
> 412-220-2646
Cell: 412-916-2867
Text message (e-mail)
> 4129162867 at mobile.att.net
e-mail joseph.petrucci at ddiworld.com
Personal Cell:
> 724-462-0443
Personal e-mail: japetrucci at hotmail.com
> 
> ________________________________
> From: nagios-users-admin at lists.sourceforge.net on behalf of
> Andreas Ericsson
> Sent: Sun 8/21/2005 11:07 AM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] check_nt configurations/setup
> 
> 
> 
> 
> Bobby Bradshaw wrote:
> > I changed the nrpe listening port to 1250, because I read somewhere
> > that MS Exchange uses port 1248.
> 
> This is not exactly true. MS Exchange doesn't care what ports it uses,
> it just starts off at 1024 and keeps stealing ports upwards. If you want
> to be sure of not getting caught in the Exchange trap, use a port in the
> range 50000-65535.
> 
> >  So, I opened tcp port 1250 on both
> > the nagios server and the windows xp host.  I edited nrpe.cfg - the
> > listening port to 1250 and added the xp host ip to allowed_hosts
> > section.  I added the following to command.cfg:
> >
> > command[check_nt_disk]=$USER1$/check_nt -H $HOSTADDRESS$
> -p 1250 -v
> > USEDDISKSPACE -l $ARG1$ -w $ARG2$ -c $ARG3$
> > command[check_nt_cpuload]=$USER1$/check_nt -H
> $HOSTADDRESS$ -p 1250 -v
> > CPULOAD -l $ARG1$
> > command[check_nt_uptime]=$USER1$/check_nt -H
> $HOSTADDRESS$ -p 1250 -v UPTIME
> > command[check_nt_service]=$USER1$/check_nt -H
> $HOSTADDRESS$ -P 1250 -v
> > SERVICESTATE -l $ARG1$
> > command[check_nt_memuse]=$USER1$/check_nt -H
> $HOSTADDRESS$ -p 1250 -v
> > MEMUSE -w $ARG1$ -c $ARG2$
> >
> > Also, I have NOT edited checkcommands.cfg, because I don't know if I
> > have to and not sure what to put in there if I do have to.
> >
> > Please advise if I am doing something wrong or if there is extra steps
> > to be taken.
> 
> What's the problem, and what ports does nmap tell you are open?
> 
> > Thanks!
> >
> >
> > On 8/21/05, Petrucci, Joseph <Joseph.Petrucci at ddiworld.com> wrote:
> >
> >>
> >>There are a few things you can check.
> >>First check that the "Nagios Agent" is running as a service on the Windows
> >>machine.
> >>Second check if port 1248 is opened between the Nagios machine and the
> >>Windows machine.
> >>
> >>These are first steps I would think you have already done, but since you
> >>didn't mention them I thought I would.
> >>
> >>If you have already done this post a description of the steps you have
> taken
> >>so far and there results so we can help further.
> >>
> >>Joseph A. Petrucci
> >
> > E Systems
> >
> >>DBA
> >
> > ------------------------------------------------
> > Desk:
> >
> >>412-220-2646
> >
> > Cell: 412-916-2867
> > Text message (e-mail)
> >
> >>4129162867 at mobile.att.net
> >
> > e-mail joseph.petrucci at ddiworld.com
> > Personal Cell:
> >
> >>724-462-0443
> >
> > Personal e-mail: japetrucci at hotmail.com
> >
> >>________________________________
> >>From: nagios-users-admin at lists.sourceforge.net on behalf
> of
> >>Bobby Bradshaw
> >>Sent: Fri 8/19/2005 2:43 PM
> >>To: nagios-users at lists.sourceforge.net
> >>Subject: [Nagios-users] check_nt configurations/setup
> >>
> >>
> >>Hi all,
> >>
> >>My Nagios setup is:
> >>Suse 9.3 Professional
> >>Nagios v1.2
> >>Nagios plugins v1.4
> >>Nagios nrpe v2.0
> >>
> >>I have Nagios running correctly, sending notifications, checking ping and
> >>HTTP on several hosts.  Although, I am having so much trouble trying to
> get
> >>Nagios to run "./check_nt -H 192.168.1.111 -v UPTIME" command without
> >>getting a "CRITICAL - Socket timeout after 10 seconds" error or any of the
> >>check_nt commands without an error.  I have the Nsclient 2.01 on my
> Windows
> >>XP host.  Is there better documentation than what is provided with
> Nsclient?
> >> Can I get some pointers on ALL the cfg files that I have to edit to get
> the
> >>check_nt command to work.
> >>
> >>Thanks in advance!
> >>
> >>--
> >>Bobby Bradshaw, Jr.
> >>bobby.bradshaw at gmail.com
> >
> >
> >
> 
> --
> Andreas Ericsson                   andreas.ericsson at op5.se
> OP5 AB                             www.op5.se
> Lead Developer
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> 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
> 
> 


-- 
Bobby Bradshaw, Jr.
bobby.bradshaw at gmail.com


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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