bitflicker64 opened a new issue, #2979: URL: https://github.com/apache/hugegraph/issues/2979
### Bug Type (问题类型) None ### Before submit - [x] 我已经确认现有的 [Issues](https://github.com/apache/hugegraph/issues) 与 [FAQ](https://hugegraph.apache.org/docs/guides/faq/) 中没有相同 / 重复问题 (I have confirmed and searched that there are no similar problems in the historical issue and documents) ### Environment (环境信息) - Server Version: 1.7.0 - Backend: HStore - OS: Linux (Docker) - Deployment: docker-compose (single node & cluster) ### Expected & Actual behavior (期望与实际表现) Expected: `docker logs hg-pd / hg-store / hg-server` should show application logs for debugging Actual: `docker logs` only shows a few entrypoint startup lines and nothing else. All actual JVM/application logs are silently written to files inside the container under /hugegraph-pd/logs/, /hugegraph-store/logs/, /hugegraph-server/logs/. This means during debugging you have to manually exec into the container and tail log files directly, which is not the expected Docker workflow. Root cause: Two issues working together: 1. The startup scripts redirect JVM stdout/stderr to a file via `>> ${OUTPUT} 2>&1` before Docker can capture it 2. The console appender in the dist log4j2.xml configs is defined but never wired to the root logger, so even without the shell redirect, most logs wouldn't reach stdout ### Vertex/Edge example (问题点 / 边数据举例) ```javascript ``` ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构) ```javascript ``` -- 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]
