Search failed

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 (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 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
Marten Fokkens
Posts: 12
Joined: Sat Jan 07, 2006 8:40 pm
Location: Wedde, The Netherlands

Search failed

Post by Marten Fokkens »

Are there any search problems at the moment?

gr. Marten
Ustinov
Posts: 20
Joined: Tue Aug 12, 2003 6:41 pm

Post by Ustinov »

Probably. I have problems as well.
error 10061..machine actively refused it.
Marten Fokkens
Posts: 12
Joined: Sat Jan 07, 2006 8:40 pm
Location: Wedde, The Netherlands

Post by Marten Fokkens »

I have the same number 10061.
We will wait for Alex................
alex
Posts: 4515
Joined: Thu Feb 27, 2003 5:57 pm

Post by alex »

there was expected but sudden (not scheduled well in advance) electrical work to replace part of the outside line with noone around (the work in march failed to fix voltage drop when inductive load like a motor or compressor kicks in). UPS succumbed shortly before the work had been finished. here (different time zone) it was night time, because of work overload i need strict sleeping hours discipline.

after power was back one computer's server didn't start properly again, but this time i found the reason, on that computer windows autologon wasn't set in the registry, in windows the startup menu (from where the server is launched) is engaged only after logon. all fixed now.

it is 3+ year old windows install (the very fist indexing computer), just power/hardware were stable so far and we didn't experience spontaneous reboot.
Post Reply