# Logstash-2.0 issue with stdout | help required **URL:** \ **Category:** Logstash\ **Created:** [November 16, 2015, 11:19pm UTC](https://discuss.elastic.co/t/logstash-2-0-issue-with-stdout-help-required/34743 "2015-11-16T23:19:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pramodmax](https://avatars.discourse-cdn.com/v4/letter/p/7c8e57/32.png) [@pramodmax](https://discuss.elastic.co/u/pramodmax)\ **Post date:** [November 16, 2015, 11:19pm UTC](https://discuss.elastic.co/t/logstash-2-0-issue-with-stdout-help-required/34743/1 "2015-11-16T23:19:39Z")
Hi Team, I have an issue, in which the logstash is writing all the details into the "logstash.stdout" file. The file grows in time and consumes all the disk space[100GB], since we have 16 servers pushing all the log details. Additionally, since logstash writes all the log details in a stdout file, it consumes a huge amount of CPU resource. Easily goes 140% [We have 2 core] Logstash version: logstash-2.0.0-1.noarch Operating System: RHEL 6 I have tried removing the stdout block from the output section and still I can see the logs. What I saw was that the agent.rb file appends the stdout block if the block does not exist!! I may be wrong in this. but some insight on this is really appreciated. My main purpose is to stop the logstash doing any logs into the file, [Even if it has error, I do not need them] Since it is consuming a lot of CPU resources. Please suggest. Kind regards, Pramod ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [November 17, 2015, 7:04am UTC](https://discuss.elastic.co/t/logstash-2-0-issue-with-stdout-help-required/34743/2 "2015-11-17T07:04:40Z")
> I have tried removing the stdout block from the output section and still I can see the logs. I'm sure you still have a stdout output somewhere. If you're running Logstash out of /etc/logstash/conf.d, make sure there's nothing there (`grep stdout /etc/logstash/conf.d/*`). Logstash will parse _all_ files in that directory. > What I saw was that the agent.rb file appends the stdout block if the block does not exist!! Only if you're using `-e` with a string that contains no outputs. ---
**Author:** ![pramodmax](https://avatars.discourse-cdn.com/v4/letter/p/7c8e57/32.png) [@pramodmax](https://discuss.elastic.co/u/pramodmax)\ **Post date:** [November 17, 2015, 9:40pm UTC](https://discuss.elastic.co/t/logstash-2-0-issue-with-stdout-help-required/34743/3 "2015-11-17T21:40:04Z")
Hi Magnus, Thank you for the details. But unfortunately, that did not help. It looks like it was caching the config somewhere aswell. It was weird, but what can I say. So I uninstalled the logstash and reinstalled it again. It has stopped logging all the logs in stdout log file. Then, the Kibana was getting stuck in the discovery screen. I refreshed the cache of the Elasticsearch, removed all the index, and even reinstalled the Elastic search. Nothing was helping in this case. one last thing I saw was that the permission on the Kibana was not assigned to the kibana user and group. I changed kibana folder permission as [chown -R kibana:kibana kibana\_folder] and then restarted the Kibana. It started working. Hope this will help someone. Kind regards, Pramod ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [November 18, 2015, 6:59am UTC](https://discuss.elastic.co/t/logstash-2-0-issue-with-stdout-help-required/34743/4 "2015-11-18T06:59:48Z")
Logstash doesn't cache configuration anywhere. Next time you get a problem like this, start Logstash with `--debug` to get additional details about the configuration and from where it's loaded. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 5:22am UTC](https://discuss.elastic.co/t/logstash-2-0-issue-with-stdout-help-required/34743/5 "2017-07-06T05:22:24Z")