[
https://issues.apache.org/jira/browse/SOLR-9570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527321#comment-15527321
]
Jan Høydahl commented on SOLR-9570:
-----------------------------------
The file {{solr-8983-console.log}} is simply a redirect of all stdout/err from
the start script. It is only written when in backgoround mode, and log4j's
ConsoleAppender is always muted when the file is written. The file is useful
since it will capture any errors happening outside of the logging system such
as System.out.println or stdout/stderr printouts from some of Solr's
dependencies etc. So we should never redirect stdout/err to {{/dev/null}}. I
think we should try to do some simple rotation not to lose potential important
info after a crash.
The main log will append, and when we switch to Log4j2 we can implement startup
rotation.
> Logs backed up on restart are kept forever
> ------------------------------------------
>
> Key: SOLR-9570
> URL: https://issues.apache.org/jira/browse/SOLR-9570
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Reporter: Jan Høydahl
>
> When (re)starting Solr, the start script will backup any existing
> {{solr.log}} or {{solr_gc.log}} to a file {{solr_log_<date>}} and
> {{solr_gc_log_<date>}} respectively. That may be all good, but these old
> copies are never cleaned up, as they are not under the control of log4j.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
