# XenForo Search ES6.0 index doesn't work

**URL:** <https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985>\
**Category:** Elasticsearch\
**Created:** [November 24, 2017, 7:48am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985 "2017-11-24T07:48:35Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![pavuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pavuk/32/28914_2.png) [@pavuk](https://discuss.elastic.co/u/pavuk)\
**Post date:** [November 24, 2017, 7:48am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985/1 "2017-11-24T07:48:35Z")

</div>

Hi community!  
Previously I had Xenforo Elasticsearch with ElasticSearch 5.x and everything worked perfectly.  
Ten I have updated to Elasticsearch and Kibana to 6.0, installed X-pack, updated Xenforo Elasticsearch plugin to latest 1.1.7 version, removed xf index, recreated, re-indexed. Search works now, but the problem is that no new messages fall into the index and, accordingly, are not searchable. When I see /\_cat/indices?v' I always see the same value of docs.count for this index. I have another indexes there for nginx logs, and they works fine!  
Moreover, I have absolutely the same configuration on staging server and all works perfect there!  
ES gurus, please guide me how I can debug and fix this issue?  
Thanks!

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 24, 2017, 8:02am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985/2 "2017-11-24T08:02:40Z")

</div>

I think you should ask on Xenforo forum to see if the plugin has been updated for elasticsearch 6.

---

<div class="post-metadata">

**Author:** ![pavuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pavuk/32/28914_2.png) [@pavuk](https://discuss.elastic.co/u/pavuk)\
**Post date:** [November 24, 2017, 8:22am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985/3 "2017-11-24T08:22:41Z")

</div>

Yes, plugin was updated for ES6.0 and this plugin works fine on my staging XenForo server.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 24, 2017, 8:40am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985/4 "2017-11-24T08:40:20Z")

</div>

Did you use x-pack previously as well?  
What are your elasticsearch logs?

---

<div class="post-metadata">

**Author:** ![pavuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pavuk/32/28914_2.png) [@pavuk](https://discuss.elastic.co/u/pavuk)\
**Post date:** [November 24, 2017, 8:53am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985/5 "2017-11-24T08:53:47Z")

</div>

Yes, I used x-pack.  
I have noticed in Kibana on production and staging servers that there is different structure of index - different number of fields. Strange... I have tried to get mapping of working index and create new index with this mapping on problem server but it doesn't work. I see errors like:

```
{
  "error": {
    "root_cause": [
      {
        "type": "mapper_parsing_exception",
        "reason": "Failed to parse mapping [post]: Enabling [_all] is disabled in 6.0. As a replacement, you can use [copy_to] on mapping fields to create your own catch all field."
      }
    ],
    "type": "mapper_parsing_exception",
    "reason": "Failed to parse mapping [post]: Enabling [_all] is disabled in 6.0. As a replacement, you can use [copy_to] on mapping fields to create your own catch all field.",
    "caused_by": {
      "type": "illegal_argument_exception",
      "reason": "Enabling [_all] is disabled in 6.0. As a replacement, you can use [copy_to] on mapping fields to create your own catch all field."
    }
  },
  "status": 400
}
```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 24, 2017, 9:19am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985/6 "2017-11-24T09:19:36Z")

</div>

May be there is an index template?

I'd ask the XenForo team though.

---

<div class="post-metadata">

**Author:** ![pavuk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pavuk/32/28914_2.png) [@pavuk](https://discuss.elastic.co/u/pavuk)\
**Post date:** [November 24, 2017, 10:18am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985/7 "2017-11-24T10:18:33Z")

</div>

Thank you! It was really bug in XenForo plugin - [https://xenforo.com/community/threads/content-is-not-automatically-indexed-properly-in-xfes-single-type-mode.136974/](https://xenforo.com/community/threads/content-is-not-automatically-indexed-properly-in-xfes-single-type-mode.136974/)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 22, 2017, 10:19am UTC](https://discuss.elastic.co/t/xenforo-search-es6-0-index-doesnt-work/108985/8 "2017-12-22T10:19:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.