# Encoding issue depending on how logstash is started

**URL:** https://discuss.elastic.co/t/encoding-issue-depending-on-how-logstash-is-started/317136
**Category:** Logstash
**Tags:** elastic-stack-sql, windows
**Created:** [October 20, 2022, 3:35pm UTC](https://discuss.elastic.co/t/encoding-issue-depending-on-how-logstash-is-started/317136 "2022-10-20T15:35:13Z")
**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: [October 20, 2022, 4:20pm UTC](https://discuss.elastic.co/t/encoding-issue-depending-on-how-logstash-is-started/317136/2 "2022-10-20T16:20:25Z")

</div>

> [@simon137](#):
>
> Has anyone maybe encountered something similar in the past?

You are not alone. There are threads [here](https://discuss.elastic.co/t/incompatible-encodings-ibm437-and-utf-8/316918) and [here](https://discuss.elastic.co/t/8-4-2-incompatible-encodings-cp850-and-utf-8-issue-sending-db-records-to-elastic-after-upgrade-to-elastic-8-4-2-from-8-3-2/315697) reporting this issue after upgrading to 8.4.2. Neither thread provided any resolution.

For output redirection to affect whether you get the exception is baffling.

---

_[View the full topic](https://discuss.elastic.co/t/encoding-issue-depending-on-how-logstash-is-started/317136)._