-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Bootstrap check failures are easy to miss in logs #93074
Comments
Pinging @elastic/es-core-infra (Team:Core/Infra) |
8.4 corresponds with the Great Startup Refactor. That's the most likely cause of this change |
The code that did the log file logging was explicitly removed by #87809, leaving just the system err logging in Elasticsearch.java @rjernst can you provide some more context on whether this logging behaviour change for validation errors was deliberate? The best thing to do is probably to define the precise behaviour we want around validation exception specifically, then re-implement it in 8.7/8.6 |
This change to behavior was an unintentional side effect of the startup refactoring. I will work on a fix. |
Bootstrap check failures were unintentionally moved to the info level in the log output. This commit restores logging them as errors. closes elastic#93074
Bootstrap check failures were unintentionally moved to the info level in the log output. This commit restores logging them as errors. closes #93074
Elasticsearch Version
8.7.0-SNAPSHOT (50c1a78)
Installed Plugins
No response
Java Version
bundled
OS Version
Linux fedora 5.15.89-200.fc37.x86_64 #1 SMP Wed Jan 18 14:59:21 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Problem Description
When bootstrap checks fail, we only receive INFO logs and it's easy to miss the problem. The console output is as follows:
This is surprising as there is nothing else in the output. But what is worse is that elasticsearch.log (which is what the log asks to look and which was anyway the only file I was looking at the time) ends with the following:
This is very confusing as I was looking for an ERROR log and did not understand at all why Elasticsearch decided to stop. Nothing mentions in that log if something failed.
I looked a bit at minor Elasticsearch versions (7.17, 8.0, 8.2, 8.3, 8.4, 8.6 and main). It turns out that Elasticsearch 8.2.0 does everything correctly:
the console output makes sense:
the logs do include an ERROR:
However:
main
output but elasticsearch.log is still correct.main
outputSteps to Reproduce
xpack.security.enabled: false
to make sure the security by default does not addcluster.initial_master_nodes
that will make the bootstrap check passLogs (if relevant)
Here are the full logs on
main
:The text was updated successfully, but these errors were encountered: