-
Notifications
You must be signed in to change notification settings - Fork 66
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
fluent-bit service fails due to segmentation fault #1266
Comments
Hi @diegoauad, thank you for opening an issue. I have been investigating some similar issues other users have reported with MongoDB logging. Particularly we have seen issues with particularly complicated nested logs coming from MongoDB. Would you please open a support case so that we can assist in greater detail? In the support case, if you could include the output from our diagnostic tool as well as some representative Mongo logs if possible. You can also mention this GitHub Issue in the case. If you do open a support case, please respond here with the case number so we can investigate. |
Describe the bug
google-cloud-ops-agent-fluent-bit.service fails to start. A 'segmentation fault' error is shown in journalctl logs.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All Agent Ops services working correctly, or at least an informative error message about what's misconfigured.
Environment (please complete the following information):
Additional context
We are running MongoDB as a standalone replica, with authentication enabled. Monitoring works fine, we are experiencing issues with logging only.
The text was updated successfully, but these errors were encountered: