[ 
https://issues.apache.org/jira/browse/SOLR-12989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688453#comment-16688453
 ] 

Christine Poerschke commented on SOLR-12989:
--------------------------------------------

Okay, so I think i've tested the Linux part of the patch okay and would 
consider that ready for review.

The Windows part of the patch however, struggling with testing that:
* 7.5.0 binary release with a plain {{bin\solr start}} then at 
http://localhost:8983/solr/#/~java-properties shows {{solr.​log.​muteconsole}} 
as expected
* 7.5.0 binary release with the patched start script e.g. {{bin\alt.solr.cmd 
start}} does _not_ show {{solr.​log.​muteconsole}} (which is unexpected)


> facilitate -Dsolr.log.muteconsole opt-out
> -----------------------------------------
>
>                 Key: SOLR-12989
>                 URL: https://issues.apache.org/jira/browse/SOLR-12989
>             Project: Solr
>          Issue Type: Improvement
>          Components: logging, scripts and tools
>            Reporter: Christine Poerschke
>            Assignee: Christine Poerschke
>            Priority: Minor
>         Attachments: SOLR-12989.patch, SOLR-12989.patch
>
>
> Having made a small log4j2.xml edit
> {code}
>  <Root level="info">
>    <AppenderRef ref="RollingFile"/>
> -  <AppenderRef ref="STDOUT"/>
> +  <AppenderRef ref="STDOUT" level="error"/>
>  </Root>
> {code}
> I was surprised to find the errors logged in the {{solr.log}} file but not in 
> the {{solr-*-console.log}} file.
> https://lucene.apache.org/solr/guide/7_5/configuring-logging.html#permanent-logging-settings
>  very helpfully mentioned how the console logger is disabled when running in 
> the background.
> This ticket proposes to facilitate opting out of the muting via a 
> {{SOLR_LOG_MUTECONSOLE_OPT}} option.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to