# ES stack 6.3.0 stopped working =\>Can't get text on a START\_OBJECT

**URL:** <https://discuss.elastic.co/t/es-stack-6-3-0-stopped-working-cant-get-text-on-a-start-object/137424>\
**Category:** Logstash\
**Created:** [June 26, 2018, 11:47am UTC](https://discuss.elastic.co/t/es-stack-6-3-0-stopped-working-cant-get-text-on-a-start-object/137424 "2018-06-26T11:47:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\
**Post date:** [June 26, 2018, 11:47am UTC](https://discuss.elastic.co/t/es-stack-6-3-0-stopped-working-cant-get-text-on-a-start-object/137424/1 "2018-06-26T11:47:41Z")

</div>

After upgrading ES stack from 6.2.4 =\> 6.3.0 Logstash isn't producing any data.  
In LS log I've found:

```auto
[2018-06-26T13:44:05,968][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>"SIKSKL2017-05-19T05:46:36.000Z1140994898", :_index=>"transakcije_kv", :_type=>"log_transakcije", :_routing=>nil}, #<LogStash::Event:0x40f46392>], :response=>{"index"=>{"_index"=>"transakcije_kv", "_type"=>"log_transakcije", "_id"=>"SIKSKL2017-05-19T05:46:36.000Z1140994898", "status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse [host]", "caused_by"=>{"type"=>"illegal_state_exception", "reason"=>"Can't get text on a START_OBJECT at 1:980"}}}}}

```

But host is produced by FB.  
Can anyone advice me, how to fix this?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 26, 2018, 12:31pm UTC](https://discuss.elastic.co/t/es-stack-6-3-0-stopped-working-cant-get-text-on-a-start-object/137424/2 "2018-06-26T12:31:16Z")

</div>

I answered the same question yesterday, so search for that or just google the error message in general. You're not the first person to hit this.

---

<div class="post-metadata">

**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\
**Post date:** [June 26, 2018, 1:16pm UTC](https://discuss.elastic.co/t/es-stack-6-3-0-stopped-working-cant-get-text-on-a-start-object/137424/3 "2018-06-26T13:16:40Z")

</div>

Found a similarity using Google on Stack Owerflow.  
And got it fixed.

As I can see the sintacs of FB output has changed. As I did nothing with `host` field.  
So an on the fly upgrade is not possible any more.

And yes I did a search on discuss, but I didn't found a topic with `host` field involved.  
So sorry for the duplication of topics and questions.

---

<div class="post-metadata">

**Author:** ![Mojster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mojster/32/21209_2.png) [@Mojster](https://discuss.elastic.co/u/Mojster)\
**Post date:** [June 27, 2018, 7:16am UTC](https://discuss.elastic.co/t/es-stack-6-3-0-stopped-working-cant-get-text-on-a-start-object/137424/4 "2018-06-27T07:16:30Z")

</div>

So now all of us who uses Beats, have to reindex all our indexes.  
This is a enormous tasks.

This is the description of it:

> <https://github.com/elastic/beats/pull/7051>

---

<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:** [July 25, 2018, 7:16am UTC](https://discuss.elastic.co/t/es-stack-6-3-0-stopped-working-cant-get-text-on-a-start-object/137424/5 "2018-07-25T07:16:31Z")

</div>

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