[
https://issues.apache.org/jira/browse/SOLR-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000654#comment-16000654
]
Bernd Fehling edited comment on SOLR-10632 at 5/8/17 12:21 PM:
---------------------------------------------------------------
I would also recommend changing
{noformat}solr-x.y.z/server/resources/log4j.properties{noformat} line
{noformat}"solr.log=${solr.log.dir}"{noformat} to
{noformat}"solr.log=${solr.solr.home}/../logs"{noformat} as it is in
solr-x.y.z/example/resources/log4j.properties
This eliminates a major pitfall while setting up separate node directories with
separate logging on one sever.
was (Author: befehl):
I would also recommend changing solr-x.y.z/server/resources/log4j.properties
line "solr.log=${solr.log.dir}" to
"solr.log=${solr.solr.home}/../logs" as it is in
solr-x.y.z/example/resources/log4j.properties.
This eliminates a major pitfall while setting up separate node directories with
separate logging on one sever.
> logfiles are moved to archived if server is still running
> ---------------------------------------------------------
>
> Key: SOLR-10632
> URL: https://issues.apache.org/jira/browse/SOLR-10632
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: logging
> Affects Versions: 6.5
> Reporter: Bernd Fehling
> Priority: Minor
>
> There are server logfiles without portnumber in logfile name. If another
> instance is started these logfiles are moved to archived, eventhough the
> other server is still running.
> Solution could be to give every logfile a name with the portnumber it belongs
> to. Or check if a logfile is still in use and quit with an error before
> moving to archived.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
