[ZBX-20569] Zabbix 6 HTTP master item: If collected data is too long for item information type, dependent items don't get values Created: 2022 Feb 10  Updated: 2024 Apr 10  Resolved: 2022 Mar 30

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 6.0.0rc2
Fix Version/s: 6.2 (plan)

Type: Problem report Priority: Major
Reporter: Nathan Liefting Assignee: Vladislavs Sokurenko
Resolution: Duplicate Votes: 1
Labels: bug, dependentitems, httpcheck, masteritems
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2022-02-10 at 16.47.12.png     File zbx_export_hosts (1).yaml    
Issue Links:
Duplicate
duplicates ZBX-20450 Issue with cyrillic names of items an... Closed
Team: Team A
Sprint: Sprint 85 (Feb 2022), Sprint 86 (Mar 2022)
Story Points: 0.5

 Description   

In Zabbix 6:

If collected data is too long for item information type, dependent items don't get values. UNLESS we select Do not keep history.

Steps
1. If we create the HTTP item while keeping history:

2. The HTTP item receives data that's too long to store in the TEXT table. Error in the server log file:

814550:20220210:163300.210 [Z3005] query failed: [1406] Data too long for column 'value' at row 1 [insert into history_text (itemid,clock,ns,value) values (81479,1644507179,834906558,'{"id":"cardano","symbol":"ada","name":"Cardano","asset_platform_id":null,"platforms":{"":""},"block_time_in_minutes":0,"hashing_algorithm":null,"categories":["Smart Contract Platform",null],"public_notice":null,"additional_notices":[],"localization":{"en":"Cardano","de":"Cardano","es":"Cardano","fr":"Cardano","it":"Cardano","pl":"Cardano","ro":"Cardano","hu":"Cardano","nl":"Cardano","pt":"Cardano","sv":"Cardano","vi":"Cardano","tr":"Cardano","ru":"Кардано","ja":"エイダ","zh":"艾达币","zh-tw":"艾達幣","ko":"에이다","ar":"كاردانو","th":"Cardano","id":"Cardano"},"description":{"en":"Cardano is a decentralised platform that will allow complex programmable transfers of value in a secure and scalable fashion. It is one of the first blockch

 

3. Create a dependent item on the HTTP master item.

4. Dependent item won't be populated.

5. Set Do Not keep history on the master item and see the dependent item receiving data now.

 

As dependent items should receive data from the master item even before the value is being stored to the database, this should not happen. It is breaking exisiting implementations as the Zabbix 5 version did allow this to work.

 

 

 



 Comments   
Comment by Vladislavs Sokurenko [ 2022 Mar 29 ]

Thank you for your report, unfortunately issue could not be reproduced, could you please be so kind and show output of following command ?

show create table history_text;
Comment by Vladislavs Sokurenko [ 2022 Mar 29 ]

Closing as cannot reproduce, please feel free to reopen if there is additional information.

Comment by Brian van Baekel [ 2022 Mar 29 ]

Not so fast @vso, just give us some time to respond

OS: RHEL8
DB: Mariadb 10.5.15
Zabbix: 6.0.0

Just to make reproducing a little easier, attached the host so you don't have to build it yourself.
zbx_export_hosts (1).yaml

Import host, config cache reload, tail -f on zabbix_server.log and a execute now should give the error.

Comment by Vladislavs Sokurenko [ 2022 Mar 29 ]

Thanks for the host, unfortunately still cannot reproduce, could you please be so kind and show output of:

show create table history_text; 
Comment by Brian van Baekel [ 2022 Mar 29 ]

Completely vanilla 6.0.0 installation...

[zabbix]> show create table history_text;
+--------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table        | Create Table                                                                                                                                                                                                                                                                                   |
+--------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| history_text | CREATE TABLE `history_text` (
  `itemid` bigint(20) unsigned NOT NULL,
  `clock` int(11) NOT NULL DEFAULT 0,
  `value` text COLLATE utf8mb4_bin NOT NULL,
  `ns` int(11) NOT NULL DEFAULT 0,
  PRIMARY KEY (`itemid`,`clock`,`ns`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin |
+--------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.000 sec)
Comment by Vladislavs Sokurenko [ 2022 Mar 29 ]

Also tried with Server version: 5.5.5-10.5.15-MariaDB-1:10.5.15+Maria~focal
Could you please share output of zabbix_server -V

Comment by Brian van Baekel [ 2022 Mar 29 ]
# zabbix_server -V
zabbix_server (Zabbix) 6.0.0
Revision 5203d2ea7d 14 February 2022, compilation time: Feb 14 2022 16:12:33

Copyright (C) 2022 Zabbix SIA
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it according to
the license. There is NO WARRANTY, to the extent permitted by law.

This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/).

Compiled with OpenSSL 1.1.1g FIPS  21 Apr 2020
Running with OpenSSL 1.1.1k  FIPS 25 Mar 2021
Comment by Vladislavs Sokurenko [ 2022 Mar 29 ]

Thanks, this is most likely a duplicate of ZBX-20450 then, please upgrade and see if issue persists

Comment by Brian van Baekel [ 2022 Mar 29 ]

Upgrade seems to fix it; no idea whether it was a duplicate of ZBX-20450 or something.

Comment by Vladislavs Sokurenko [ 2022 Mar 29 ]

Yes, it should have been caused by ZBX-20450 as it had trouble with setting correct encoding, thanks for feedback.

Generated at Tue Jun 10 07:46:59 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.