# Systemd version conflict / bug on journalbeat

**URL:** <https://discuss.elastic.co/t/systemd-version-conflict-bug-on-journalbeat/259569>\
**Category:** Beats\
**Tags:** journalbeat\
**Created:** [December 24, 2020, 9:06am UTC](https://discuss.elastic.co/t/systemd-version-conflict-bug-on-journalbeat/259569 "2020-12-24T09:06:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DenizParlak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/denizparlak/32/81179_2.png) [@DenizParlak](https://discuss.elastic.co/u/DenizParlak)\
**Post date:** [December 24, 2020, 9:06am UTC](https://discuss.elastic.co/t/systemd-version-conflict-bug-on-journalbeat/259569/1 "2020-12-24T09:06:16Z")

</div>

Hi all,

Our journalbeat deployed on the Kubernetes cluster and stopped shipping logs to the elasticsearch via logstash suddenly. We got this error message first:

/var/log/journal/ec28d502b342fad1a4d44d3a101845cf/system@643e63d4269b4f10b3c28c4699a271a3-0000000000000001-0005b70da77d609f.journal uses an unsupported feature, ignoring file.

We have identified the issue with the Elk stack and fixed in the sandbox environment. Problem is 'systemd 246' version where 'zstd' compression algorithm was introduced, and this version not compatible with older systemd versions. Once we downgraded CoreOS version (from Fedora 33 to Fedora 31) now everything is fine.

Could you provide the compatibility between these versions?

---

<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:** [January 21, 2021, 11:06am UTC](https://discuss.elastic.co/t/systemd-version-conflict-bug-on-journalbeat/259569/2 "2021-01-21T11:06:28Z")

</div>

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