Zabbix Win 5.0 client can't to Zabbix server 4.0

[bartman10]

Windows 2019 Agent 5 sending logs to Zabbix 4 and Zabbix 5 server using PSK encryption. Works with Linux clients v5
On Win clients we see the error below in the Zabbix 4 server.


cannot parse list of active checks from [clientcomputer.com:10051]: json: cannot unmarshal number into Go struct field Request.data.delay of type string

In the Zabbix 4 server we did see info about the server like ping but no windows logs.

[Atsushi]

If you use Zabbix server version 4.0, Zabbix agent version should be 4.0 or lower. Alternatively, consider upgrading your Zabbix server version to 5.0 or later.
Manual:

https://www.zabbix.com/documentation/4.0/en/manual/appendix/compatibility

Note that Zabbix agent newer than 4.0 cannot be used with Zabbix server 4.0.

[bartman10]

We are migrating to Zabbix 5. There are reasons beyond my control for these requirements.

I think I answered my own question though. Using Zabbix Agent 5 V1 worked. It was only V2 that wasn't sending logs.

So the answer seems to be Zabbix 4 server needs V1 clients.

[Markku]

So the answer seems to be Zabbix 4 server needs V1 clients.

You are pushing your luck That's not an "answer", that's just your personal attempt to disregard the documentation that was presented to you. If your Zabbix data and function are not valuable for you, you are obviously free to do whatever you like. If it breaks, you can keep all the pieces.

If you are migrating from 4 to 5, the correct order is to first upgrade the server (and proxies), and after that upgrade the agents (if agent upgrades are needed by your own requirements, that is not generally required by the Zabbix system). That's because of the mentioned documentation: older agents are generally compatible with newer servers, but newer agents are not documentedly compatible with older servers.

Markku

[eadingandesite]

PSK-encrypted logs are being sent from Windows 2019 Agent 5 to Zabbix 4 and Zabbix 5 servers in 2019. Supports version 5 of the Linux client. This problem appears on Windows clients while connecting to a Zabbix 4 server.phrazle