What is $USER7$ macro? In your resource.conf?
Likely to be the Community string, as that is what resource.conf is generally for.
"check_snmp_mem.pl -H 41.211.3.218 $USER7$ communitystring -w -I -c 80 98"
Is what your command translates too, which wouldn't work.
________________________________________
From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Alex Dehaini
Sent: 04 March 2008 10:47
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] check_snmp_mem.pl
Hi Guys,
I am having difficulties using this plugin. I can't get it to work. Can you guys help me please. What is syntax in the commands.cfg file and in the service file of the cisco router I intend to monitor. This is what I have
commands.cfg
define command{
command_name check_snmp_mem_v1
command_line $USER1$/check_snmp_mem.pl -H $HOSTADDRESS$ $USER7$ $ARG1$ -w $ARG2$ -c $ARG3$ $ARG4$
}
In my service definition file
define service{
use core-rservice
host_name core
service_description Memory
check_command check_snmp_mem_v1!communitystring!-I!80!98
}
This is the result I get in nagios web cgi
Memory
CRITICAL
03-04-2008 09:29:57
0d 14h 2m 0s
6/6
(Return code of 127 is out of bounds - plugin may be missing)
I reckon I am not doing something right because the plugin works from the command line i.e.
snmp:/usr/local/nagios/libexec# ./check_snmp_mem.pl -H 41.211.3.218 -C communitystring -I -w 40% -c 90%
Processor:24%,I/O:60% : 28% : > 40 ; WARNING
What am I doing wrong?
--
Alex Dehaini
Developer
Site - www.alexdehaini.com
Email - alexdehaini at gmail.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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