# How to handle erroring logs, that just stick around

**URL:** <https://discuss.elastic.co/t/how-to-handle-erroring-logs-that-just-stick-around/108307>\
**Category:** Logstash\
**Created:** [November 20, 2017, 2:44am UTC](https://discuss.elastic.co/t/how-to-handle-erroring-logs-that-just-stick-around/108307 "2017-11-20T02:44:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cybergoof](https://avatars.discourse-cdn.com/v4/letter/c/e274bd/32.png) [@cybergoof](https://discuss.elastic.co/u/cybergoof)\
**Post date:** [November 20, 2017, 2:44am UTC](https://discuss.elastic.co/t/how-to-handle-erroring-logs-that-just-stick-around/108307/1 "2017-11-20T02:44:06Z")

</div>

We have been running Logstash in production for a while. When I restart Logstash, it seems that logstash is attempting to resend Logs that have errors in them "Could not index event to ElasticSearch", caused by problems "failed to parse [xxx]".

These are older logs, going back to months.

Is logstash attempting to reparse these erroring logs? Are they attempting to just resend them? Is there anything I can do to either fix the parsing, or just clear them out of the pipeline?

---

<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:** [December 18, 2017, 2:44am UTC](https://discuss.elastic.co/t/how-to-handle-erroring-logs-that-just-stick-around/108307/2 "2017-12-18T02:44:41Z")

</div>

Closed on December 18, 2017, 2:44am UTC

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