# Logstash 6.0 breaks winlogbeat agent indexing **URL:** \ **Category:** Logstash\ **Created:** [November 21, 2017, 4:56pm UTC](https://discuss.elastic.co/t/logstash-6-0-breaks-winlogbeat-agent-indexing/108595 "2017-11-21T16:56:17Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [November 24, 2017, 7:07pm UTC](https://discuss.elastic.co/t/logstash-6-0-breaks-winlogbeat-agent-indexing/108595/2 "2017-11-24T19:07:48Z")
See the following topics: > [@Problem with multiple mapping types in 6.0. Not sure why](https://discuss.elastic.co/t/problem-with-multiple-mapping-types-in-6-0-not-sure-why/108231): > > I have previously commented on another topic with a similar issue, but as that was beats related, and fixed by updates there, and mine is not, i a, creating this topic. I am getting errors due to multiple mapping types, as per the 6.0 breaking changes, but i don't know why i have multiple mapping types. The data is delivered by a powershell script which gathers performance counter data and sends it to logstash. My logstash configuration looks like this: input { tcp { port =\> 5560 codec =\> … > [@Help please.. breaking changes?](https://discuss.elastic.co/t/help-please-breaking-changes/108010): > > Upgrading to 6.0.0 of the ELK stack Can anyone please help me why i get this entrys over and over in the Logstash log [2017-11-16T20:49:36,973][WARN][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=\>400, :action=\>["index", {:\_id=\>nil, :\_index=\>"winlogbeat-2017.11.16", :\_type=\>"wineventlog", :\_routing=\>nil}, #LogStash::Event:0x59ffd445], :response=\>{"index"=\>{"\_index"=\>"winlogbeat-2017.11.16", "\_type"=\>"wineventlog", "\_id"=\>"LcRhxl8BA5Maqd7NKABD", "status"=\>40… --- _[View the full topic](https://discuss.elastic.co/t/logstash-6-0-breaks-winlogbeat-agent-indexing/108595)._