-
Change Request
-
Resolution: Fixed
-
Blocker
-
5.0.14
-
None
-
Sprint 79 (Aug 2021), Sprint 80 (Sep 2021)
-
1
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?
- causes
-
ZBX-20015 Zabbix agent on windows returns message size 63 exceeds the maximum size 0 bytes.
- Closed
- depends on
-
ZBXNEXT-6862 Implement multithreaded compression/decompression of the configuration for Zabbix proxy
- Open