FrankChen021 commented on pull request #10147: URL: https://github.com/apache/druid/pull/10147#issuecomment-870348038
@kailiu6 I see. You're using the node.sh to start the Druid process instead of using the supervise, which uses the run-druid.sh to start Druid. You could redirect the the stderr to a file like this: ```bash nohup $JAVA -Ddruid.node.type=$nodeType -Ddruid.log.path=$LOG_DIR `cat $CONF_DIR/$nodeType/jvm.config | xargs` -cp $CONF_DIR/_common:$CONF_DIR/$nodeType:$LIB_DIR/*:$HADOOP_CONF_DIR org.apache.druid.cli.Main server $nodeType > $LOG_DIR/$nodeType-console.log 2>&1 & ``` The stdout and stderr will be both redirected into a file like coordinator-console.log under `DRUID_LOG_DIR` which defaults to 'log'. If Druid processes run normally, there will be two log files: one is xxx-console.log, and another one is xxx.log. If your log4j2.xml configures no console output, these two log files are different. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
