Zabbix Proxy 3.0 connection reset/interrupted system call after a while

[boetn]

Hi,

This is my first post here, so far I have found the answer to my problems, but now I have run into a problem I can't seem to solve.

We have a setup with 1 central server and about 20 proxies. I've upgraded the Zabbix server to 3.0 and I'm in progress of upgrading the proxies. All the proxies that aren't upgraded yet are currently stopped.

The proxies connect correctly to the server but after a while the zabbix proxy doesn't seem to be able to connect to the server anymore, the proxy gives the errors:

cannot send history data to server at "...": ZBX_TCP_WRITE() failed: [104] Connection reset by peer
cannot send heartbeat message to server at "...": ZBX_TCP_READ() failed: [4] Interrupted system call

In the zabbix server I can see that the 4 proxies that are running, are using 50 connections together that are in the ESTABLISHED state and each have about 2/3 connections that are in the SYN_RECV state.

Can anybody give me a hint into what could be wrong?

Thanks in advance!

[boetn]

Can anybody help me out please? This is a really annoying issue.
All the proxies close their connection after about an hour or 2.

If any more information is needed or if I need to run some tests I'm happy to do it.

[Atsushi]

Please check the configuration of network equipment.
Depending on the configuration, it might cut connection by idle state continue.

[boetn]

Please check the configuration of network equipment.
Depending on the configuration, it might cut connection by idle state continue.

Thanks for your reply Atsushi. I find it strange that this only started to happen after an upgrade to 3.0, nothing changed in the configuration of the network. Everything was working fine for about a year now. Or could this be due to an architectural change?

It's also stange the data is transferred correctly for about an hour or so and after that the problem starts to occur.

I will have a look at the network anyway to be sure.

[boetn]

Disabling all of the firewall features was indeed the solution. I will now have a look which rule was causing the error.
Thanks for the tip Atsushi!

[boetn]

Edit: not fixed after all. I now even installed a local proxy: the problem still occurs.

[Rasvari]

Same problem here

Sorry about posting to an old thread.

Upgraded from 2.2 -> 3.04 with active proxy.

Random connection problem will occour every now and then. Unfortunately I have to use NAT in the connection between in both ends, however this worked well with Zabbix 2.

I just converted the proxy from active to passive to see if there is any difference.