Search failed (5) Too many users

03 Oct 23: One server has been relocated, the server currently doesn't have a public IP address in the meantime. I wrote some additional tunnel code running separately to handle this. When the server is engaged the connection is 5600+ days uniform (since around 24 July 2008). In the unlikely case I disengaged the server because of some problem the retention is 1200-3800 days depending on newsgroup. If you experience any issue please let me know.

29 Nov 23: Because of encrypted and "obfuscated" flood mass posted by few nzb websites and newzbin-like communities using usenet servers as private storage for their members to download the posts - the situation with the content is pretty chaotic, since posts are disguised in such a way, that users must use the satellite ecosystem (whish is not a part of Usenet) exclusively to download them, when the website disappears - the encrypted scattered posts just eat usenet providers' disk space uselessly. If you can't find something specific please let me know what exactly you can't find for me to check how it is possible to retain the posts. Legible posts shouldn't be affected at all, let me know if you notice anything missing.

08 Aug 24: After being unchanged for many years the search service communication protocol had to be updated a few times in part to resolve a server side set feature limitation and properly handle trial searches on the relocated server. The searches themselves are not affected and it looks like the work is now complete.
Post Reply
cthulhiac
Posts: 13
Joined: Tue Jul 24, 2007 2:59 pm

Search failed (5) Too many users

Post by cthulhiac »

Is this due to a DoS attack or is there a limit to the number of users? First time I've seen it.
Top
alex
Posts: 4538
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failed (5) Too many users

Post by alex »

i noticed, checking it, it could be it ran out of memory after running for months, restarting it now.
Top
alex
Posts: 4538
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failed (5) Too many users

Post by alex »

Looks like it is running ok after reboot.

Update:

It happened second time after 4 days, while I was monitoring the server with very similar picture.

Given the timing it could be because of recently exposed Windows RDP vulnerability, which I have now patched manually.

https://portal.msrc.microsoft.com/en-US ... -2019-0708

There is some "research" exploit code available, maybe enough to make the system unstable, but without yet taking full control.

The affected server uses the standard RDP port, so only it was hit.

If it won't happen again this was the cause.
Top
Post Reply

Return to “Search service”