# Why do logstash's internal logs and stdout end up in /var/log/messages?

**URL:** <https://discuss.elastic.co/t/why-do-logstashs-internal-logs-and-stdout-end-up-in-var-log-messages/179485>\
**Category:** Logstash\
**Created:** [May 3, 2019, 6:42am UTC](https://discuss.elastic.co/t/why-do-logstashs-internal-logs-and-stdout-end-up-in-var-log-messages/179485 "2019-05-03T06:42:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 3, 2019, 12:54pm UTC](https://discuss.elastic.co/t/why-do-logstashs-internal-logs-and-stdout-end-up-in-var-log-messages/179485/2 "2019-05-03T12:54:50Z")

</div>

The default log4j2 configuration does not write to /var/log/messages. My guess is that you are running logstash as a service and systemd (or whatever service manager you use) is configured to forward its stdout to /var/log/messages. You could reconfigure systemd...

---

_[View the full topic](https://discuss.elastic.co/t/why-do-logstashs-internal-logs-and-stdout-end-up-in-var-log-messages/179485)._