[
https://issues.apache.org/jira/browse/SOLR-14109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998982#comment-16998982
]
Jan Høydahl commented on SOLR-14109:
------------------------------------
Linking SOLR-9047 [~gchanan] since that is where the env var was introduced.
Since that we got a centralized stdout logger config, and I cannot see a reason
for not always using that for a CLI tool like this.
> zkcli.sh and zkcli.bat barfs when LOG4J_PROPS is set
> ----------------------------------------------------
>
> Key: SOLR-14109
> URL: https://issues.apache.org/jira/browse/SOLR-14109
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Reporter: Jan Høydahl
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I noticed this when running {{zkcli.sh}} from solr's docker image. [The
> docker image sets the variable
> {{LOG4J_PROPS}}|https://github.com/docker-solr/docker-solr/blob/master/8.3/Dockerfile],
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
