Version 4.2 errors with proxies

[vlam]

Hi

I have upgraded one of my environments to 4.2 so that we can start to test it, this environment also has 2 proxies in it.

Currently there is some items that does produce data but for the most of it I get the following:

Zabbix server:
4325:20190405:064355.149 unknown request received [host availability]
94325:20190405:064355.267 unknown request received [history data]
94301:20190405:064355.272 unknown request received [host availability]
94304:20190405:064355.307 unknown request received [host availability]
94323:20190405:064355.375 unknown request received [auto registration]
94282:20190405:064355.391 unknown request received [history data]
94306:20190405:064355.431 unknown request received [history data]
94296:20190405:064355.500 unknown request received [auto registration]
94296:20190405:064355.540 unknown request received [auto registration]

Zabbix Proxy:
51674:20190405:063725.845 cannot send history data to server at "zabbapp": empty string received
51674:20190405:063726.847 cannot send host availability data to server at "zabbapp": empty string received
51674:20190405:063726.973 cannot send history data to server at "zabbapp": empty string received
51674:20190405:063727.083 cannot send history data to server at "zabbapp": empty string received
51674:20190405:063728.086 cannot send host availability data to server at "zabbapp": empty string received
51674:20190405:063728.206 cannot send history data to server at "zabbapp": empty string received
51674:20190405:063728.316 cannot send history data to server at "zabbapp": empty string received
51674:20190405:063729.318 cannot send host availability data to server at "zabbapp": empty string received
51674:20190405:063729.438 cannot send history data to server at "zabbapp": empty string received

[GustavoVegas]

Did you ever resolve this issue?
I am having a similar problem with a 4.4 setup. The server is logging "Unknown requests from <proxy IP>: [auto registration]" and the proxy's log shows "cannot send history data to server at "<Server FQDN>": empty string received". I have checked the network setup and both server and proxy can connect to each other over port 10051, and the server can connect to the proxy over port 10050. I am wondering if both ports need to be opened in both directions.

[vlam]

Hi

In our case it was the Proxy that did not upgrade it's database correctly so the info it received from the Zabbix servers was massively different and that caused then to talk in different tables, we dropped the database on the proxy and re-created it from scratch

[GustavoVegas]

It has been a little while since I looked at this, I think I ended up doing both, dropping the database, recreating from scratch, and also opening up the firewall(s) in both directions.