• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Elasticsearch Failed But Configured Correctly.

Wesker

Well-known member
#1
ElasticSearch is installed and configured on server side. Its working perfectly fine on server side.

When we connect it with XF, it occasionally throws an error:

"Elasticsearch server returned no response. Is it running? Elasticsearch indexing failed"

Above error is not permanent and search works fine for most of the time. We also get the same issue while reindexing.

NOTE: Our server is having MySQL issues and I suspect that this issue is connected to MySQL server going down..
Per devs above. Using 1.1.0. If a common error with 1.1.0, can upgrade to newer versions.
 

Wesker

Well-known member
#3
What issues?

It may be worth resolving those and ensuring the server is stable before attempting to troubleshoot any other issues.
We have slow queries those are locking up database and MySQL server is responding quite slow. We're already working to resolve those issues.
 

Mike

XenForo developer
Staff member
#4
If you're having MySQL lock ups, you're quite likely having general load/contention issues, which means that MySQL may be the underlying cause. So trying to troubleshoot/resolve that first is potentially worthwhile.

Otherwise, there are some somewhat related changes in newer XFES releases, so upgrading may help. (There was a situation in a previous release where you could get that error as a false positive, though I don't recall if it applied to the release you're running.)
 

Wesker

Well-known member
#5
If you're having MySQL lock ups, you're quite likely having general load/contention issues, which means that MySQL may be the underlying cause. So trying to troubleshoot/resolve that first is potentially worthwhile.

Otherwise, there are some somewhat related changes in newer XFES releases, so upgrading may help. (There was a situation in a previous release where you could get that error as a false positive, though I don't recall if it applied to the release you're running.)
Waiting for our teams response. I believe they'll respond saying part of those slow queries is the standard search load which is why we're trying to upgrade to the enhanced search.
 
Last edited:

Mike

XenForo developer
Staff member
#6
If you have enabled Elasticsearch in XF (it would seem so as otherwise you wouldn't get the original error), it wouldn't be using the standard search.
 

Wesker

Well-known member
#7
Per your recommendation we will fix the SQL issues first and then report back to you. We could use your help with the SQL issues the most. We're reviewing the data logs now and will have an update on that shortly. Thank you.