-
Notifications
You must be signed in to change notification settings - Fork 460
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
SIGBUS after journal rotation #4645
Comments
Still visible in version 4.4:
|
SIGBUS indicates that the backing pages of a mmap()-ed region is gone. Normally, this should not happen with a normal file system, as if the file itself is removed, as long as there's a reference to it (e.g. mmap), it should not be removed in reality, the backing storage would remain to be allocated while the filename itself is removed from the containing directory. What kind of filesytem hosts the systemd journal file? Is it a normal file system or a ramdisk, perhaps something else? We really can't do too much in this situation, at least if my assumptions are correct. But the question remains, what do you have as backing storage for the journal files? |
This can be somewhat related to: systemd/systemd#12042 As you can see, sometimes the journald will truncate a file, which might cause a SIGBUS in the reading side (e.g. syslog-ng) |
And here's the possible fix: systemd/systemd#24320 It is fixed in systemd v255, I am not sure which one you are running. But the same bug affects rsyslog and filebeat |
The journal is in a type ext4 partition of an SSD. Probably the issue that you mentioned can be the cause. I will let you know when we decide to upgrade. |
Thanks Alexeandra. Sorry it took this long for me to answer.
…On Tue, Dec 12, 2023 at 12:39 PM Alexandre Santos ***@***.***> wrote:
The journal is in a type ext4 partition of an SSD.
The machine is still using: systemd 252 (252.17-1~deb12u1).
Probably the issue that you mentioned can be the cause. I will let you
know when we decide to upgrade.
—
Reply to this email directly, view it on GitHub
<#4645 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFOK5SHDKJMELIHBIYWYCLYJA67JAVCNFSM6AAAAAA5CFBJZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJRHA3TAOBQGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
syslog-ng
Version of syslog-ng
Service file
Platform
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Debug bundle
Not Aviable
Issue
Failure
Steps to reproduce
I think it happening after the journal rotation:
Configuration
In attachment GX-101569.syslog-ng.zip
Input and output logs (if possible)
The text was updated successfully, but these errors were encountered: