-
Notifications
You must be signed in to change notification settings - Fork 906
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
Bookie does not show logs in 4.15.0rc0 #3165
Comments
I change the params in |
According to the log4j2 documentation if we set the old system property log4j2 should behave like log41 |
we could:
|
basically we should move forward with the work started here #2816 |
I suggest convert the configuration files to log4j2 format (YAML). I can work on this. |
Thanks @hangc0276, I agree with you. I remember testing logging with PR #2816 and the follow-up PR #2837. Anyway, I just checked out the project on commit
However, when doing the same exact experiment with last
|
Thanks for you reply @RaulGracia . I test #2837 by update the log4j version from 2.14.1 to 2.17.1, It only print few logs out. But use log4j 2.14.1 works well. The detail log paste here: #2816 (comment) |
@hangc0276 thanks, you are right, and I have checked that the problem with logging started with this PR switching to log4j 2.17.1. |
@eolivelli @hangc0276 please, check locally #3188 to validate that it fixes the logging problem in your settings. If it works for you, we would need to merge it, cherry-pick it to |
BUG REPORT
Describe the bug
It looks like in BK 4.15.0rc0 the bookie does not log anything.
We still have log4j1 configuration files in "conf" and we are not setting "log4j.configurationFile" (but log4j.configuration) in the shell scripts
https://logging.apache.org/log4j/2.x/manual/configuration.html
To Reproduce
Unpack the binary tarball and then run
bin/bookkeeper localbookie 3
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
The logs show up
The text was updated successfully, but these errors were encountered: