[ZBXNEXT-6840] Proxy fails to receive large configuration Created: 2021 Aug 19  Updated: 2024 Oct 15  Resolved: 2021 Sep 17

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: 5.0.14
Fix Version/s: 5.0.16rc1, 5.4.5rc1, 6.0.0alpha3, 6.0 (plan)

Type: Change Request Priority: Blocker
Reporter: Edgars Melveris Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File ZBXNEXT-6840-2.diff    
Issue Links:
Causes
causes ZBX-25301 Unconditional 64-bit code in proxy co... Closed
causes ZBX-20015 Zabbix agent on windows returns messa... Closed
Duplicate
Sub-task
depends on ZBXNEXT-6862 Implement multithreaded compression/d... Open
Team: Team A
Sprint: Sprint 79 (Aug 2021), Sprint 80 (Sep 2021)
Story Points: 1

 Description   

Proxy configuration with 78k hosts and 11M items fails to load, configuration syncer outputs this in log:

 39364:20210818:173200.698 zbx_setproctitle() title:'configuration syncer [loading configuration]'
 39364:20210818:173200.698 In process_configuration_sync()
 39364:20210818:173200.698 In connect_to_server() [x.x.x.x]:10051 [timeout:600]
 39364:20210818:173200.698 In zbx_tls_connect(): psk_identity:"PROXY"
 39364:20210818:173200.698 zbx_psk_client_cb() requested PSK identity "PROXY"
 39364:20210818:173207.858 End of zbx_tls_connect():SUCCEED (established TLSv1.3 TLS_CHACHA20_POLY1305_SHA256)
 39364:20210818:173207.858 In get_data_from_server() request:'proxy config'
 39364:20210818:173830.777 End of get_data_from_server():FAIL
 39364:20210818:173830.777 cannot obtain configuration data from server at "x.x.x.x": cannot uncompress data: not enough space in output buffer
 39364:20210818:173830.778 End of process_configuration_sync()
 39364:20210818:173830.778 zbx_setproctitle() title:'configuration syncer [synced config 0 bytes in 390.080612 sec, idle 300 sec]'

Is this running into some limits:
cannot uncompress data: not enough space in output buffer
And how can such limits be increased?

 Comments   
Comment by Vladislavs Sokurenko [ 2021 Aug 19 ]

It should not be possible because documented limit is 1G, only if it was manually changed to higher one and recompiled, to support more than 4G would need to introduce new protocol flag 0x4 that will send sizes as uint64 instead of uint32, this will allow setting any limit when recompiling.

Comment by Vladislavs Sokurenko [ 2021 Sep 13 ]

Implemented in:

Updated documentation:

Generated at Wed Dec 25 16:11:49 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.