Check_nt win2k service states and nagios

[Ørjan Sandland]

On Mon, 3 Nov 2003 13:04:50 -0700
  "Neil Lehouillier" <NLehouillier at comptonpetroleum.com> 
wrote:
>Tim,
> 
>first thanks for helping out.  I tried what you suggested 
>but it just
>had the same effect.  No changes.  I tried creating the 
>entire command
>within checkcommands.cfg.  I have also tried passing the 
>$ARG$ from
>Services.cfg but to no avail.  Is anyone out there 
>currently doing
>this(ie checking windows nt services with check_nt).  If 
>so, could you
>publish the way you have it set up for me to look at 
>(from the cfg files
>to the permissions).

I'm currently using NSClient on about 10 W2K servers with 
no particular problems. 
I do however, check for the exe file of the service, not 
for the servicename, and I have not yet tried to check 
multiple processes on one host.

I'll get some confs for you to look at when I get to work 
tomorrow.

Ørjan 

<keeping the rest :->
> 
>If anyone has any other ideas I am more than willing to 
>give it a try to
>get this working.....
> 
>Thanks....
> 
>Neil
>
>	-----Original Message-----
>	From: VanZee, Timothy [mailto:T-VANZEE at govst.edu] 
>	Sent: Monday, November 03, 2003 7:29 AM
>	To: nagios-users at lists.sourceforge.net
>	Subject: RE: [Nagios-users] Check_nt win2k service 
>states and
>nagios
>	
>	
>
>	You can define a new check command in your 
>checkcommand.cfg file
>such as:
>
>	 
>
>	# 'check_nt_service_exchange' command definition
>
>	define command{
>
>	        command_name    check_nt_service
>
>	        command_line    $USER1$/check_nt -H 
>$HOSTADDRESS$ -s
>password123 -v SERVICESTATE -d SHOWALL -l $ARG1$
>
>	        }
>
>	 
>
>	Then in your services.cfg file modify the line:
>
>	 
>
>	check_command
>"/usr/local/nagios/libexec/check_nt_exchange!SMTPSVC,AVExch32Service
>
>	 
>
>	I haven't tested with a comma in the check_command line, 
>so you
>may need to either add another $ARG$ or place an escape 
>character in the
>command.
>
>	 
>
>	 
>
>	Tim Van Zee
>
>	ITS Network Specialist
>
>	Governors State University
>
>	 
>
>	
>  _____  
>
>
>	From: nagios-users-admin at lists.sourceforge.net
>[mailto:nagios-users-admin at lists.sourceforge.net] On 
>Behalf Of Neil
>Lehouillier
>	Sent: Friday, October 31, 2003 3:02 PM
>	To: nagios-users at lists.sourceforge.net
>	Subject: [Nagios-users] Check_nt win2k service states 
>and nagios
>
>	 
>
>	Hi All, 
>
>	I'm having a problem monitoring some Win 2k exchange 
>services
>using nagios and check_nt from nsclient.  When I execute 
>the following
>from the command line su'd to nagios(ie...su - nagios) I 
>get the
>following:
>
>	usr/local/nagios/libexec/check_nt -H 192.168.0.7 -s 
>password123
>-v SERVICESTATE -d SHOWALL -l SMTPSVC,AVExch32Service
>	
>	SMTPSVC: Started - AVExch32Service: Started
>	
>	But within nagios on the http web page I get:
>	Service Checks(SMTP,AV)
>	
>	WARNING 10-31-2003 09:00:54 0d 0h 6m 11s 1/1 SMTPSVC: 
>Started -
>AVExch32Service$: Unknown
>	
>	Here is the definition in the services.cfg file:
>	define service {
>	host_name Exchange
>	service_description Service Checks(SMTP,AV)
>	register 1
>	max_check_attempts 1
>	normal_check_interval 3
>	retry_check_interval 1
>	check_period 24x7
>	notification_interval 0
>	notification_period 24x7
>	notification_options w,u,c,r
>	contact_groups ntadmins
>	check_command "/usr/local/nagios/libexec/check_nt -H 
>192.168.0.7
>-s password123 -v SERVICESTATE -d SHOWALL -l 
>SMTPSVC,AVExch32Service"
>	
>	Has anyone seen this problem before.......?
>	
>	
>	Thanks...
>	
>	Neil 
>



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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