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
Wrong RUBYLIB path for resolv gem #277
Comments
Hmm, this glitches come from different kind of base image, so I've missed it. A) base image: alpine
B) base image: debian fluent/fluentd:v1.13.0-debian-1.0
|
#278 will fix this issue. |
Thanks for the quick fix! |
Hi, I am getting similar issue. I don't know for sure if this is due to RUBYLIB is set wrong or what. I have been fluentd alpine current(edge) image. 2022-06-29 20:10:38 +0000 [info]: parsing config file is succeeded path="/fluentd/etc/fluent.conf" / $ env LD_PRELOAD= / $ fluent-gem env
|
We hit the Fluentd burning CPU problem, because of a bug in the
resolv
lib, which is already described in multiple issues, e.g.: uken/fluent-plugin-elasticsearch#885, fluent/fluentd#3382.Read through the issues and determine that we were already using the
v1.13.0-1.0
docker image, which has the fixedresolv
andexcon
lib and theRUBYLIB
env update from here: #275.Despite that, we still saw the 100% CPU issue and after some investigation, I think I found the problem.
The
RUBLYLIB
env set here is wrong because the official fluentd docker file using another path for installed gems.I tested this out, based on the config file used in the PR above.
After fixing this in our environment, the issue is gone.
The text was updated successfully, but these errors were encountered: