# Logstash won't show output on console

**URL:** https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941
**Category:** Logstash
**Created:** [January 14, 2020, 7:38am UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941 "2020-01-14T07:38:45Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![Anindita\_Chavan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anindita_chavan/32/60755_2.png) [@Anindita\_Chavan](https://discuss.elastic.co/u/Anindita_Chavan)
#### Post date: [January 14, 2020, 7:38am UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/1 "2020-01-14T07:38:45Z")

</div>

This is my logstash configuration file:  
\<  
input {  
file {  
path =\> "/home/trimslogs/trims.log"  
sincedb\_path =\> "NUL"  
ignore\_older =\> 0  
}  
}

filter {  
grok {  
match =\> { "message" =\> "([(?%{YEAR}-%{MONTHNUM}-%{MONTHDAY:day} %{TIME:time})])([%{LOGLEVEL:type}])([%{USERNAME:application}])([%{IPV4:ip}])([%{HOSTNAME:hostname}])([%{HOSTNAME:class}])([%{USERNAME:method}])([%{BASE10NUM:linenumber}])([null])([null])([Thread[%{GREEDYDATA:threadname}]])([(?%{YEAR}-%{MONTHNUM}-%{MONTHDAY:day} %{TIME:time})])([(?%{YEAR}-%{MONTHNUM}-%{MONTHDAY:day} %{TIME:time})])([%{GREEDYDATA:threadname1}])([%{GREEDYDATA:error\_message}])()()()()()()()()()()"}  
}

}

output {  
stdout { codec =\> rubydebug }  
}

/\>  
When i run logstash, it won't give me output on console and remains stuck on  
[INFO] 2020-01-14 02:37:55.184 [Api Webserver] agent - Successfully started Logstash API endpoint {:port=\>9600}

---

<div class="post-metadata">

### Author: ![Kishorekolla](https://avatars.discourse-cdn.com/v4/letter/k/5fc32e/32.png) [@Kishorekolla](https://discuss.elastic.co/u/Kishorekolla)
#### Post date: [January 14, 2020, 8:52am UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/2 "2020-01-14T08:52:53Z")

</div>

Since you are using linux, which your path suggests. Try changing` sincedb_path => "/dev/null"`

---

<div class="post-metadata">

### Author: ![Anindita\_Chavan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anindita_chavan/32/60755_2.png) [@Anindita\_Chavan](https://discuss.elastic.co/u/Anindita_Chavan)
#### Post date: [January 14, 2020, 9:00am UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/3 "2020-01-14T09:00:09Z")

</div>

Hello Kishore,  
Thank You for the answer. However, I'm still facing the same issue. When I ran it one time before, it worked. When I tried to run it again, it remained stuck at successfully started logstash API endpoint

---

<div class="post-metadata">

### Author: ![Kishorekolla](https://avatars.discourse-cdn.com/v4/letter/k/5fc32e/32.png) [@Kishorekolla](https://discuss.elastic.co/u/Kishorekolla)
#### Post date: [January 14, 2020, 9:18am UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/4 "2020-01-14T09:18:04Z")

</div>

Remove the `ignore_older => 0` and try.

---

<div class="post-metadata">

### Author: ![Anindita\_Chavan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anindita_chavan/32/60755_2.png) [@Anindita\_Chavan](https://discuss.elastic.co/u/Anindita_Chavan)
#### Post date: [January 14, 2020, 9:30am UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/5 "2020-01-14T09:30:04Z")

</div>

Thank You so much Kishore, it worked.

---

<div class="post-metadata">

### Author: ![Kishorekolla](https://avatars.discourse-cdn.com/v4/letter/k/5fc32e/32.png) [@Kishorekolla](https://discuss.elastic.co/u/Kishorekolla)
#### Post date: [January 14, 2020, 10:49am UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/6 "2020-01-14T10:49:12Z")

</div>

Your welcome.

---

<div class="post-metadata">

### Author: ![Anindita\_Chavan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anindita_chavan/32/60755_2.png) [@Anindita\_Chavan](https://discuss.elastic.co/u/Anindita_Chavan)
#### Post date: [January 14, 2020, 10:52am UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/7 "2020-01-14T10:52:08Z")

</div>

Also, can you also tell me if there is some way to figure out where your grok filter is going wrong?  
I ran my filter on the grok debugger here [https://grokdebug.herokuapp.com/](https://grokdebug.herokuapp.com/) which seems to be running fine. However, when I try to run the configuration file, I'm getting grokparsefailure

---

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [January 14, 2020, 2:48pm UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/8 "2020-01-14T14:48:03Z")

</div>

My advice on debugging grok patterns can be found [here](https://discuss.elastic.co/t/help-needed-in-grok/213827/2).

In filebeat setting ignore\_older to zero means to include everything. In logstash, setting ignore\_older to zero means to _exclude_ everything more than zero seconds old, which usually excludes everything.

---

<div class="post-metadata">

### Author: ![Anindita\_Chavan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anindita_chavan/32/60755_2.png) [@Anindita\_Chavan](https://discuss.elastic.co/u/Anindita_Chavan)
#### Post date: [January 14, 2020, 5:40pm UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/9 "2020-01-14T17:40:34Z")

</div>

Thankyou! The explanation really helped because I’m going to configure filebeat next. I will also checkout the grok debug link. Thanks a ton.

---

<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: [February 11, 2020, 5:40pm UTC](https://discuss.elastic.co/t/logstash-wont-show-output-on-console/214941/10 "2020-02-11T17:40:36Z")

</div>

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