[ZBX-19071] Preprocessing step "Check for not supported value" stops server Created: 2021 Mar 01  Updated: 2024 Apr 10  Resolved: 2021 Mar 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 5.4.0beta1
Fix Version/s: 5.2.6rc1, 5.4.0beta1, 5.4 (plan)

Type: Problem report Priority: Minor
Reporter: Aigars Kadikis Assignee: Andrejs Kozlovs
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File Check-for-not-supported-value.yaml     PNG File image-2021-03-01-17-33-33-062.png     Text File server.log    
Issue Links:
Causes
caused by ZBXNEXT-6035 Introduce "Override errors" to items Closed
Duplicate
is duplicated by ZBX-19064 "Check for not supported value" with ... Closed
is duplicated by ZBX-19093 zabbix_server crashing with segmentat... Closed
is duplicated by ZBX-19141 Zabbix server stopped cannot open IPC... Closed
is duplicated by ZBX-19315 "Check for not supported value" with ... Closed
Sub-task
Team: Team C
Sprint: Sprint 74 (Mar 2021)
Story Points: 1

 Description   

Create an item: test.trap which holds integer values.

Create a calculated item that takes the last value and substracts the previous value:

last("test.trap")-last("test.trap","#2")

Create a preprocessing step:

Deliver only one metric to test.trap item.

zabbix_sender -z 127.0.0.1 -s trap -k test.trap -o 44

Result

When the calculated item will execute the expression, the server will crash with a message:
server.log

P.S.

  • If there are two metrics in item, then it works.
  • If a preprocessing step has been removed, then it works.

Attaching template for faster reproducing:
Check-for-not-supported-value.yaml

 Comments   
Comment by Andrejs Kozlovs [ 2021 Mar 04 ]

Available in:

Comment by Marc Schiller [ 2021 Mar 12 ]

Is there any workaround? How can I figure out which item causes the crash?

Comment by Vladislavs Sokurenko [ 2021 Mar 12 ]

It is the one that uses "Check for not supported value" preprocessing step
Easy way to identify is with this:

select itemid from item_preproc where type=26;
Comment by Marc Schiller [ 2021 Mar 12 ]

Thanks

Comment by Raoel Oomen [ 2021 Mar 26 ]

Manual downgrade did not break anything for me (the mysql-query gave me 200 results, no point in fixing that manually).
Ofcourse make a backup before you try

Generated at Fri Jul 04 07:24:56 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.