[
https://issues.apache.org/jira/browse/SOLR-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994470#comment-14994470
]
Alexandre Rafalovitch commented on SOLR-8232:
---------------------------------------------
Ok. Perhaps I am missing something basic here. I thought that
solr-$SOLR_PORT-console.log contained three kinds of things:
* stuff sent there by log4j setting
* stuff sent to stdout by a random library (possibly not Solr) saying
System.out.println("Oh, fiddlesticks")
* stuff sent to stderr (because of 2>&1) by a random library (surely not Solr)
saying System.err.println("Sky is falling")
I am in full agreement on reducing duplication with the first (log4j) item.
Like you said, we are already logging it somewhere.
What I thought I was commenting on was that I want the second and third item to
stay captured somewhere. Which will not be if we do 1>/dev/null 2>&1 .
> bin/solr does not rotate console log file
> -----------------------------------------
>
> Key: SOLR-8232
> URL: https://issues.apache.org/jira/browse/SOLR-8232
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
> Affects Versions: 5.3
> Reporter: Upayavira
> Priority: Minor
>
> The bin/solr script, when started with bin/solr start, uses this command to
> start Solr:
> {code} nohup "$JAVA" "${SOLR_START_OPTS[@]}" $SOLR_ADDL_ARGS -jar start.jar \
> "-XX:OnOutOfMemoryError=$SOLR_TIP/bin/oom_solr.sh $SOLR_PORT
> $SOLR_LOGS_DIR" "${SOLR_JETTY_CONFIG[@]}" \
> 1>"$SOLR_LOGS_DIR/solr-$SOLR_PORT-console.log" 2>&1 & echo $! >
> "$SOLR_PID_DIR/solr-$SOLR_PORT.pid"
> {code}
> This sends console output to stdout, with no means of rotating the log file,
> meaning it will eventually fill the drive unless restarted.
> I would propose that stdout be written to dev/null and we use proper means
> for handling logging, which can do proper log rotation as configured by the
> user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
