Search service - Connection unexpectedly closed by the serve

03 Oct 23: One server was relocated, the server currently doesn't have a public IP address since in the meantime it is running on starlink. I wrote some additional tunnel code running separately to handle this. When the server is engaged the connection is 5600+ days uniform. 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 posts flood mass posted by a few nzb indexing websites using usenet servers as private storage for their members to download the posts - the situation with the content is pretty chaotic since their purpose is to post in such a way, so users must use their website exclusively, when the website disappears - the encrypted posts just eat usenet providers' hard disk space uselessly. If you can't find something specific please let me know at alexbirj at gmail dot com what exactly you can't find for me to check how it is possible to retain the posts. Non-obfuscated posts shouldn't be affected at all, let me know if you notice anything missing.

29 Nov 23: The search protocol had to be upgraded to extend 3 byte (16M+) limit on the server side for number of sets per instance, so at least the version 5.8.3 is needed to access it, otherwise should be no any difference.
Post Reply
thekays
Posts: 3
Joined: Mon Sep 05, 2016 7:39 pm

Search service - Connection unexpectedly closed by the serve

Post by thekays »

The search service started returning the error "Connection unexpectedly closed by the Server" starting about 5 minutes ago. This happens when doing a search, or when I attempt to import the results from an earlier search. It was working fine until about 5 minutes ago. Restarting the program yields the same error when it comes back up.
alex
Posts: 4509
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search service - Connection unexpectedly closed by the s

Post by alex »

It works now, why periods of inactivity are so long is not clear yet, it should be several seconds, but I also saw it longer on monitor couple of times, maybe around 5-7 minutes, it comes back by itself. From what I observed such outages are infrequent.

One server is currently running on starlink, need to wait until the direct ethernet connection is installed between the starlink router and the network router in one to two weeks to exclude a router which works as wireless repeater as the cause.

Update: the direct ethernet cable has been installed, as to this particular issue it appears to be resolved.
Post Reply