# Elasticsearch logging to syslog

**URL:** <https://discuss.elastic.co/t/elasticsearch-logging-to-syslog/229398>\
**Category:** Elasticsearch\
**Created:** [April 23, 2020, 7:25am UTC](https://discuss.elastic.co/t/elasticsearch-logging-to-syslog/229398 "2020-04-23T07:25:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![coudenysj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/coudenysj/32/23108_2.png) [@coudenysj](https://discuss.elastic.co/u/coudenysj)\
**Post date:** [April 23, 2020, 7:25am UTC](https://discuss.elastic.co/t/elasticsearch-logging-to-syslog/229398/1 "2020-04-23T07:25:26Z")

</div>

Hi,

I'm trying to find out why the garbage collection system of Elasticsearch is still logging to both syslog and /var/log/elasticsearch/gc.log.

When I look at the command line options loaded in the process, I see `-Xlog:gc*,gc+age=trace,safepoint:file=/var/log/elasticsearch/gc.log:utctime,pid,tags:filecount=32,filesize=64m`, so there is nothing in there which suggest logging to syslog.

I'm also using the --quiet option in the systemd service file, so I'm not sure why it is still logging to syslog.

Does anyone has this problem too?

---

<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 21, 2020, 7:25am UTC](https://discuss.elastic.co/t/elasticsearch-logging-to-syslog/229398/2 "2020-05-21T07:25:27Z")

</div>

Closed on May 21, 2020, 7:25am UTC

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