# Removing Logstash logs from syslog

**URL:** <https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466>\
**Category:** Logstash\
**Created:** [October 7, 2019, 1:29am UTC](https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466 "2019-10-07T01:29:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sud0](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sud0](https://discuss.elastic.co/u/sud0)\
**Post date:** [October 7, 2019, 1:29am UTC](https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466/1 "2019-10-07T01:29:42Z")

</div>

Hi.

My logstash is sending logs to `/var/log/syslog`, which is causing the disk to fill up pretty quick.  
How can I disable it?

My `logstash.yml`:

```
log.level: info
path.logs: /var/log/logstash

```

syslog:

```
root@elk:/etc/logstash# tail -n 10 /var/log/syslog
Oct 7 14:28:39 elk logstash[7097]: "environment" => "production",
Oct 7 14:28:39 elk logstash[7097]: "class" => "TransactionDocumentPersisterImpl.message",
Oct 7 14:28:39 elk logstash[7097]: "message" => "Transaction coo2 b2f51909 Message cooLocalNewOwnerDetails 1897334591 | timestamp: 2019-10-07T14:28:38.082+13:00",
Oct 7 14:28:39 elk logstash[7097]: "host" => "appserver.datacentre.example.co.nz",
Oct 7 14:28:39 elk logstash[7097]: "@version" => "1",
Oct 7 14:28:39 elk logstash[7097]: "log-level" => "INFO",
Oct 7 14:28:39 elk logstash[7097]: "@timestamp" => 2019-10-07T01:28:38.083Z,
Oct 7 14:28:39 elk logstash[7097]: "path" => "/mnt/example/app/industry/industry.log",
Oct 7 14:28:39 elk logstash[7097]: "type" => "web_industry_log"
Oct 7 14:28:39 elk logstash[7097]: }
```

---

<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:** [October 7, 2019, 1:13pm UTC](https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466/2 "2019-10-07T13:13:01Z")

</div>

I would guess that you are running logstash as a service and whatever service manager you are using is cc'ing stdout to /var/log/syslog. You can reconfigure that in the service manager.

---

<div class="post-metadata">

**Author:** ![sud0](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sud0](https://discuss.elastic.co/u/sud0)\
**Post date:** [October 8, 2019, 10:05pm UTC](https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466/3 "2019-10-08T22:05:04Z")

</div>

Yes.. I thought that too.. but it is not the case.

Locate logstash.service:

```
root@elk:~# locate logstash.service
/etc/systemd/system/logstash.service
/etc/systemd/system/multi-user.target.wants/logstash.service

```

file /etc/systemd/system/logstash.service:

```
[Unit]
Description=logstash

[Service]
Type=simple
User=logstash
Group=logstash
# Load env vars from /etc/default/ and /etc/sysconfig/ if they exist.
# Prefixing the path with '-' makes it try to load, but if the file doesn't
# exist, it continues onward.
EnvironmentFile=-/etc/default/logstash
EnvironmentFile=-/etc/sysconfig/logstash
ExecStart=/usr/share/logstash/bin/logstash "--path.settings" "/etc/logstash"
Restart=always
WorkingDirectory=/
Nice=19
LimitNOFILE=16384

[Install]
WantedBy=multi-user.target

```

file /etc/systemd/system/multi-user.target.wants/logstash.service:

`same as above`

file /etc/default/logstash:

```
LS_HOME="/usr/share/logstash"
LS_SETTINGS_DIR="/etc/logstash"
LS_PIDFILE="/var/run/logstash.pid"
LS_USER="logstash"
LS_GROUP="logstash"
LS_GC_LOG_FILE="/var/log/logstash/gc.log"
LS_OPEN_FILES="16384"
LS_NICE="19"
SERVICE_NAME="logstash"
SERVICE_DESCRIPTION="logstash"

```

file /etc/sysconfig/logstash:

`empty`

---

<div class="post-metadata">

**Author:** ![sud0](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sud0](https://discuss.elastic.co/u/sud0)\
**Post date:** [October 8, 2019, 10:24pm UTC](https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466/4 "2019-10-08T22:24:06Z")

</div>

[This issue](https://discuss.elastic.co/t/error-unable-to-locate-appender-sys-ls-log-format-rolling-for-logger-config-root/107942/7) seems to be related.

---

<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:** [October 8, 2019, 11:28pm UTC](https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466/5 "2019-10-08T23:28:39Z")

</div>

[This](https://discuss.elastic.co/t/why-do-logstashs-internal-logs-and-stdout-end-up-in-var-log-messages/179485/2) issue and [this](https://discuss.elastic.co/t/logstash-logging-to-var-log-messages/186085/2) issue are related.

---

<div class="post-metadata">

**Author:** ![sud0](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sud0](https://discuss.elastic.co/u/sud0)\
**Post date:** [October 8, 2019, 11:35pm UTC](https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466/6 "2019-10-08T23:35:20Z")

</div>

The solution proposed [here](https://discuss.elastic.co/t/why-do-logstashs-internal-logs-and-stdout-end-up-in-var-log-messages/179485/2) solved my problem.

---

<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:** [November 5, 2019, 11:35pm UTC](https://discuss.elastic.co/t/removing-logstash-logs-from-syslog/202466/7 "2019-11-05T23:35:24Z")

</div>

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