Subject: | MultiCheck bug ? |
Hi Roland,
Possible bug regarding MultiCheck with 0.72_1 developer release.
This is my ouput :
check_jmx4perl --config jmx4perl.cfg --server myserver --check
jdbc_Machine_1_b
OK - All 2 checks OK
[1] OK DS_Status: Status : 'Running' as expected
[2] OK DS_ActiveConnections: ActiveConnections : Value 0 in range |
Status=Running;;!Running ActiveConnections=0;8;12
check_jmx4perl --config jmx4perl.cfg --server myserver --check
jdbc_Machine_1_a
CRITICAL - 2 of 2 failed (2 errors)
[1] CRITICAL DS_Status: Status : 'Overloaded' matches threshold '!Running'
[2] CRITICAL DS_ActiveConnections: ActiveConnections : Threshold '12'
failed for value 15 | Status=Overloaded;;!Running ActiveConnections=15;8;12
check_jmx4perl --config jmx4perl.cfg --server myserver --check
jdbc_Machine_1
OK - All 4 checks OK
[1] OK DS_Status: Status : 'Running' as expected
[2] OK DS_ActiveConnections: ActiveConnections : Value 0 in range
[3] OK DS_Status: Status : 'Running' as expected
[4] OK DS_ActiveConnections: ActiveConnections : Value 0 in range |
Status=Running;;!Running ActiveConnections=0;8;12
Status=Running;;!Running ActiveConnections=0;8;12
This is the configuration :
<MultiCheck jdbc_Machine_1>
MultiCheck jdbc_Machine_1_a
MultiCheck jdbc_Machine_1_b
</MultiCheck>
<MultiCheck jdbc_Machine_1_a>
MultiCheck jdbc_Machine_1_db01
</MultiCheck>
<MultiCheck jdbc_Machine_1_b>
MultiCheck jdbc_Machine_1_db02
</MultiCheck>
<MultiCheck jdbc_Machine_1_db01>
Check DS_Status(Machine_1,DS-db01-vip)
Check DS_ActiveConnections(Machine_1,DS-db01-vip,8,12)
</MultiCheck>
<MultiCheck jdbc_Machine_1_db02>
Check DS_Status(Machine_1,DS-db02-vip)
Check DS_ActiveConnections(Machine_1,DS-db02-vip,8,12)
</MultiCheck>
Bug description :
If I run "jdbc_Machine_1_a" check then status is CRITICAL but if I run
"jdbc_Machine_1" MultiCheck then "jdbc_Machine_1_a" status is OK but it
should be CRITICAL.
I didn't have a chance to try 0.72, so I'm not aware if It has already
been fixed with this stable release.
Giuseppe