[ https://issues.apache.org/jira/browse/SOLR-10632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002355#comment-16002355 ]
Bernd Fehling commented on SOLR-10632: -------------------------------------- Well, I found my solution. Just wanted to give a hint where I (and probably others also) struggled when going from "-e cloud" to production. Any complains if I close this issue? > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org