DanielCarter-stack commented on issue #10507:
URL: https://github.com/apache/seatunnel/issues/10507#issuecomment-3950046979
<!-- code-pr-reviewer -->
Thanks for reporting this. I can confirm the bug exists in the official
Docker image.
**Root cause:** The Dockerfile at
`seatunnel-dist/src/main/docker/Dockerfile` (lines 10–12) intentionally
disables file logging by commenting out `rootLogger.appenderRef.file.ref` to
redirect logs to console (for container log collection). However,
`LogUtil.getLogPath()` in
`seatunnel-engine/seatunnel-engine-common/src/main/java/org/apache/seatunnel/engine/common/utils/LogUtil.java`
expects either `routingAppender` or `fileAppender` references to be enabled,
causing the REST API to fail with "Log file path is empty".
**Workaround:** Mount a custom `log4j2.properties` that restores file
logging:
```yaml
volumes:
- ./config/log4j2.properties:/opt/seatunnel/config/log4j2.properties
```
Ensure your custom config contains: `rootLogger.appenderRef.file.ref =
fileAppender`
If you'd like to submit a PR to fix this, consider adding an environment
variable to control whether file logging is enabled in Docker, or update the
Web UI to fall back to console logs when file appenders are disabled.
--
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]
