[ZBX-16137] Server 3.0.12 can not connect to agent 4.0.4 Created: 2019 May 17  Updated: 2019 Aug 01  Resolved: 2019 May 17

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G), Server (S)
Affects Version/s: None
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Jeroen Baten Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu server 18.04 with repo version Zabbix server 3.0.12
Ubuntu desktop 19.04 with repo version Zabbix agent 4.0.4

Attachments: File ZBX-16137.diff    

 Description   

Steps to reproduce:

This started after an upgrade of the workstation to 19.04.

Result:

Agent logfile says:

11736:20190517:073734.806 Message from 10.1.1.1 is missing header. Message ignored.

Expected:
Well, a server-agent connection would be nice



 Comments   
Comment by Oleksii Zagorskyi [ 2019 May 17 ]

Yes, forward compatibility does not work in this exact case, like server pre-4.0 and agent 4.0+

Comment by Jeroen Baten [ 2019 May 17 ]

I know it's not an argument but I have never had this problem before. Example: running server 16.04 and clients 16.10-17.10.

So, basically, I have to upgrade my server and all other clients to 4.0 now?

Comment by Oleksii Zagorskyi [ 2019 May 17 ]

Yes, in the past it was possible and most likely will be possible in future versions.
But not in the current case, as I said previously.

What to do - you should decide yourself.

I'm closing this issue as it's not a bug.

Comment by Glebs Ivanovskis [ 2019 May 17 ]

kwoot, see documentation regarding version compatibility.

I have never had this problem before.

You were lucky. It worked just because it worked, there were no guarantees for it to work. Compatibility between older server/proxy and newer agent has never been officially supported.

I have to upgrade my server and all other clients to 4.0 now?

Upgrading server (and proxies) is one of the options. You don't have to upgrade all agents — new server/proxy will work with older agents, this is officially supported. Another option is to downgrade agents to 3.0 (also officially supported). And yet another option is to switch from passive to active checks (this is not officially supported though).

Comment by Jeroen Baten [ 2019 May 17 ]

I tried switching to active agent and that made no difference. I was unable to find a 3.0 agent package for ubuntu 19.04.

Comment by Glebs Ivanovskis [ 2019 May 17 ]

I tried switching to active agent and that made no difference.

Have you changed item type in the frontend?

Generated at Fri Apr 26 01:51:30 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.