# Logstash not processing new beat

**URL:** <https://discuss.elastic.co/t/logstash-not-processing-new-beat/166566>\
**Category:** Logstash\
**Created:** [January 31, 2019, 1:28pm UTC](https://discuss.elastic.co/t/logstash-not-processing-new-beat/166566 "2019-01-31T13:28:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin\_Ross](https://avatars.discourse-cdn.com/v4/letter/k/9de053/32.png) [@Kevin\_Ross](https://discuss.elastic.co/u/Kevin_Ross)\
**Post date:** [January 31, 2019, 1:28pm UTC](https://discuss.elastic.co/t/logstash-not-processing-new-beat/166566/1 "2019-01-31T13:28:12Z")

</div>

Hi,

I am upgrading my logging so I have reinstalled server with new ELK stack and rebuilt a system to send logs into (bro & suricata).

Now in Kibana I can see firewall syslog logs from before and a sensor (to be rebuilt) I have running filebeat 5.X something and its logs appear but the new sensor with recent 6.X while traffic is going to the box the logs don't appear. I do have this in logstash logs but not sure if it is related and everytime I try the mutate fix I found around this it breaks all my logging.

[2019-01-31T13:24:58,858][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"logstash-2019.01.31", :\_type=\>"doc", :routing=\>nil}, #LogStash::Event:0x415a661a], :response=\>{"index"=\>{"\_index"=\>"logstash-2019.01.31", "\_type"=\>"doc", "\_id"=\>"5LwVpGgBZZmAyljHf3pn", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse field [host] of type [text]", "caused\_by"=\>{"type"=\>"illegal\_state\_exception", "reason"=\>"Can't get text on a START\_OBJECT at 1:60"}}}}}

I am wondering how I would go about tracing down this issue as I have checked all the common things (error messages, network, connectivity etc). so I think now I am in the logstash to elasticsearch part of it but only that error is occuring but it could be off another system like the firewalls.

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [January 31, 2019, 2:19pm UTC](https://discuss.elastic.co/t/logstash-not-processing-new-beat/166566/2 "2019-01-31T14:19:10Z")

</div>

Is there an error in the elasticsearch logs at that time?

---

<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:** [February 28, 2019, 2:19pm UTC](https://discuss.elastic.co/t/logstash-not-processing-new-beat/166566/3 "2019-02-28T14:19:13Z")

</div>

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