-
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
Segmentation fault when uploading logs to s3 #3823
Comments
I believe there were some connection-related improvements in the 1.7.x series that could have fixed this, it's probably worth upgrading to 1.7.9 or the 1.8.x releases. |
Sorry, @atheriel, for my delayed response, I've had some problems lately and couldn't come back to this issue. I tested with version 1.8.2 and 1.8.3 and had different problems, so I'd like to avoid updating to 1.8.x. I'll try 1.7.9 and see what happens. Thanks!! |
Sadly it looks like the problem keep happening:
It do not happen a lot, every now and then one of the pods restart due to this problem, it's a little bit annoying. |
This last sample was happening after updating to 1.7.9 |
I managed to test with 1.8.3 and it happened again, it's a bit different though:
Sometimes this error log I also checked this other issue #2507 and used the config:
It seems to not change the behavior. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Bug Report
Describe the bug
I run fluent bit as a daemon set in a k8s cluster and use it to send logs to S3 using S3 output plugin and every now and then one of fluent bit's pods restart due to SIGSEGV after failing to upload the log file to S3 bucket. It does not happen with all pods. I'm not really sure why it is happening.
Expected behavior
Fluent bit handling this kind of failure without segmentation violations.
Your Environment
Additional context
I also have other output to elastic search and some logs are routed to both outputs. I didn't post it and the filters because I don't think it is related to the problem but if you think it would help I can provide it.
The text was updated successfully, but these errors were encountered: