Search failure

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 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.

21 Jun 24: The search protocol had to be upgraded again to be able to properly process the trial version searches on the tunneled server (see the first note above).



Post Reply
swent
Posts: 23
Joined: Wed Mar 28, 2007 4:49 pm

Search failure

Post by swent »

I'm getting the (10) failed to respond error today. I can't be sure how long it's been down, I've gotten it for about an hour now.
alex
Posts: 4518
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failure

Post by alex »

i'll switch to backup configuration in the meantime, temporary routing issue.
alex
Posts: 4518
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failure

Post by alex »

Restarted it normally, the problem has been completely resolved.
Sheffer
Posts: 12
Joined: Tue Jul 06, 2004 10:16 pm

Re: Search failure

Post by Sheffer »

I'm still getting Search failure (8) here, been like that for around half an hour at least. Just FYI.
n2mdk
Posts: 31
Joined: Mon Feb 28, 2011 7:29 pm

Re: Search failure

Post by n2mdk »

Search Service is still giving Search Failed (8) Server is being restarted after maintenance.
It will be available shortly.
It's been that way since 12:30 CST
alex
Posts: 4518
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failure

Post by alex »

i've switched it to backup again.

it appears power went down and two computers were affected, there was some problem with one restarting and second one took too long I'm checking error log.
tbindler
Posts: 1
Joined: Tue Jan 13, 2015 6:04 pm

Re: Search failure

Post by tbindler »

Since the last restart of the server, I have incomplet result for my search.
For example, if I search 'fansadox', I have :
- no result between the day 1 and 68.
- no result oder than 328 days
alex
Posts: 4518
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failure

Post by alex »

I restarted it already normally, so should be no such issue any more.

When it was in a backup configuration gaps may exist, but recent results are always there.

The backup configuration means one or two computers are down so I cannot have search service to load all retention, if the computers are expected to be up within short time I only adjust headers from the present to some time backwards so they will be continuous and complete, the rest of computers I keep it as it is so later I can restart search normally faster.
Post Reply