# Carriage return needed to continue

**URL:** <https://discuss.elastic.co/t/carriage-return-needed-to-continue/140073>\
**Category:** Logstash\
**Created:** [July 16, 2018, 2:55am UTC](https://discuss.elastic.co/t/carriage-return-needed-to-continue/140073 "2018-07-16T02:55:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![safhw91](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@safhw91](https://discuss.elastic.co/u/safhw91)\
**Post date:** [July 16, 2018, 2:55am UTC](https://discuss.elastic.co/t/carriage-return-needed-to-continue/140073/1 "2018-07-16T02:55:38Z")

</div>

Hello,

I've been testing Logstash for a few months now, and mostly I've been able to figure out solutions to most of the problems I've been having.

But there is one thing really bugging me, not extremely critical but something I find very weird and annoying. Every now and then (e.g. every few hours or days), Logstash simply stops parsing until I press "Enter" on my Windows cmd. So I have times my Logstash is simply not parsing for days unless I go and check on it. What's going on?

---

<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:** [August 13, 2018, 2:55am UTC](https://discuss.elastic.co/t/carriage-return-needed-to-continue/140073/2 "2018-08-13T02:55:43Z")

</div>

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