>Where did you get this plugin? It doesn't appear to live at any of the
>common plugin repositories.
>
>This seems reasonable, provided servername is a FQDN and is the same
>as what you tested above.
>
>>
>> However, when nagios runs, it returns
>>
>> SIP CRITICAL: SIP failure ("...")
>
>Does it really print '("...")' or is that creative editing? If there's
>more output, please post it. Have you looked at the script to see
>under what conditions that's shown?
>
>My guess would be an environment issue. The script may call external
>programs but not specify the full paths to them, may depend on
>environment variables that are not present, etc.
>
>--
>MarcMany thanks for the reply The plugin is from http://exchange.nagios.org/directory/Plugins/Network-Protocols/*-VoIP/SIP/check_sip-sipsak/details Just renamed to check_sipsak as check_sip is already in use Running the command via CLI as the nagios user gives the desired results, so I am unsure As to how environmental variables would affect the output. Yes, the error posted is the returned result, not creative editing..;o) I will post should I find a solution. Many thanks to all who have responded. Regards Tom This electronic communication and the attached file(s) are subject to a disclaimer which can be accessed on the following link: Disclaimer - or copy the following URL into your browser - http://www.mweb.co.za/disclaimer. If you are unable to view the disclaimer, please contact [email protected] for a copy. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Nagios-users mailing list [email protected] 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
