[ZBX-8348] Substitution in some triggers from LDD Created: 2014 Jun 11  Updated: 2017 May 30  Resolved: 2014 Jun 13

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.2.3
Fix Version/s: 2.0.13rc1, 2.2.4rc3, 2.3.2

Type: Incident report Priority: Critical
Reporter: Alexey Pustovalov Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: expressions, lld, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate

 Description   

Sometimes LLD rule can create not correct triggers from trigger prototypes. It can exchange conditions from two and more trigger expression parts.
For example, trigger prototype is ({host:item[

{#MACRO}].regexp(^TEST$)})=0&{host:item[{#MACRO}

].strlen(#2)}#2. So triggers are created from the prototype can have the next expression ({host:item[

{#MACRO}].regexp(^TEST$)})#2&{host:item[{#MACRO}

].strlen(#2)}=0



 Comments   
Comment by Alexander Vladishev [ 2014 Jun 13 ]

It could occur in a case when part of functions have bigger IDs than in the table 'ids'.

For example:

  • triggers
    triggerid expression
    402910 ( {100100043858669}

    )#2&

    {722847}

    =0

    402911 ( {100100043858670}

    )#2&

    {722848}

    =0

    402912 ( {100100043858671}

    )#2&

    {722849}

    =0

  • ids
    table_name field_name nextid
    functions functionid 723258

It not normal case. The table 'ids' shall contain correct information.

Fixed in the development branch svn://svn.zabbix.com/branches/dev/ZBX-8348

Comment by Alexander Vladishev [ 2014 Jun 16 ]

Fixed in pre-2.0.13 r46532, pre-2.2.4 r46533 and pre-2.3.2 (trunk) r46534.

Generated at Thu Mar 28 12:41:21 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.