Hi,
I'm having an issue with zabbix agent where the agent always have issue or 'down". Every time it happen, I will just restart the agent from services.msc then after few hours or a day, it goes down again.
When the zabbix server failed to read data from the agent, I tried to telnet:
From agent to server port 10051 --> OK
From server to agent port 10050 --> OK
Ping agent to server --> OK
Ping server to agent --> OK
I even tried turn off both side firewall then restart the agent, still same thing happened after few hours or day.
From zabbix monitoring, the problem reported are "get value from agent failed:ZBX_TCP_READ() failed: [104] Connection reset by peer"
Through some searching online, comes upon "tcp port exhaustion" problem, so I tried to tweak the Windows Server registryby editing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters following the recommendation at https://www.filehold.com/help/techni...ort-Exhaustion.
Still, the issue persist.
I tried to tweak the agent conf as below:
StartAgents=10
BufferSend=10
BufferSize=150
MaxLinesPerSecond=100
Timeout=20
Still, the issue persist.
Below are my environment architecture:
server1 ----------------------
server2 ---------------------- 10.16.145.0/24
server3 ----------------------
server4 ----------------------
server5 ---------------------- 10.16.144.0/24
server6 ----------------------
zabbix ----------------------
server1,2,and 3 are the servers that having the problems. server 4,5 and 6 are fine. All server running Windows Server 2003 SP2.
Zabbix Server version = 3.4.12
Zabbix Agent version = 3.4.6
Zabbix Server OS = Centos 7.5
I attached together the agent log and agent conf file from server2.
The error are regarding TCP, so I guess is something to do with network or port. But there were no issue with connectivity, I really have no idea on how to further check the problem anymore.
I really appreciate some help.
Thanks
soonhin
I'm having an issue with zabbix agent where the agent always have issue or 'down". Every time it happen, I will just restart the agent from services.msc then after few hours or a day, it goes down again.
When the zabbix server failed to read data from the agent, I tried to telnet:
From agent to server port 10051 --> OK
From server to agent port 10050 --> OK
Ping agent to server --> OK
Ping server to agent --> OK
I even tried turn off both side firewall then restart the agent, still same thing happened after few hours or day.
From zabbix monitoring, the problem reported are "get value from agent failed:ZBX_TCP_READ() failed: [104] Connection reset by peer"
Through some searching online, comes upon "tcp port exhaustion" problem, so I tried to tweak the Windows Server registryby editing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters following the recommendation at https://www.filehold.com/help/techni...ort-Exhaustion.
Still, the issue persist.
I tried to tweak the agent conf as below:
StartAgents=10
BufferSend=10
BufferSize=150
MaxLinesPerSecond=100
Timeout=20
Still, the issue persist.
Below are my environment architecture:
server1 ----------------------
server2 ---------------------- 10.16.145.0/24
server3 ----------------------
server4 ----------------------
server5 ---------------------- 10.16.144.0/24
server6 ----------------------
zabbix ----------------------
server1,2,and 3 are the servers that having the problems. server 4,5 and 6 are fine. All server running Windows Server 2003 SP2.
Zabbix Server version = 3.4.12
Zabbix Agent version = 3.4.6
Zabbix Server OS = Centos 7.5
I attached together the agent log and agent conf file from server2.
The error are regarding TCP, so I guess is something to do with network or port. But there were no issue with connectivity, I really have no idea on how to further check the problem anymore.
I really appreciate some help.
Thanks
soonhin
Comment