-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
in_systemd: prevent infinite loop #899
Comments
kabakaev
added a commit
to c445/fluent-bit
that referenced
this issue
Apr 17, 2019
It fixes fluent-bit issue fluent#899. Signed-off-by: Alexander Kabakaev <[email protected]>
kabakaev
added a commit
to c445/fluent-bit
that referenced
this issue
May 1, 2019
It fixes fluent-bit issue fluent#899. Signed-off-by: Alexander Kabakaev <[email protected]>
kabakaev
added a commit
to c445/fluent-bit
that referenced
this issue
May 7, 2019
It fixes fluent-bit issue fluent#899. Signed-off-by: Alexander Kabakaev <[email protected]>
edsiper
pushed a commit
that referenced
this issue
May 7, 2019
It fixes fluent-bit issue #899. Signed-off-by: Alexander Kabakaev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Fluent-bit-v0.14.4 was caught in 100% CPU inside sd_journal_enumerate_data() of in_systemd. The GDB backtrace is given below.
The systemd-journald.service was restarted on that node prior to the observed 100% CPU loop, which might have triggered the issue.
Here we see that negative return values are possible:
https://github.com/systemd/systemd/blob/9e8b1ec08e8eb0b4611b7caf6adb8828feb32312/src/journal/sd-journal.c#L2312
But the negative values of the sd_journal_enumerate_data() are not handled in the current FLB:
I was unable to reproduce the issue so far. It seems that it was a combination of journald restart with some other factors, such as removal of a systemd log database file due to journald vacuum.
Backtrace of the frozen process:
Unfortunately, GDB messed up with this process upon detach, so i was not able to step over it to find out the actual return value.
The text was updated successfully, but these errors were encountered: