Trigger re-sent at each item cycle

[gleepwurp]

Having some issues with a trigger set to an SNMP item.

The trigger is configured to generate an event should the last value of an SNMP ITEM be different than "1":

{sysChassisPowerSupplyStatus.2.last()}<>1

How ever, each 120 Seconds (the item's cycle time), the trigger gets re-sent...
The ITEM is verified as having a constant value of "2" for each cycle for the past day, and the trigger keeps sending out events, as if it forgot it already triggered the event in the previous cycle...

I have enabled the debug log, but nothing pops up:

1767:20141118:154749.178 In evaluate_function() function:'Server.something:sysChassisPowerSupplySt atus.2.last()'
1767:20141118:154749.178 In evaluate_LAST()
1767:20141118:154749.178 In __get_function_parameter_uint31() parameters:'' Nparam:1
1767:20141118:154749.178 In substitute_simple_macros() data:EMPTY
1767:20141118:154749.178 __get_function_parameter_uint31() flag:1 value:1
1767:20141118:154749.178 End of __get_function_parameter_uint31():SUCCEED
1767:20141118:154749.178 In zbx_vc_get_value_range() itemid:33303 value_type:3 seconds:0 count:1 timestamp:1416343668
1767:20141118:154749.178 End of zbx_vc_get_value_range():SUCCEED count:1 cached:1
1767:20141118:154749.178 End of evaluate_LAST():SUCCEED
1767:20141118:154749.179 End of evaluate_function():SUCCEED value:'2'


Any ideas?

Thanks!

G.

[ArtemK]

which zabbix version do you use? AFAIK, 'not equal' should be defined as #, not <>. Maybe there is problem?

[gleepwurp]

Hello,

I'm using 2.4.2... As of 2.4.0, the "NOT" operator has been replaced from "#" to "<>" (https://www.zabbix.com/documentation...on/whatsnew240 section 5).

I also used the "Last (most recent) T value is NOT N" function in the Trigger expression constructor, and the "<>" operator is what was put in as a result...

It's really weird. I don't know if it might be a side-effect from changing the NOT operator in the Zabbix code?

Thanks for the reply!

G.

[ArtemK]

Ok, I don't think that there is some side-effect from changing operator.

Do you have "Multiple PROBLEM events generation" enabled in trigger options?

[gleepwurp]

Ahh! My friend, I think you found my problem!

It is selected... we had 2 pair of eyes here, any we didn't notice it...

I'll update the trigger to remove this option and validate...

Thank you for your quick reply!

G.