User defined a custom log4j config file (using env var) and changed log level inside the file to debug.
Besu was still logging at the info level because we override the value at startup and we don't use the one from the log4j file.
It's usually not an issue as user can modify it using the '--logging' CLI option.
But in the case where user defined a custom log4j config file it's expected to have the file log level as default value even if then the value can still be overridden by CLI option.
When defining a custom log4j config, the effective log level is the one indicated in the custom file.