Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use latest systemd-journal #111

Merged
merged 1 commit into from
Sep 11, 2024

Conversation

kenhys
Copy link
Contributor

@kenhys kenhys commented Sep 11, 2024

There is known bug that systemd-journal 1.4.2 or older version doesn't work with custom memory allocator such as jemalloc because of inappropriate allocated memory handling.
As a result, it causes a SEGV. This bug was frequently reported from fluent-docker-image and fluentd-kubernetes-daemonset images users. [1]

[1] fluent/fluentd-docker-image#378

Recently, this bug was fixed [2] and released as systemd-journal 2.0.0. Now we should switch to it.

[2] ledbettj/systemd-journal#97

NOTE: systemd-journal 2.0.0 requires Ruby 3.0.0 or later, so need to bump base image version which provides Ruby 3.x - so use ubuntu:jammy for testing.

There is known bug that systemd-journal 1.4.2 or older version
doesn't work with custom memory allocator such as jemalloc because of
inappropriate allocated memory handling.
As a result, it causes a SEGV. This bug was frequently reported from
fluent-docker-image and fluentd-kubernetes-daemonset images users. [1]

[1] fluent/fluentd-docker-image#378

Recently, this bug was fixed [2] and released as systemd-journal 2.0.0.
Now we should switch to it.

[2] ledbettj/systemd-journal#97

NOTE: systemd-journal requires Ruby 3.0.0 or later, so need to bump
base image version which provides Ruby 3.x - so use ubuntu:jammy for
testing.

Signed-off-by: Kentaro Hayashi <[email protected]>
@kenhys kenhys merged commit f6b235b into fluent-plugins-nursery:master Sep 11, 2024
5 checks passed
@kenhys kenhys deleted the latest-systemd-journal branch September 11, 2024 05:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants