Elasticsearch error: Unknown key for a START_ARRAY in [docvalue_fields].

[marioman]

hi,

i installed latest ES5
search index finished without issue but search still not work
i get this error on xenforo Server Error Log

XenForo_Exception: Elasticsearch error: {"root_cause":[{"type":"parsing_exception","reason":"Unknown key for a START_ARRAY in [docvalue_fields].","line":1,"col":173}],"type":"parsing_exception","reason":"Unknown key for a START_ARRAY in [docvalue_fields].","line":1,"col":173} -

 

[Mike]

Can you include the rest of the error backtrace/request state?

Also, do you have any add-ons that add indexable content or add-ons that interact with search?

 

[marioman]

XenForo_Exception: Elasticsearch error: {"root_cause":[{"type":"parsing_exception","reason":"Unknown key for a START_ARRAY in [docvalue_fields].","line":1,"col":173}],"type":"parsing_exception","reason":"Unknown key for a START_ARRAY in [docvalue_fields].","line":1,"col":173} - library/XenES/Search/SourceHandler/ElasticSearch.php:1006
Generated By: user, 16 minutes ago
Stack Trace

#0 /home/user/public_html/forum/library/XenES/Search/SourceHandler/ElasticSearch.php(361): XenES_Search_SourceHandler_ElasticSearch->_logSearchResponseError(Object(stdClass), true)
#1 /home/user/public_html/forum/library/XenForo/Search/SourceHandler/Abstract.php(115): XenES_Search_SourceHandler_ElasticSearch->executeSearch('books', false, Array, Array, false, '200')
#2 /home/user/public_html/forum/library/XenForo/Search/Searcher.php(79): XenForo_Search_SourceHandler_Abstract->searchGeneral('books', Array, 'relevance', '200')
#3 /home/user/public_html/forum/library/XenForo/ControllerPublic/Search.php(255): XenForo_Search_Searcher->searchGeneral('books', Array, 'relevance')
#4 /home/user/public_html/forum/library/XenES/Proxy/ControllerSearch.php(34): XenForo_ControllerPublic_Search->actionSearch()
#5 /home/user/public_html/forum/library/XenForo/FrontController.php(351): XenES_Proxy_ControllerSearch->actionSearch()
#6 /home/user/public_html/forum/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#7 /home/user/public_html/forum/index.php(13): XenForo_FrontController->run()
#8 {main}

Request State

array(3) {
  ["url"] => string(37) "http://forum.zyzoom.net/search/search"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(10) {
    ["keywords"] => string(5) "books"
    ["users"] => string(0) ""
    ["date"] => string(0) ""
    ["nodes"] => array(1) {
      [0] => string(0) ""
    }
    ["child_nodes"] => string(1) "1"
    ["order"] => string(9) "relevance"
    ["_xfToken"] => string(8) "********"
    ["_xfRequestUri"] => string(8) "/search/"
    ["_xfNoRedirect"] => string(1) "1"
    ["_xfResponseType"] => string(4) "json"
  }
}

 

[marioman]

 

[marioman]

i stopped all Add-ons except XenForo Enhanced Search and still have same issue

 

[marioman]

i tried to upgrade to 5.1.2
i get now
Elasticsearch does not appear to be running but is enabled as the search system.

 

[marioman]

i did exactly what is here
https://www.axivo.com/resources/repository-setup.1/
https://www.axivo.com/resources/elasticsearch-setup.11/

except this command line

yum -q keys | egrep 'axivo|Repo'

i get error ("No such command: keys")
after all i create (service elasticsearch start) and get green ok
but still have this message (Elasticsearch does not appear to be running but is enabled as the search system.)
when i check status i found it dead
help me please

 

[Mike]

Running an alpha version of 5.0 is quite likely to be the issue and we don't tend to support alpha/beta versions of underlying software.

Unfortunately, we can't really provide too much support for Elasticsearch itself not starting. You can likely find more details of the cause in the Elasticsearch log files though.

 

[Xon]

@marioman you are much better off using the official repo and not what is basically an unmaintained 3rd party.

Likely you'll need to rebuild your elasticsearch.yml file, and replace the ES_MAX_HEAP setting with jvm.options

The official releases have actual errors reporting what you need to change, where as the alpha builds give you really garbled error messages.