Elasticsearch server returned no response

[dutchbb]

I get these errors sometimes and one time the forum went down for a second and lost connection to ftp. These happen with member searches. Elasticsearch 5.6.0 installed.

XenForo_Exception: Elasticsearch server returned no response. Is it running? - library/XenES/Search/SourceHandler/ElasticSearch.php:1012
Gegenereerd Door: Onbekend Account, 14 minuten geleden
Stack Trace
#0 /home/bodyforum/public_html/library/XenES/Search/SourceHandler/ElasticSearch.php(680): XenES_Search_SourceHandler_ElasticSearch->_logSearchResponseError(false, true)
#1 /home/bodyforum/public_html/library/XenForo/Search/Searcher.php(136): XenES_Search_SourceHandler_ElasticSearch->executeSearchByUserId(94045, 0, '200')
#2 /home/bodyforum/public_html/library/XenForo/ControllerPublic/Search.php(369): XenForo_Search_Searcher->searchUser(94045, 0)
#3 /home/bodyforum/public_html/library/XenForo/FrontController.php(351): XenForo_ControllerPublic_Search->actionMember()
#4 /home/bodyforum/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#5 /home/bodyforum/public_html/index.php(13): XenForo_FrontController->run()
#6 {main}
Aanvraagstatus
array(3) {
  ["url"] => string(57) "https://forum.bodybuilding.nl/search/member?user_id=94045"
  ["_GET"] => array(1) {
   ["user_id"] => string(5) "94045"
  }
  ["_POST"] => array(0) {
  }
}

XenForo_Exception: Elasticsearch server returned no response. Is it running? - library/XenES/Search/SourceHandler/ElasticSearch.php:1012
Gegenereerd Door: Onbekend Account, Vandaag om 05:39
Stack Trace
#0 /home/bodyforum/public_html/library/XenES/Search/SourceHandler/ElasticSearch.php(361): XenES_Search_SourceHandler_ElasticSearch->_logSearchResponseError(false, true)
#1 /home/bodyforum/public_html/library/XenForo/Search/SourceHandler/Abstract.php(115): XenES_Search_SourceHandler_ElasticSearch->executeSearch('', true, Array, Array, false, '200')
#2 /home/bodyforum/public_html/library/XenForo/Search/Searcher.php(79): XenForo_Search_SourceHandler_Abstract->searchGeneral('', Array, 'date', '200')
#3 /home/bodyforum/public_html/library/XenForo/ControllerPublic/Search.php(362): XenForo_Search_Searcher->searchGeneral('', Array, 'date')
#4 /home/bodyforum/public_html/library/XenForo/FrontController.php(351): XenForo_ControllerPublic_Search->actionMember()
#5 /home/bodyforum/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#6 /home/bodyforum/public_html/index.php(13): XenForo_FrontController->run()
#7 {main}
Aanvraagstatus
array(3) {
["url"] => string(72) "Zoekresultaten | Bodybuilding.nl Forum"
["_GET"] => array(2) {
["content"] => string(6) "thread"
["user_id"] => string(5) "78351"
}
["_POST"] => array(0) {
}
}

 

[Slavik]

If they are only occurring once in a while, it would just suggest a temporary failure to connect to ElasticSearch, do you have to manually restart ES or do things just carry on as normal after?

 

[dutchbb]

Things just carry on as normal.

 

[Slavik]

I wouldn't worry about it then, obviously it means the search at that time didn't complete, but unless the ES logs are showing an error, it probably isn't going to be easily tracked down.

 

[dutchbb]

Ok, thanx

 

[Mike]

It could generally indicate server load issues, as all it's saying is that no response was received in the allowed time. You mentioned the forum went down once, so that's fitting too.

It could potentially also indicate that Elasticsearch needs more memory than was allocated (to prevent it from having to go to the disk as much).

 

[dutchbb]

I think it needs more memory then because serverload is mostly around 0,5 to max 1 (6 dual core processors). Memory usage is 50-70% true the day and 30-50 at night (16GB ram)

But elasticsearch uses around 17% of that memory usage. Processor usage is 0,5% against 2,5% for mysql.

 

[dutchbb]

Upgraded to php 7.1 and problem went away. I was still on 5.6

 

[dutchbb]

I happened a few times more but i have located the scource. It only happens at night, yesterday also when php 7 was automatically updated.

So this is because of updates at night.