[ZBX-1681] multiple listing sockets in state TIME_WAIT, any time block receive data from agent Created: 2010 Jan 08  Updated: 2017 May 30  Resolved: 2011 Sep 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 1.6.4
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Semenov Sergey Assignee: Unassigned
Resolution: Won't fix Votes: 1
Labels: windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 2003 server


 Description   

If restart zabbix agent on windows more time - it is stop send data to zabbix server.
If after that, stopping zabbix agent and see netstat - can see many CLOSE_WAIT or TIME_WAIT state of connections. And if try to connect to 10050 from zabbix_get - connect success, but data not received. telnet - also.
In this case help only reboot or set another port to list connections in zabbix agent config file.

 Comments   
Comment by richlv [ 2011 Aug 29 ]

does this still happen with 1.8 agent ? if agent is stopped, did you confirm that no more agent processes are there ?

Comment by Semenov Sergey [ 2011 Aug 31 ]

I try 1.8.2 agent on windows. After many restarts agent it work properly. Connection success, data received.
But netstat continue show many connections in state TIME_WAIT. Number of connections incremented after each trying telnet connections to this zabbix_agent.
Such situations is on 1.8.3 on linux:
tcp 0 0 172.21.250.3:10050 172.21.250.34:56951 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:56739 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:56828 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:56866 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:57169 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:57074 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:56995 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:57219 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:56738 TIME_WAIT -
tcp 0 0 172.21.250.3:10050 172.21.250.34:56981 TIME_WAIT -

But data received successfully. All work properly, except this many TIME_WAIT connections.

Comment by richlv [ 2011 Sep 05 ]

time_waits is a tcp/operating system feature. see https://support.zabbix.com/browse/ZBX-3948?focusedCommentId=44463&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-44463 for my feeble attempt to describe it

Generated at Mon May 12 08:04:24 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.