Connection resset by peer - Zabbix proxy

[monicat590]

Hi everybody.
I have a problem related with the error “connection resset by peer”.
I have a zabbix server, a zabbix-proxy and the clients.
The scenario is as the image shows.
The sever is allocated in a different network as the proxy and the clients.


Zabbix server IP: 10.249.108.3
Zabbix proxy IP: 44.168.216.206

The configuration in the Zabbix proxy agentd.conf is this:
PidFile=/var/run/zabbix/zabbix_agentd.pid
LogFile=/var/log/zabbix/zabbix_agentd.log
LogFileSize=0
SourceIP=44.168.216.206
Server=10.249.108.3
ServerActive=10.249.108.3
Hostname=malnzabproxy01
Timeout=30
Include=/etc/zabbix/zabbix_agentd.d/*.conf

The configuration of zabbix proxy.conf is this:
Server=10.249.108.3
Hostname=malnzabproxy01
SourceIP=44.168.216.206
LogFile=/var/log/zabbix/zabbix_proxy.log
LogFileSize=0
PidFile=/var/run/zabbix/zabbix_proxy.pid
SocketDir=/var/run/zabbix
DBName=zabbix_proxy
DBUser=zabbix
DBPassword=xxxxxxxxx
ProxyOfflineBuffer=4
HeartbeatFrequency=60
ConfigFrequency=600
StartPollers=50
StartPollersUnreachable=5
StartTrappers=15
StartPingers=5
StartDiscoverers=5
StartVMwareCollectors=10
VMwareCacheSize=128M
VMwareTimeout=30
SNMPTrapperFile=/var/log/snmptrap/snmptrap.log
HousekeepingFrequency=6
CacheSize=512M
HistoryCacheSize=128M
HistoryIndexCacheSize=128M
Timeout=30
ExternalScripts=/usr/lib/zabbix/externalscripts
LogSlowQueries=3000
StatsAllowedIP=44.168.216.206,10.249.108.3

The logs showthis:
Zabbix_proxy.log:
28449:20230120:094643.685 cannot send proxy data to server at "10.249.108.3": ZBX_TCP_READ() failed: [104] Connection reset by peer
28449:20230120:094644.735 cannot send proxy data to server at "10.249.108.3": ZBX_TCP_READ() failed: [104] Connection reset by peer
28434:20230120:094657.055 cannot send list of active checks to "44.168.216.180": host [pmasrv0-allianz] not found
28448:20230120:094659.068 cannot send heartbeat message to server at "10.249.108.3": ZBX_TCP_READ() failed: [104] Connection reset by peer
28448:20230120:094759.124 cannot send heartbeat message to server at "10.249.108.3": ZBX_TCP_READ() failed: [104] Connection reset by peer
28430:20230120:094857.081 cannot send list of active checks to "44.168.216.180": host [pmasrv0-allianz] not found
28448:20230120:094859.180 cannot send heartbeat message to server at "10.249.108.3": ZBX_TCP_READ() failed: [104] Connection reset by peer
28448:20230120:094959.237 cannot send heartbeat message to server at "10.249.108.3": ZBX_TCP_READ() failed: [104] Connection reset by peer
28430:20230120:095057.106 cannot send list of active checks to "44.168.216.180": host [pmasrv0-allianz] not found
28448:20230120:095059.292 cannot send heartbeat message to server at "10.249.108.3": ZBX_TCP_READ() failed: [104] Connection reset by peer
28448:20230120:095159.355 cannot send heartbeat message to server at "10.249.108.3": ZBX_TCP_READ() failed: [104] Connection reset by peer

Zabbix-agent.log:
28726:20230118:132642.369 using configuration file: /etc/zabbix/zabbix_agentd.conf
28726:20230118:132642.369 agent #0 started [main process]
28727:20230118:132642.370 agent Home started [collector]
28728:20230118:132642.371 agent Forum started[listener #1]
28729:20230118:132642.372 agent #3 started[listener #2]
28731:20230118:132642.374 agent #5 started [active checks #1]
28730:20230118:132642.374 agent #4 started[listener #3]
28731:20230118:132642.426 active check configuration update from [10.249.108.3:10051] started to fail (ZBX_TCP_READ() failed: [104] Connection reset by peer)

The configuration of the Zabbix proxy network is this:




When I execute Zabbix_get command on zabbix server, it returns the correct value.


On the web console it shows me nothing




The first problem is that the proxy-server doesn't have eny information on the webconsole (as anoather server)
And the secod proble is that it doesn't work as a proxy server.


Any ideas about it?

[Markku]

Your server IP address 10.x.x.x is not routable over public networks, so some device reset the connection. What kind of network do you have between the server and proxy?

If you don't have a public IP address on the server side that you could use for inbound connectivity to reach the server from outside, you need to set your proxy to passive mode (both in the proxy configuration file and in the frontend configuration for the proxy).

Markku

[monicat590]

Good morning Markku,

Thanks for your update.
The IP Zabbix Server has an IP public: 10.249.108.2
The IP Zabbix Proxy is a private IP 44.168.216.206, that has the communication with the zabbix - server.
The IP 10.249.108.2 (Zabbix Server) is being used for the communication to others zabbix-proxy and it works properly.

Regards,

[Markku]

Please contact your local network admin for assistance. 10.x.x.x is still not routable over public networks.

Markku

[monicat590]

But I' do't understand where is the problem. I mean, if I execute the zabbix_get command on the zabbix server it returns me data. The zabbix_get command is asking information to zabbix-proxy server.

It's asking to zabbix proxy the system.uptime. So the communication is OK, isn't it?

Apart from that, I've realized that all item monitoring with the type external check, simple check or zabbix internal, work ok.

What it doesn't work are the items monitorized with the type zabbix agent active.

I don't understand in what part of the communication it doesn't work

[Markku]

Can you answer this question:

What kind of network do you have between the server and proxy?

Markku

[monicat590]

The IP of the zabbix server is a private IP NAT. Is this escenario not possible to obtain the information properrly?

[Markku]

It was already said above: some device reset the connection.

If you don't know how your network is built and which component can do that, you need to ask someone that knows.

Markku

[monicat590]

Hi Markku,
I have finally managed to establish communication between the server and Zabbix Proxy.
After insisting to the network administrator that the problem is that at some point communications are being blocked, they checked the FW rules again and enabled the ports correctly,

Thanks a lot for your support and for your patience

Regards,