# Courier Fetch Errors

**URL:** <https://discuss.elastic.co/t/courier-fetch-errors/74321>\
**Category:** Kibana\
**Created:** [February 8, 2017, 6:00am UTC](https://discuss.elastic.co/t/courier-fetch-errors/74321 "2017-02-08T06:00:30Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![kopacko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kopacko/32/10733_2.png) [@kopacko](https://discuss.elastic.co/u/kopacko)\
**Post date:** [February 8, 2017, 9:36pm UTC](https://discuss.elastic.co/t/courier-fetch-errors/74321/13 "2017-02-08T21:36:43Z")

</div>

@ppisljar

New topic created for Logstash related errors that I think are tied to the Kibana errors.

> [@Failed Action](https://discuss.elastic.co/t/failed-action/74433):
>
> Last night I upgraded my Elasticsearch data nodes from 4 CPUs to 8 CPUs and now I am getting these errors from my Logstash shippers. Please help!!!!! [2017-02-08T15:31:14,344][WARN][logstash.outputs.elasticsearch] Failed action. {:status=\>500, :action=\>["index", {:\_id=\>nil, :\_index=\>"logstash-2017.02.08", :\_type=\>"logs", :\_routing=\>nil}, ####\<LOG MESSAGE REMOVED\>####, :response=\>{"index"=\>{"\_index"=\>"logstash-2017.02.08", "\_type"=\>"logs", "\_id"=\>"AVofozXYJ8M9dMOnBjdZ", "status"=\>500, …

---

_[View the full topic](https://discuss.elastic.co/t/courier-fetch-errors/74321)._