On 13 Jul 2009, at 00:29, Roy wrote:
This is the check command that I have
check_snmp -H $HOSTADDRESS$ -C $SNMP_COMMUNITY$ -l Status -m
READYNAS-MIB -o volumeStatus.1 -s "\"ok\""
When I issue it from the command line, I get
./check_snmp -H 10.10.100.xxx -C xxxx -l Status -m READYNAS-MIB -o
volumeStatus.1 -s "\"ok\""
Status OK - "ok" | READYNAS-MIB::volumeStatus.1="ok"
What I see in Opsview 3.0 on the service status page is
Current Status: CRITICAL (for 0d 0h 45m 27s)
Status Information: Status CRITICAL - *"ok"*
Performance Data: READYNAS-MIB::volumeStatus.1="ok"
On 2.12.5 I see the same page shows
Current Status: OK Status Information: Status OK - "ok"
Performance Data: READYNAS-MIB::volumeStatus.1="ok"
There was an enhancement we made in Opsview 3 where the parameters are
passed as args to a check command. In Opsview 2, we created new
service check commands for each service, which was wasteful.
However, it looks like the parameters are double escaped - once for
the arguments and then again at the command. I think this is the
discrepancy you are seeing.
I've tried to get a consensus in the Nagios community for the correct
fix, but have not had any luck. I think we'll end up having to make a
patch to our own version of Nagios independently.
In the meantime, the arguments should be:
check_snmp -H $HOSTADDRESS$ -C $SNMP_COMMUNITY$ -l Status -m READYNAS-
MIB -o volumeStatus.1 -s "\\"ok\\""
(Note: the back slashes are escaped).
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
