-
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
caught signal (SIGSEGV) with output elasticsearch #4412
Comments
I try 1.8.10 without reverting PR #3788 and with PR #4361 but it doesn't solve my issue. logs:
or
or
or
or
|
In some case, ES_BULK_CHUNK is not enough to increase size of the buffer Fix fluent#4412 Signed-off-by: Guillaume Smaha <guillaume.smaha@gmail.com>
In some case, ES_BULK_CHUNK is not enough to increase size of the buffer Fix fluent#4412 Signed-off-by: Guillaume Smaha <guillaume.smaha@gmail.com>
In some case, ES_BULK_CHUNK is not enough to increase size of the buffer Fix #4412 Signed-off-by: Guillaume Smaha <guillaume.smaha@gmail.com>
In some case, ES_BULK_CHUNK is not enough to increase size of the buffer Fix #4412 Signed-off-by: Guillaume Smaha <guillaume.smaha@gmail.com>
I have tried fluent-bit versions 1.7.x and 1.8.x and they all crash using tail input and elastic output with heavy JSON formatted logs. I tried the change in commit 0a061fb. Fluent-bit was a bit more stable but still crashed. I have gone back to version 1.6.10 which "just runs". I have noticed another issue with the 1.8.x series, it is continually logging errors on writing to elastic, but the "status": element in the elastic response only ever shows status 201 which should be "document created" and not an error. When I see errors reported with 1.6 I always see a real error status in the response, like a 429 for example. I think that the elastic response handling has also been broken. |
@fhitchen if you have a simple repro case for the crash, please provide the payload and config used. |
In some case, ES_BULK_CHUNK is not enough to increase size of the buffer Fix fluent#4412 Signed-off-by: Guillaume Smaha <guillaume.smaha@gmail.com>
What's the status of this issue? |
Bug Report
Describe the bug
I am having SEGV after few minutes on some pods and I think it is related to this PR #3788.
In some case,
append_size
is still inferior torequired
which meansmemcpy
is writing outside of the buffer and can create a SEGV.On 1.8.10 version, I try by adding a log to check this case GuillaumeSmaha@5b908dd and I got the log few time with a SEGV just after:
gdb-fluent-bit-4vljw.log
I also try to revert the change by using:
Until now, it is working for 20h without SEGV. (it was crashing after few minutes)
To Reproduce
Expected behavior
SEGV accous
Screenshots
Your Environment
Kubernetes 1.21.1
Ubuntu 18.04 or ubuntu 20.04
The text was updated successfully, but these errors were encountered: