Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
I noticed this when running zkcli.sh from solr's docker image. The docker image sets the variable LOG4J_PROPS, causing the zkcli script to pick up and use that logger instead of the console logger. Problem with that is that Solr's log4j2 config relies on the solr.log.dir sysprop being set, which it is not when running this script.
So either fix the wrapper script to set solr.log.dir or, better, always log to stdout.
Attachments
Issue Links
- is caused by
-
SOLR-9047 zkcli should allow alternative locations for log4j configuration
- Closed
- links to