-
Notifications
You must be signed in to change notification settings - Fork 133
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
consistent error: caught signal (SIGSEGV) #383
Comments
I suspect this is caused by running a version that is older and must have a bug, we do not have reports of SIGSEGV with our latest and current stable tags: https://github.com/aws/aws-for-fluent-bit/blob/mainline/troubleshooting/debugging.md#downgrading-or-upgrading-your-version |
The release you are on is from October, it is very old: It has known bugs: #269 As noted here, you can search old issues by version: https://github.com/aws/aws-for-fluent-bit/blob/mainline/troubleshooting/debugging.md#searching-old-issues |
We believe this crash report is likely the same as is described here: fluent/fluent-bit#5753 (comment) The fix will be released in 2.28.1 #418 |
This bug seem to be persistent on the latest tag (2.29.0). "log_router" have 256MB of RAM and still exits with 139. |
@aws-patrickc Can you please share the Fluent Bit configuration and task definition that you used when you encountered the issue. Thanks! |
I believe I'm also encountering this same problem running the latest tag (2.29) as a sidecar to a Fargate service. My Container Definition is as follows:
This was working previously in a Task Definition that had 512M memory. However, since updating versions recently, it has been exiting with code 139 (SIGSEGV) consistently, even when memory was increased to 2048M for the task group. Not sure if that's helpful. |
@jensenak Apologies for the issue you are experiencing. Can you please open a new issue, and add this info as well as Fluent Bit log output, and which version you are using. |
Sorry, wasn't trying to raise a new issue. I just switched from |
@jensenak Thanks, that's why I asked for a new issue. We do not and can not patch old versions. Everyone affected by this issue, please upgrade to our latest or latest stable. If you still see SIGSEGV, please open a new issue. Thanks! https://github.com/aws/aws-for-fluent-bit#using-the-stable-tag |
Hi all,
I have an issue when running fluentbit in my EKS cluster. It consistently shows caught signal(SIGSEGV) error, and I checked the error code from fluent-bit container is 139.
Here is the error log from fluent-bit pod:
Here is the yaml for fluent-bit and its config
I have modified the memory buffer in fluent-bit config and container request memory but none of them helped.
The text was updated successfully, but these errors were encountered: