[Dxspider-support] DXSpider stop responding to connections with 100% CPU

[Mike McCarthy, W1NR]

CLOSE_WAIT can be caused by a connection timeout because the program has 
stopped talking to the socket. The most likely problem is a corrupt file 
or database. Only a debug session trying to find the specific area of 
the code that is going into a loop and blocking all other activity will 
reveal where the problem is. You might try going back several versions 
of the users file or deleting it altogether.

On 2/20/2024 1:02 PM, Normando IZ6FXS via Dxspider-support wrote:
> I’ll try even though the two addresses you saw are the cluster’s ones. On the right column I’ve masked the IPs trying to connect to the cluster all hung in CLOSE_WAIT. And BTW happened 3 times today.
> It seems an uncommon thing to happen, nothing in the archives too… So since I can’t offer such a bad service I’ll shut the node once and for all eventually.
> 
> Thanks,
> Norm
> 

-- 
73 de Mike, W1NR

THAT was the equation. EXISTENCE!... SURVIVAL... must cancel out... 
programming!

- Ruk -