<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <title>RE : [Nagios-users] Sybase check on windows servers</title> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Florent,<o:p></o:p> Thank you so much for being patient with me. I tried what you said. But unfortunately I am still getting the error “return code of 139 is out of bounds”.<o:p></o:p> Here is my configuration-<o:p></o:p> <o:p> </o:p> Hostgroups.cfg-<o:p></o:p> <o:p> </o:p> define hostgroup{<o:p></o:p> hostgroup_name sybasetest<o:p></o:p> alias Sybase Servers Test<o:p></o:p> members ganges,nila<o:p></o:p> }<o:p></o:p> <o:p> </o:p> Commands.cfg-<o:p></o:p> <o:p> </o:p> define command{<o:p></o:p> command_name check_sybase<o:p></o:p> command_line $USER1$/check_nt -v SERVICESTATE -d SHOWALL -l $ARG1$ $ARG2$<o:p></o:p> }<o:p></o:p> <o:p> </o:p> Services.cfg-<o:p></o:p> <o:p> </o:p> define service{<o:p></o:p> use local-service<o:p></o:p> hostgroup_name sybasetest<o:p></o:p> service_description Sybase<o:p></o:p> check_command check_sybase!0!SYBSQL_$HOSTNAME$<o:p></o:p> }<o:p></o:p> <o:p> </o:p> Kindly help.<o:p></o:p> <o:p> </o:p> Regards,<o:p></o:p> Lalita<o:p></o:p> <div> <o:p></o:p> From: Florent HOUBART [mailto:Florent.HOUBART@Ajilon.fr] Sent: Monday, June 25, 2007 4:54 PM To: Lalita Drolia Cc: nagios-users@lists.sourceforge.net Subject: RE : [Nagios-users] Sybase check on windows servers<o:p></o:p> </div> <o:p> </o:p> Hi, >I am using nagios2.9 and Nagios plugins 1.4.9. > >I have made a hostgroup for Sybase servers of the sort- > >define hostgroup{ > hostgroup_name sybase > alias Sybase Servers > members machine1,machine2,machine3,machine4,machine5 > } > >Now I want to know if its possible to define a single service for all >these machines as the service name differs in each server because it is- >Sybsql-machine1,sybsql_machine2,sybsql_machine3 etc. > >Can you please also provide me help on command definition and service >definition for Sybase check on linux machines. Here is a small test I done to validate that using HOSTNAME in serice definition is OK. You can adapt this exemple with your real commands. I use the dummy check to verify if the hostname is well read by the command. This plugin take in first argument the return value, and in second the status message. I have two hosts, host1 and host2, and a hostgroup containing the two hosts. I then define the service on the hostgroup. I use the $HOSTNAME$ macro in service definition to specify parameters. ################################## # Command definition # 'check_dummy' command definition define command{ command_name check_dummy command_line $USER1$/check_dummy $ARG1$ $ARG2$ } ################################## # hosts definition definition define host{ use linux-server host_name host1 alias Host1 address 127.0.0.1 } define host{ use linux-server host_name host2 alias Host2 address 127.0.0.1 } ################################## # Hostgroup definition define hostgroup{ hostgroup_name Sybase ; The name of the hostgroup alias Sybase servers ; Long name of the group members host1,host2 ; Comma separated list of hosts that belong to this group } ################################## # Service definition define service{ use local-service hostgroup_name Sybase ; I specify here the hostgroup service_description Sybase check_command check_dummy!0!SYBSQL_$HOSTNAME$ ; The $HOSTNAME$ will be replaced by Nagios by the name of the host } In nagios console, I then have : host1 Sybase OK: SYBSQL_host1 host2 Sybase OK: SYBSQL_host2 Best regards, Florent <o:p></o:p> </div> </body> </html> Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.