Page 1 of 1
Search failure
Posted: Mon Jan 12, 2015 3:11 am
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.
Re: Search failure
Posted: Mon Jan 12, 2015 3:39 am
by alex
i'll switch to backup configuration in the meantime, temporary routing issue.
Re: Search failure
Posted: Mon Jan 12, 2015 2:19 pm
by alex
Restarted it normally, the problem has been completely resolved.
Re: Search failure
Posted: Mon Jan 12, 2015 6:30 pm
by Sheffer
I'm still getting Search failure (8) here, been like that for around half an hour at least. Just FYI.
Re: Search failure
Posted: Mon Jan 12, 2015 11:12 pm
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
Re: Search failure
Posted: Tue Jan 13, 2015 3:30 am
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.
Re: Search failure
Posted: Tue Jan 13, 2015 6:59 pm
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
Re: Search failure
Posted: Tue Jan 13, 2015 7:45 pm
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.