Search failed (7) Error communicating with the server

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
Hamish
Posts: 16
Joined: Thu May 29, 2003 3:52 pm

Search failed (7) Error communicating with the server

Post by Hamish »

I am getting this. I have had it before but recently it has happened more often.

Is this something to do with the search servers? What does the number in brackets mean?

The message wording leads me to think that the problem is at my end. So I've reset the search configuration, turned off my firewall and virus checker but I still get it.

If this is a server problem then could you replace the message with something like "Search server(s) not responding" so it lets the user know it isn't their own configuration.

Cheers
alex
Posts: 4518
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failed (7) Error communicating with the server

Post by alex »

do you see other numbers or it is always (7), if not what other numbers it shows?

i could check then if there is a correlation.
Hamish
Posts: 16
Joined: Thu May 29, 2003 3:52 pm

Re: Search failed (7) Error communicating with the server

Post by Hamish »

I've just done some searchers in succession. The numbers were: 9, 8, 5, 9, 5, 8, 6, 9, 6, 7

Are these the numbers of the search servers?
alex
Posts: 4518
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failed (7) Error communicating with the server

Post by alex »

It is one location but more than one computer, unlikely to be a search service computer issue. Try to reboot the router, check if there is any change. I've reset the search count to see if there is any significant difference between the locations.
Hamish
Posts: 16
Joined: Thu May 29, 2003 3:52 pm

Re: Search failed (7) Error communicating with the server

Post by Hamish »

I've rebooted the router.

I get the same problem. Server numbers were: 9,9,6,9,9,5
alex
Posts: 4518
Joined: Thu Feb 27, 2003 5:57 pm

Re: Search failed (7) Error communicating with the server

Post by alex »

I've checked, I reset counter 152 hours ago. The difference is 42, it might be you are the only one who is affected.

I'll send you pm how to ping, maybe you'll see occational timeouts.

Update: The problem was edit menu->properties->tasks, read xpat timeout which is employed by UE for search service as well was changed by the user from the default to only few seconds, so it was just timeout because of the too low setting.
Post Reply