# Pipeline aborted due to EOF in aggregate maps file

**URL:** <https://discuss.elastic.co/t/pipeline-aborted-due-to-eof-in-aggregate-maps-file/254783>\
**Category:** Logstash\
**Created:** [November 9, 2020, 3:42pm UTC](https://discuss.elastic.co/t/pipeline-aborted-due-to-eof-in-aggregate-maps-file/254783 "2020-11-09T15:42:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lens](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@lens](https://discuss.elastic.co/u/lens)\
**Post date:** [November 9, 2020, 3:42pm UTC](https://discuss.elastic.co/t/pipeline-aborted-due-to-eof-in-aggregate-maps-file/254783/1 "2020-11-09T15:42:49Z")

</div>

We have had several cases recently of logstash not being able to restart all of its configured pipelines. We are using the aggregation filter and it should write out any aggregation maps that are in-progress when logstash is stopped. It does this, but sometimes 1 or 2 of them appear to be incomplete. When logstash is started up, those pipelines are aborted with this error:

```auto
Pipeline aborted due to error {:pipeline_id=>"pipeline2", :exception=>#<EOFError: End of file reached>

```

The only solution seems to be deleting the bad files, and losing all their stored events.

Anyone know why this happens or have any ideas on what to try?  
We are on logstash 7.6.2.

---

<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 7, 2020, 3:42pm UTC](https://discuss.elastic.co/t/pipeline-aborted-due-to-eof-in-aggregate-maps-file/254783/2 "2020-12-07T15:42:51Z")

</div>

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