# Dead Letter Queue generates single byte file log

**URL:** <https://discuss.elastic.co/t/dead-letter-queue-generates-single-byte-file-log/126668>\
**Category:** Logstash\
**Created:** [April 4, 2018, 4:09am UTC](https://discuss.elastic.co/t/dead-letter-queue-generates-single-byte-file-log/126668 "2018-04-04T04:09:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pandeesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pandeesh/32/29194_2.png) [@pandeesh](https://discuss.elastic.co/u/pandeesh)\
**Post date:** [April 4, 2018, 4:09am UTC](https://discuss.elastic.co/t/dead-letter-queue-generates-single-byte-file-log/126668/1 "2018-04-04T04:09:04Z")

</div>

I am using logstash 6.2.3 and running two pipelines as given below:

> - pipeline.id: main  
> path.config: "/etc/logstash/conf.d/logstash\_es.conf"  
> dead\_letter\_queue.enable: true  
> dead\_letter\_queue.max\_bytes: 30g  
> path.dead\_letter\_queue: "/var/lib/logstash/dead\_letter\_queue"  
> #queue.type: persisted  
> - pipeline.id: dlq  
> path.config: "/etc/logstash/conf.d/logstash\_es\_dlq.conf"

I noticed sometimes single byte files are being generated in /var/lib/logstash/dead\_letter\_queue/mian directory which causes "timestamp field is misisng " in the dlq pipeline. may I know the circumstances in which the single byte file is produced by DeadLetterQueue Reader? is there any workarounds for this issue? thanks

---

<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:** [May 2, 2018, 4:09am UTC](https://discuss.elastic.co/t/dead-letter-queue-generates-single-byte-file-log/126668/2 "2018-05-02T04:09:10Z")

</div>

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