check_asterisk plugin returning null

[Athiqur Rahman]

I am using the check_asterisk pluing that is found here 
http://www.voip-info.org/wiki/index.php?page_id=1864

When executing this script from bash it works like a charm

[root at watcher2 libexec]# ./check_asterisk -U sip:1111 at 192.168.53.10 -w 10 -c 50

SIP OK - Test Duration: 2.19 ms


I created the command

define command {

    command_name                   check_asterisk

    command_line                   $USER1$/check_asterisk -U $ARG1$ -P $ARG2$ -w 100 -c 500

    }


and then i created the service

define service{

        use                             generic-service

        host_name                       TVoIP1

        service_description             check_sip_asterisk

        display_name                    check for SIP on astersk

        check_command                   check_asterisk!sip:1111 at 192.168.53.10!5060

        }


This gives me critical alert on nagios with a status information of 'null'

I tried executing the check_asterisk from bash as user nagios and got 
the following

[nagios at watcher2 libexec]$ ./check_asterisk -U sip:1111 at 192.168.53.10 -w 10 -c 20

warning: need raw socket (root privileges) to receive all ICMP errors

SIP OK - Test Duration: 0.53 ms


The check_asteisk plugin uses sipsak, could this have anything to do 
with this? Any comments appreciated.

Thanks,







------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
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