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.
15 Mar 25: It looks like the search service is currently down as there are no pings. The other server is no more on starlink, but the search requests are still routed and the access to it is through the first server, since it is safer, but the direct access is no problem if this will be a repeated issue. The connection will be restored or server restarted as soon as possible.
16 Mar 25: One server is currently still down, the other server was reconfigured and already connected directly, so the search service is running with minimum possible retention gaps.
We have scheduled power outage and in the same time system disk failed (second seagate and second time it is not even the database drive) when I tried to switch to backup configuration to provide the service during the power outage.
So we need to wait until the power outage will be over (at most few hours), I've already reconfigured the server affected by the power outage to run in the backup configuration on that computer when power is back.
i've managed to isolate the hard drive (running chkdisk and not using the drive for paging file) and utilize the computer as is, so all is now running as usual in the 210 day retention mode.
someone reported certain results weren't returned, when i checked it more closely, apparently when reconfiguring the server to address the failed system disk i accidentally clicked "index subjects" check box area to bring a server instance to the focus (the control area is too wide extending beyond the actual text, i'll make it narrower) thus unknowingly unchecking it so it didn't index subjects after restart.
i've restarted the server now with indexing subjects check box checked so all is ok now.
the server segment gathered headers as normal (just indexing is only an option e.g. to run the server without actual indexing for backup purposes only with less RAM consumption or higher retention), so all what was needed to recheck the check box and restart the server.