-
Problem report
-
Resolution: Fixed
-
Minor
-
None
-
Windows 2008 R2 x64
-
Sprint 47, Dec 2018, Sprint 48, Jan 2019, Sprint 49 (Feb 2019)
-
2
We have several hundreds of windows hosts and on some of them after trying to stop/start "zabbix agent" port 10050 is not released and there are a lot of "time_wait" connections, so service coudn't be started until we reboot the machine. Via TcpView it is possible to close "time_wait" connections but not that which is in listening state and it shows <non-existent> process.
C:\Windows\system32>sc query "zabbix agent" SERVICE_NAME: zabbix agent TYPE : 10 WIN32_OWN_PROCESS STATE : 1 STOPPED WIN32_EXIT_CODE : 1067 (0x42b) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 C:\Windows\system32>netstat -ano | findstr :10050 TCP 0.0.0.0:10050 0.0.0.0:0 LISTENING 2728 TCP [::]:10050 [::]:0 LISTENING 2728 C:\Windows\system32>taskkill /f /pid 2728 ERROR: The process "2728" not found. c:\Program Files\Zabbix>zabbix_agentd.exe -V zabbix_agentd Win64 (service) (Zabbix) 3.4.6 Revision 76819 15 January 2018, compilation time: Jan 15 2018 10:43:42
Steps to reproduce:
- sc stop "zabbix agent"
- sc start "zabbix agent"
Result:
Service is in stopped state. No zabbix agent process, but port 10050 is listening.
Expected:
Service is successfully restarted
- causes
-
ZBX-15728 listener failed: WSASocket() for [[-]:10050] failed: [0x00002739] A protocol was specified in the socket function call that does not support the semantics of the socket type requested.
- Closed