[ZBX-14447] Zabbix server not compatible between major version. Zabbix server 3.4.10 <=> proxy 3.4.2 Created: 2018 Jun 07 Updated: 2024 Apr 10 Resolved: 2018 Jul 03 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 3.4.10 |
| Fix Version/s: | 3.0.19rc1, 3.4.11rc1, 4.0 (plan) |
| Type: | Incident report | Priority: | Critical |
| Reporter: | finalbeta | Assignee: | Andris Zeila |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix Server on CentOS7, Proxy on rasp PI |
||
| Issue Links: |
|
||||||||||||||||
| Team: |  Team A |
||||||||||||||||
| Sprint: | Sprint 35, Sprint 36 | ||||||||||||||||
| Story Points: | 0.5 | ||||||||||||||||
| Description |
|
Steps to reproduce:
Result:
I assume this is a bug, in my Zabbix course I remember being told that Zabbix proxy and server stay compatible. The upgrade to Zabbix server 3.4.10 broke proxy compatibility with proxy 3.4.2. As I did not see this in the upgrade notes on the website, and no upgrade nodes seem to be available in the manual : https://www.zabbix.com/documentation/3.4/manual/installation/upgrade_notes_349
|
| Comments |
| Comment by finalbeta [ 2018 Jun 07 ] |
|
Can someone from Zabbix do me a favour and edit out the hostname in the log? (stupid mistake, sry). Seems I can't edit the post anymore. |
| Comment by Vladislavs Sokurenko [ 2018 Jun 07 ] |
|
Probably caused by |
| Comment by Marc [ 2018 Jun 07 ] |
|
I can confirm this. I'm getting the same error message!
Edit: Just checked the version of one of the proxies: zabbix-proxy-sqlite3-3.4.8-1.el7.x86_64 |
| Comment by Andris Zeila [ 2018 Jun 08 ] |
|
Released in:
|
| Comment by Danny Sokolovski [ 2018 Jun 08 ] |
|
using proxy 3.4.5 also not working with server 3.4.10
8119:20180608:200714.006 failed to update local proxy configuration copy: unexpected field "hosts.available" |
| Comment by Alex [ 2018 Jun 19 ] |
|
Zabbix server 3.0.18 also does not work with zabbix proxy 3.0.10. An error occurs on the zabbix-proxy side: "failed to update local proxy configuration copy: unexpected field "hosts.available". |
| Comment by Eduardo Wutzl da Silva [ 2018 Jun 19 ] |
|
System Log: 72368:20180619:123701.655 Starting Zabbix Proxy (active) [main_proxy]. Zabbix 3.4.6 (revision 76823). 72368:20180619:123701.655 **** Enabled features **** 72368:20180619:123701.655 SNMP monitoring: YES 72368:20180619:123701.655 IPMI monitoring: YES 72368:20180619:123701.655 Web monitoring: YES 72368:20180619:123701.656 VMware monitoring: YES 72368:20180619:123701.656 ODBC: YES 72368:20180619:123701.656 SSH2 support: YES 72368:20180619:123701.656 IPv6 support: YES 72368:20180619:123701.656 TLS support: YES 72368:20180619:123701.656 ************************** 72368:20180619:123701.656 using configuration file: /etc/zabbix/zabbix_proxy.conf 72368:20180619:123701.664 current database version (mandatory/optional): 03040000/03040006 72368:20180619:123701.664 required mandatory version: 03040000
72369:20180619:123902.250 received configuration data from server at "10.25.232.121", datalen 719277 72369:20180619:123902.252 failed to update local proxy configuration copy: unexpected field "hosts.available" 72369:20180619:124102.369 received configuration data from server at "10.25.232.121", datalen 719277 72369:20180619:124102.370 failed to update local proxy configuration copy: unexpected field "hosts.available" 72369:20180619:124302.491 received configuration data from server at "10.25.232.121", datalen 719277 72369:20180619:124302.493 failed to update local proxy configuration copy: unexpected field "hosts.available" 72369:20180619:124502.613 received configuration data from server at "10.25.232.121", datalen 719277 72369:20180619:124502.615 failed to update local proxy configuration copy: unexpected field "hosts.available"
|
| Comment by Erik Brakkee [ 2018 Jun 25 ] |
|
We have noticed a similar incompatibility. Specifically, zabbix proxy 3.4.11-1.el7.x86_64 is incompatible with server version zabbix-server-mysql-3.4.10-1.el7.x86_64. We are seeing the following error in the zabbix proxy log (/var/log/zabbix/zabbix_proxy.log).
19474:20180625:173140.136 failed to update local proxy configuration copy: unexpected field "hosts.available"
Downgrading zabbix-proxy to 3.4.10-1 fixes the issue.
|
| Comment by Aleksandrs Saveljevs [ 2018 Jul 02 ] |
|
We have just upgraded from version 3.4.10 to 3.4.11. Zabbix proxy was the first to restart and logged the following when talking to 3.4.10 server: 30990:20180702:160520.086 received configuration data from server at "127.0.0.1", datalen 83515 30990:20180702:160520.087 failed to update local proxy configuration copy: unexpected field "hosts.available" So it seems that there is some incompatibility between proxy 3.4.11 and server 3.4.10, as erikengerd already pointed out. |
| Comment by Andris Zeila [ 2018 Jul 02 ] |
|
Yes, 3.4.10 is neither backwards or forwards compatible. It's not quite clear from documentation though. |
| Comment by Glebs Ivanovskis [ 2018 Jul 02 ] |
|
Probably worth adding a server/proxy compatibility matrix to Version compatibility page. Similar to this one: |
| Comment by Josh Soref [ 2018 Jul 05 ] |
|
The same sort of version compatibility that was added to https://www.zabbix.com/documentation/3.4/manual/appendix/compatibility should probably be added to https://www.zabbix.com/documentation/3.0/manual/appendix/compatibility |
