# Logstash errors after upgrading to filebeat-6.3.0

**URL:** <https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 14, 2018, 6:51pm UTC](https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984 "2018-06-14T18:51:00Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![nxhack](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nxhack/32/3939_2.png) [@nxhack](https://discuss.elastic.co/u/nxhack)\
**Post date:** [June 15, 2018, 1:14am UTC](https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984/4 "2018-06-15T01:14:53Z")

</div>

> [@Logstash errors on filebeat received apache logs](https://discuss.elastic.co/t/logstash-errors-on-filebeat-received-apache-logs/135808):
>
> After an upgrade from 6.2 to 6.3, I am now getting indexing errors for apache logs. [2018-06-13T16:12:18,782][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"apache-2018.06.13", :\_type=\>"apache", :\_routing=\>nil}, #LogStash::Event:0x4db324f8], :response=\>{"index"=\>{"\_index"=\>"apache-2018.06.13", "\_type"=\>"apache", "\_id"=\>"tidr-2MB8IC994mx1\_US", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reas…

Since this is a duplicate discussion, this case is due to the specification change of filebeat, so let's move on here.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-errors-after-upgrading-to-filebeat-6-3-0/135984)._