[ 
https://issues.apache.org/jira/browse/SOLR-14109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl resolved SOLR-14109.
--------------------------------
    Resolution: Fixed

> 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
>            Assignee: Jan Høydahl
>            Priority: Major
>             Fix For: 8.5, 8.4.1
>
>          Time Spent: 1h
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to