# Logsstash filling up /var/log/syslog?

**URL:** <https://discuss.elastic.co/t/logsstash-filling-up-var-log-syslog/108234>\
**Category:** Logstash\
**Created:** [November 18, 2017, 2:01pm UTC](https://discuss.elastic.co/t/logsstash-filling-up-var-log-syslog/108234 "2017-11-18T14:01:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mathurin68](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@mathurin68](https://discuss.elastic.co/u/mathurin68)\
**Post date:** [November 18, 2017, 2:01pm UTC](https://discuss.elastic.co/t/logsstash-filling-up-var-log-syslog/108234/1 "2017-11-18T14:01:38Z")

</div>

syslog in /var/log filling up with logstash?

Every event coming through logstash is filling up syslog -  
ogstash[54646]: "type" =\> "wineventlog",  
Nov 18 06:25:05 elkstack logstash[54646]: "opcode" =\> "Info",  
Nov 18 06:25:05 elkstack logstash[54646]: "version" =\> 1,  
Nov 18 06:25:05 elkstack logstash[54646]: "tags" =\> [  
Nov 18 06:25:05 elkstack logstash[54646]: [0] "beats\_input\_codec\_plain\_applied"  
Nov 18 06:25:05 elkstack logstash[54646]: ],

This is what I have in conf.d -  
ack:/etc/logstash/conf.d# grep -r "syslog" .  
./10-syslog-filter.conf: if [type] == "syslog" {  
./10-syslog-filter.conf: match =\> { "message" =\> "%{SYSLOGTIMESTAMP:syslog\_timestamp} %{SYSLOGHOST:syslog\_hostname} %{DATA:syslog\_program}(?:[%{POSINT:syslog\_pid}])?: %{GREEDYDATA:syslog\_message}" }  
./10-syslog-filter.conf: syslog\_pri { }  
./10-syslog-filter.conf: match =\> ["syslog\_timestamp", "MMM d HH:mm:ss", "MMM dd HH:mm:ss"]

Maybe this is normal, not sure...

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 18, 2017, 10:13pm UTC](https://discuss.elastic.co/t/logsstash-filling-up-var-log-syslog/108234/2 "2017-11-18T22:13:18Z")

</div>

Looks like you have a `stdout` output somewhere.

---

<div class="post-metadata">

**Author:** ![mathurin68](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@mathurin68](https://discuss.elastic.co/u/mathurin68)\
**Post date:** [November 20, 2017, 8:29pm UTC](https://discuss.elastic.co/t/logsstash-filling-up-var-log-syslog/108234/3 "2017-11-20T20:29:40Z")

</div>

Thanks Mark!

---

<div class="post-metadata">

**Author:** ![Jason\_Brooks](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@Jason\_Brooks](https://discuss.elastic.co/u/Jason_Brooks)\
**Post date:** [November 30, 2017, 9:14pm UTC](https://discuss.elastic.co/t/logsstash-filling-up-var-log-syslog/108234/4 "2017-11-30T21:14:25Z")

</div>

Hello warkolm,

Does this mean that when daemonized and stdout is defined, that everything is written to syslog?

That's good to know.

--jason

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 30, 2017, 9:19pm UTC](https://discuss.elastic.co/t/logsstash-filling-up-var-log-syslog/108234/5 "2017-11-30T21:19:53Z")

</div>

Yes, because that is stdout when daemonised.

---

<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:** [December 28, 2017, 9:19pm UTC](https://discuss.elastic.co/t/logsstash-filling-up-var-log-syslog/108234/6 "2017-12-28T21:19:54Z")

</div>

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