Bug Sinusbot causes hundreds of close_wait connections

[m8rm]

Hi! I'm using the newest Sinusbot version with TS 3.0.18.2 on Linux.

Like mentioned in the title there're hundreds of such close_wait connections after awhile. They reset upon restarting the bot or until the bot crashes (it's going to happen eventually after a certain amount of close_wait). I don't have the log anymore, sorry. I also found this post mentioning that the IP is the server to check if there's an update.
IIRC, it started when I updated to the latest version.

~$ netstat -ton | grep CLOSE_WAIT
tcp       32      0 server_ip:39839        104.18.41.220:443       CLOSE_WAIT  off (0.00/0/0)
tcp       32      0 server_ip:34121        104.18.40.220:443       CLOSE_WAIT  off (0.00/0/0)
etc

 

[irgendwr]

yup, can confirm the issue.
flyth is looking into it

 

[m8rm]

All right, good to know you're aware of the issue. Thank you!

 

[martindines]

Hello all!

I've had an instance of Sinusbot running for ~30 days without issue. Today the instance went offline with following reason logged: Could not prepare listeners: too many open files

Running `lsof -u sinusbot` shows many (literally hundreds?!) of listeners to 104.18.41.220 and 104.18.40.220. I found another user post on the forum, related to the previously mentioned IPs, which points towards the autoupdater https://forum.sinusbot.com/threads/sinusbot-rootkit.3441/

Restarting the sinusbot service resolves the issue, but I'm wondering how this occurred, and how to prevent this going forward?

Please find attached output of `lsof -u sinusbot`

Cheers