stephen wing wrote: > Hi > If you are using nagios to send the messages, be careful that > sms_client has a limit of 150 characters in the text message. Depending on > what outputs you are sending from nagios, the outputs can easily become more > than 150 characters. > > Regards > Stephen > > --------------------------------------- > Stephen Wing > Steria Limited > Senior Technical Consultant > Telephone 02890393605 > Mobile 07966823605 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of James > Sent: 06 November 2007 23:59 > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] sms notify not working > > Hi everyone i'm using sms_client to send sms messages to a tap server > for sprint > > i can run the sms_client manually fine but i set it to a notify > definition and it won't execute > nagios logs shows that it executed the notify command but it doesn't > actually run the sms_client daemon at all. > In the notifications history it shows that those notify commands are > executed but it actually isn't being executed at all > I can run email notify commands fine. > > Help please? > TIA James > > Here's the notify commands i've tried : > > define command{ > command_name notify-by-sms > command_line /usr/bin/sms_client -q > sprintpcs:800xxxxxxx "$HOSTNAME$ $SERVICESTATE$\r\n Info: $OUTPUT$" > } > > define command{ > command_name notify-by-sms-testing > command_line /usr/bin/printf "%b" "Host: > $HOSTNAME$ I > nfo: $HOSTOUTPUT$\n" | sms_client -q sprintpcs:800xxxxxxx > } > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Nagios-users mailing list > Nagios-users@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 > > > > ***************************************************************** > This email originates from Steria Limited, registered office: Three Cherry > Trees Lane, Hemel Hempstead, Hertfordshire HP2 7AH; Registered in England and > Wales, number 2706218; www.steria.co.uk. > > This email and any attachments may contain confidential information and may > be subject to copyright or other intellectual property rights. It is only > for the use of the addressee(s). You are prohibited from copying, forwarding, > disclosing, saving or otherwise using it in any way if you are not the > addressee(s) or responsible for delivery. > If you receive this email by mistake, please advise the sender and cancel it > immediately. > Steria may monitor the content of emails within its network to ensure > compliance with its policies and procedures. > Any email is susceptible to alteration and its integrity cannot be assured. > Steria shall not be liable if the message is altered, modified, falsified, or > edited. > ================================================ > I stripped down the notify message to just hostname and hostoutput which shouldn't be more than like 60-70 characters altogether i had realized i had run into that problem earlier and started streamlining alot of my plugins. Thanks for the suggest tho.
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list Nagios-users@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
