Getting null when checking remote load.

[Tõnis Trei]

Hello,

I have run into a small problem when tried to set up Nagios on a new system
from scratch and can't figure out whats wrong. Everything looks to be kinda
ok but maybe im overseeing something :)

Nagios is returning NULL when checking load on a remote machine.

I defined service:
define service {
        use                             generic-service
        hostgroup_name                  linux-servers
        service_description             load
        check_command
check_remote_load!$_HOSTLOADWARNING$!$_HOSTLOADCRITICAL$
        servicegroups                   +load
        first_notification_delay        10
        contact_groups
}

and i defined a command in command.cfg
define command{
        command_name    check_remote_load
        command_line    $USER1$/check_munin.pl -H $HOSTADDRESS$ -M load -w
$ARG1$ -c $ARG2$
}

Check_munin.pl is added on a remote machine.
Munin is installed on the same machine as Nagios and the IP is in ALLOW list
on munin remote node.
Also munin.conf contains the entry for the remote host.

But for some reason i still get back null when forcing nagios to check the
load.

Any thoughts on what wrong or how to debug this? :)

Best wishes,
Tõnis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110608/10f1bb03/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
-------------- next part --------------
_______________________________________________
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