-
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
Segfault on startup (0.12.6) #406
Comments
which Docker image are you using ? |
fluent/fluent-bit:0.12 @edsiper |
backtrace
|
Doesn't like something about my output plugin config, then shuts down but doesn't check if the filter was initialised yet and segfaults. Not getting any error or log output though. |
that's very weird, would you please provide the output of:
|
That helps! How come |
I got a bit farther by fixing the kubernetes URL. My log shippers are using host networking for "reasons". It's still segfaulting though. This time, it can't find the pod because it looks like it assumes the hostname is the podname (which it isn't with host networking). I think we got around this in the fluentd plugin by setting an environment variable |
updated sosreport
|
Sorry, getting off topic. I'll work on sorting out the other errors. The original bug here is the segfault. Should it be checking the filter context is null before deleting it? It looks like all the filters have this issue - if the output filter fails to init, it tries to destroy the filters before they get init'd. |
@edsiper I made a PR to fix the tls output plugin error that was causing the segfault. fluent/fluent-bit-docker-image#7 |
I took a stab at fixing the segfault in #407. |
thanks for the contribution, closing this issue as fixed. note: I will make a maintenance v0.12.7 release with these changes in the next week. |
Trying fluent-bit for the first time, inside the docker image.
My config is
Not sure why the context is null, I'll try to dig into it some more.
The text was updated successfully, but these errors were encountered: