# Logstash-6.0.0 displays an unhelpful NullPointerException Error in case of corrupted persistent queue

**URL:** <https://discuss.elastic.co/t/logstash-6-0-0-displays-an-unhelpful-nullpointerexception-error-in-case-of-corrupted-persistent-queue/108641>\
**Category:** Logstash\
**Created:** [November 22, 2017, 5:43am UTC](https://discuss.elastic.co/t/logstash-6-0-0-displays-an-unhelpful-nullpointerexception-error-in-case-of-corrupted-persistent-queue/108641 "2017-11-22T05:43:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Dheeraj\_Gupta](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@Dheeraj\_Gupta](https://discuss.elastic.co/u/Dheeraj_Gupta)\
**Post date:** [November 22, 2017, 6:33am UTC](https://discuss.elastic.co/t/logstash-6-0-0-displays-an-unhelpful-nullpointerexception-error-in-case-of-corrupted-persistent-queue/108641/2 "2017-11-22T06:33:54Z")

</div>

Just to report that I got hit with the same issue on another node. I looked at the persistent queue directory and saw it had three page files - `page.105`, `page.125` and `page.126`. It also had all the checkpoint files from `105` to `125` and `head. Removed all files from this directory and logstash started correctly.

[I have another open question](https://discuss.elastic.co/t/pipeline-workers-freeze-due-to-counter-being-incremented-by-a-negative-value/108644/1) about "counter incremented with a negative value" that freezes pipeline workers which I suspect is to blame for "corrupted" persistent queues.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-6-0-0-displays-an-unhelpful-nullpointerexception-error-in-case-of-corrupted-persistent-queue/108641)._