Error: Service check command 'check_mssql.sh... not defined anywhere!

[Patrick Soltani]

Hi,
Funny I caught my mistake only after I read my own post :-).
check_mssql.sh should have been check_mssql; just in case curious minds wanted to know.


Thanx and Regards,
Patrick Soltani.

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net
> [mailto:nagios-users-admin at lists.sourceforge.net]On Behalf Of Patrick
> Soltani
> Sent: Friday, February 13, 2004 6:20 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Error: Service check command 
> 'check_mssql.sh...
> not defined anywhere!
> 
> 
> Hi,
> Nagios is 1.1 and is working fine.  Got check_mssql.sh to 
> work on the command line: 
> 
> root at nagios:/usr/local/nagios/libexec #./check_mssql.sh 
> webdev02 sqltest sqltest 7
> OK - MS SQL Server 7 has 1 user(s) connected: 1 12345.
> 
> To automating it, did 
> - Added the following 4 entries to "resource.cfg"
> $USER3$=webdev02
> $USER4$=sqltest
> $USER5$=sqltest
> $USER6$=7
> 
> - Added the following lines to "checkcommands.cfg"
> # 'check_mssql' command definition
> define command{
>         name            MSSQL
>         command_name    check_mssql
>         command_line    $USER1$/check_mssql.sh $USER3$ 
> $USER4$ $USER5$ $USER6$
>         }
> 
> - Added the following lines to "services.cfg"
> # Service definition webdev02 SQL
> define service{
>         use                             generic-service       
>   ; Name of service template to use
>         host_name                       webdev02
>         service_description             MSSQL
>         is_volatile                     0
>         check_period                    24x7
>         max_check_attempts              3
>         normal_check_interval           5
>         retry_check_interval            1
>         contact_groups                  AllAdmins
>         notification_interval           480
>         notification_period             24x7
>         notification_options            w,u,c,r
>         check_command                   
> check_mssql.sh!$USER3$!$USER4$!$USER5$!$USER6$
>         }
> 
> Other services ran by Nagios against this host are working 
> fine, however, 
> root at nagios:/usr/local/nagios/etc 
> #/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
> 
> Nagios 1.1
> Copyright (c) 1999-2003 Ethan Galstad (nagios at nagios.org)
> Last Modified: 06-02-2003
> License: GPL
> 
> Reading configuration data...
> 
> Running pre-flight check on configuration data...
> 
> Checking services...
> Error: Service check command 'check_mssql.sh' specified in 
> service 'MSSQL' for host 'webdev02' not defined anywhere!
>         Checked 33 services.
> .............snipp.....
> Total Warnings: 0
> Total Errors:   1
> 
> 
> What am I missing?
> Been googling for few hours and *re-read* the documentation 
> and still can't figure out where the problem is?
> Appreciate any pointers, info, URL,....
> 
> Thanx and Regards,
> Patrick Soltani.
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id56&alloc_id438&op=ick
> _______________________________________________
> 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
> 


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click
_______________________________________________
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