RESOLVED: Workaround: disable jemalloc when image crashed (segmentation fault) with systemd plugin #385
Labels
Comments
|
ledbettj/systemd-journal#96 will fix the root cause. |
kenhys
added a commit
to kenhys/fluentd-kubernetes-daemonset
that referenced
this issue
Sep 11, 2024
systemd-journal 2.0.0 fixes segmentation fault with jemalloc memory allocator. fluent-plugin-systemd 1.1.0 adopts systemd-journal 2.0.0 or later. fluent/fluentd-docker-image#378 fluent/fluentd-docker-image#385 fluent#1517 Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
|
This issue was fixed via fluent-plugin-systemd 1.1.0 (which uses systemd-journal 2.0.0) Now no need to disable jemalloc explicitly. Please use fluent-plugin-systemd 1.1.0 or later. ref. Note Keep this issue open for a while to inform you. |
kenhys
changed the title
kenhys
added a commit
to fluent/fluentd-kubernetes-daemonset
that referenced
this issue
Sep 11, 2024
systemd-journal 2.0.0 fixes segmentation fault with jemalloc memory allocator. fluent-plugin-systemd 1.1.0 adopts systemd-journal 2.0.0 or later. fluent/fluentd-docker-image#378 fluent/fluentd-docker-image#385 #1517 Signed-off-by: Kentaro Hayashi <hayashi@clear-code.com>
|
3 months had passed since the issue was created to raise an attention. It's time to close it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There is a known issue that combination with systemd plugin and jemalloc causes a
crash bug.
There are some feedback from users.
Related issue:
Important
As a workaround, you can avoid a segmentation fault to disable jemalloc memory allocator by specifying empty LD_PRELOAD for each container.
Caution
UPDATE: 2024 Sep 11
fluent-plugin-systemd 1.1.0 (systemd-journal 2.0.0) was shipped to fix this issue.
Please use fluent-plugin-systemd 1.1.0 or later.
To Reproduce
See above mentioned issues and related bugs.
(Especially #378 is the simplified to reproduce without k8s)
Expected behavior
Even though jemalloc is enabled, it does not cause a segmentation fault)
Your Environment
- all of v1.16.x or laterYour Configuration
Your Error Log
Additional context
To avoid this issue, jemalloc memory allocator will be disabled by default for v1.17.0-1.3 or later and v1.16.5-1.3 or later for fluent-kubernetes-daemonset images.
If you don't use systemd plugin at all, no need to disable jemalloc memory allocator explicitly.
NOTE: recent version of jemalloc is not solution for us. checked with:
The text was updated successfully, but these errors were encountered: