-
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
Setting theaded to true in prometheus_scrape input causes SIGSEGV #9525
Labels
Comments
@anderssynstad is this running through a package or a custom build ? any more insights about the systems might help us |
@edsiper Verified it on a Debian 12 (fully patched) vps on Digital Ocean:
|
Not sure if it is related, but the yaml example on https://docs.fluentbit.io/manual/pipeline/inputs/node-exporter-metrics has the "same" result.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Describe the bug
Setting the
threaded
key totrue
forprometheus_scrape
input causes Fluent Bit to throw SIGSEGV errors.To Reproduce
Then changing
threaded
fromfalse
totrue
:Expected behavior
I expect a supported configuration key to not throw an error and cause the program to die.
Your Environment
Additional context
This generates a significant amount of noise due to the fluent-bit service keeps retarting.
On one random server, that fluent-bit service has retarted 184 times the last 8 hours alone ...
The text was updated successfully, but these errors were encountered: