Hi!
After some hours HostMonitor 4.86 running on Windows XP Pro(SP1, Webservice 2.0, IE6.0) there exist a lot of tcp sessions, which caused that some users could not connect to the systems. The maximal amount of open sessions is reached. Take a look at netstat please:
"ehaaski01" is the machine where HM is installed(local machine) and "localhost" is the remote machine.
Can you tell me what type of sessions are built?
[System Process]:0 TCP ehaaski01:15236 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15237 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15238 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15239 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15240 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15241 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15242 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15243 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15244 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15245 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15246 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15247 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15248 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15249 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15250 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15251 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15252 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15253 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15254 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15255 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15256 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15257 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15258 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15259 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15260 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15261 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15262 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15263 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15264 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15265 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15266 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15267 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15268 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15269 localhost:1054 TIME_WAIT
[System Process]:0 TCP ehaaski01:15270 localhost:1054 TIME_WAIT
Too many connections
By default HostMonitor uses port 1054 for RCI interface (Web Service & Telnet Service).
As I see all these sessions have "TIME_WAIT" status. It means HostMonitor already closed socket but Windows have not released resources yet.
Solution?
On the one hand you may decrease HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay counter
See http://www.microsoft.com/resources/docu ... /58811.asp for details
On the other hand Microsoft says that Time_Wait sockets should not make any problem because
Regards
Alex
As I see all these sessions have "TIME_WAIT" status. It means HostMonitor already closed socket but Windows have not released resources yet.
Solution?
On the one hand you may decrease HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay counter
See http://www.microsoft.com/resources/docu ... /58811.asp for details
On the other hand Microsoft says that Time_Wait sockets should not make any problem because
But it may depend on version of you system DLLs. Probably your version of winsock works different/incorrectly. You may try to decrease TcpTimedWaitDelay time (you should create this key because Windows does not have it).Normally, TCP does not release closed connections until the value of this entry expires. However, TCP can release connections before this value expires if it is running out of TCP control blocks (TCBs).
Regards
Alex
TIME_WAIT normally not necessary
Great software, but I was noticing that on the AHM server there are more than a standard amount of TIME_WAITs sitting there incessantly. Not sure here, but my impression is that there normally shouldn't be all these TIME_WAITs around. I reduced my setting to 60 seconds, and I still have a huge list that other apps don't create.
Could it be that the code needs a change to properly close the socket?
Please see the following posting I found on the web:
http://www.ks-soft.net/cgi-bin/phpBB/pr ... key=20d09b
It almost seems as if the sockets aren't being closed even though connection is. Perhaps, you could review the code and see if there's something that could be added to clean house a little?
Could it be that the code needs a change to properly close the socket?
Please see the following posting I found on the web:
http://www.ks-soft.net/cgi-bin/phpBB/pr ... key=20d09b
It almost seems as if the sockets aren't being closed even though connection is. Perhaps, you could review the code and see if there's something that could be added to clean house a little?
Please ignore the post above
The link is to a kludge that probably shouldn't be used. After pondering the situation a little more, I realized that it's fine. Sorry for the unnecessary posting.