-
Documentation task
-
Resolution: Fixed
-
Trivial
-
4.2.5
-
None
-
None
-
Zabbix server 4.2.5
Zabbix proxy 3.2.x
-
Sprint 55 (Aug 2019)
In the documentation of version 4.2 there is still a statement:
Backwards compatibility
Server supports partial backwards compatibility by accepting old host availability, history data, discovery data and auto registration requests.
But in reality, it seems that the code was removed. In 4.0 there is still code in src/zabbix_server/trapper/trapper.c
/****************************************************************************** * * * Function: recv_proxyhistory * * * * Purpose: processes the received values from active proxies * * * ******************************************************************************/ static void recv_proxyhistory(zbx_socket_t *sock, struct zbx_json_parse *jp, zbx_timespec_t *ts) ..... out: /* 'history data' request is sent only by pre 3.4 version proxies */ /* that did not have compression support */ ....... }
In version 4.2 it is no longer there
grep recv_proxyhistory zabbix-4.2.5/src/zabbix_server/trapper/trapper.c
The incorrect statement should be removed from documentation.
As a result, if there is an outdated proxy connecting to Zabbix server, there is a very undescriptive error written in the log:
3469:20190814:091418.139 unknown request received [host availability]
every time that proxy tries to connect to the server.
I will create an additional ZBX about this.
- causes
-
ZBX-16511 Undescriptive error in log - unknown request received [host availability]
- Closed