bitflicker64 commented on issue #3103:
URL: https://github.com/apache/hugegraph/issues/3103#issuecomment-5042903052
Hi @neoblackcap — there are two separate things going on here.
**1. Why `docker logs` shows nothing on 1.7.0.** In the 1.7.0 image the
server writes its logs to a file inside the container
(`/hugegraph-server/logs/`) instead of stdout, so `docker logs` is empty by
design. This was fixed in #2980 (commit c0a2b93), which landed **after** the
1.7.0 release. I checked Docker Hub to be sure: the `1.7.0` image was last
rebuilt on **2026-03-22**, still before that fix (2026-04-05), so **no `1.7.0`
image has working `docker logs`** — pulling `1.7.0` again won't help. The fix
is only in the `latest` image (pushed 2026-07-21), and will ship in 1.8.0.
Two options:
- Pull `hugegraph/hugegraph:latest` and `docker logs <container>` will show
the server logs.
- Stay on 1.7.0 and read the log file directly:
```
docker exec <container> tail -500
/hugegraph-server/logs/hugegraph-server.log
```
(or mount it out with `-v /host/logs:/hugegraph-server/logs`).
**2. Why the container turns unhealthy.** Note that the logging fix only
makes logs *visible* — it doesn't change *why* the container goes unhealthy.
The healthcheck is `curl -fsS http://localhost:8080/versions`, so "unhealthy"
means the REST server stopped answering. To find the cause, grab the server log
around when it started failing, plus:
```
docker stats <container> --no-stream # memory/GC pressure
docker exec <container> jstack 1 > td.txt # is the JVM stuck?
```
Common culprits after long runs are JVM/GC pressure (heap ≈
[`MaxRAMPercentage=50`](https://github.com/apache/hugegraph/blob/master/hugegraph-server/Dockerfile#L42))
and accumulated task results; there are also a few open HStore issues in 1.7.0
(e.g. [#3095](https://github.com/apache/hugegraph/issues/3095)) — not
necessarily related, but worth ruling out. Sharing that log would help us
pinpoint it.
--
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]
