[Bug] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes:

[bitflicker64]

Bug Type (问题类型)

None

Before submit

• 我已经确认现有的 Issues 与 FAQ 中没有相同 / 重复问题 (I have confirmed and searched that there are no similar problems in the historical issue and documents)

Environment (环境信息)

• Server Version: 1.0.0 (Apache Release Version)
• Backend: RocksDB x nodes, HDD or SSD
• OS: xx CPUs, xx G RAM, Ubuntu 2x.x / CentOS 7.x
• Data Size: xx vertices, xx edges

Expected & Actual behavior (期望与实际表现)

sd

Vertex/Edge example (问题点 / 边数据举例)

dsd

Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

[bitflicker64]

(base) [root@lnpg ~]# docker run -itd --name=hugegraph -p 8080:8080 --memory=8g --security-opt seccomp=unconfined -e PRELOAD=true -e JAVA_OPTS="-Xms2048m -Xmx2048m -XX:+UseG1GC" hugegraph/hugegraph:1.7.0
bf42813a9146eee0be3eba171ed8c218429d117f745728eb185881f647c7d759
(base) [root@lnpg ~]# docker logs -f hugegraph
[hugegraph-server-entrypoint] init hugegraph with non-auth mode
Initializing HugeGraph Store...
2026-06-29 00:52:05 [main] [WARN] o.a.h.c.HugeConfig - The config option 'arthas.telnet_port' is redundant, please ensure it has been registered
2026-06-29 00:52:05 [main] [WARN] o.a.h.c.HugeConfig - The config option 'arthas.http_port' is redundant, please ensure it has been registered
2026-06-29 00:52:05 [main] [WARN] o.a.h.c.HugeConfig - The config option 'arthas.disabled_commands' is redundant, please ensure it has been registered
2026-06-29 00:52:05 [main] [INFO] o.a.h.u.ConfigUtil - Scanning option 'graphs' directory './conf/graphs'
2026-06-29 00:52:05 [main] [INFO] o.a.h.c.InitStore - Init graph with config file: /hugegraph-server/conf/graphs/hugegraph.properties
2026-06-29 00:52:05 [db-open-1] [INFO] o.a.h.b.s.r.RocksDBStore - Opening RocksDB with data path: rocksdb-data/data/m
2026-06-29 00:52:05 [db-open-1] [INFO] o.a.h.b.s.r.RocksDBStore - Failed to open RocksDB 'rocksdb-data/data/m' with database 'default/hugegraph', try to init CF later
2026-06-29 00:52:05 [main] [INFO] o.a.h.b.c.CacheManager - Init RamCache for 'schema-id-DEFAULT-hugegraph' with capacity 10000
2026-06-29 00:52:05 [main] [INFO] o.a.h.b.c.CacheManager - Init RamCache for 'schema-name-DEFAULT-hugegraph' with capacity 10000
2026-06-29 00:52:05 [db-open-1] [INFO] o.a.h.b.s.r.RocksDBStore - Opening RocksDB with data path: rocksdb-data/data/s
main dict load finished, time elapsed 734 ms
model load finished, time elapsed 37 ms.
2026-06-29 00:52:06 [db-open-1] [INFO] o.a.h.b.s.r.RocksDBStore - Opening RocksDB with data path: rocksdb-data/data/g
2026-06-29 00:52:06 [main] [INFO] o.c.o.l.Uns - OHC using JNA OS native malloc/free
2026-06-29 00:52:06 [main] [INFO] o.a.h.b.c.CacheManager - Init LevelCache for 'vertex-DEFAULT-hugegraph' with capacity 10000:10000000
2026-06-29 00:52:06 [main] [INFO] o.a.h.b.c.CacheManager - Init LevelCache for 'edge-DEFAULT-hugegraph' with capacity 1000:1000000
2026-06-29 00:52:06 [main] [INFO] o.a.h.t.TaskManager - Use local as the scheduler of graph (hugegraph)
2026-06-29 00:52:06 [main] [INFO] o.a.h.b.c.CacheManager - Init RamCache for 'users-DEFAULT-hugegraph' with capacity 10240
2026-06-29 00:52:06 [main] [INFO] o.a.h.b.c.CacheManager - Init RamCache for 'users_pwd-DEFAULT-hugegraph' with capacity 10240
2026-06-29 00:52:06 [main] [INFO] o.a.h.b.c.CacheManager - Init RamCache for 'token-DEFAULT-hugegraph' with capacity 10240
2026-06-29 00:52:06 [main] [INFO] o.a.h.b.s.r.RocksDBStore - Write down the backend version: 1.11
2026-06-29 00:52:06 [main] [INFO] o.a.h.StandardHugeGraph - Graph 'DEFAULT-hugegraph' has been initialized
2026-06-29 00:52:06 [main] [WARN] o.a.h.c.HugeConfig - The config option 'arthas.telnet_port' is redundant, please ensure it has been registered
2026-06-29 00:52:06 [main] [WARN] o.a.h.c.HugeConfig - The config option 'arthas.http_port' is redundant, please ensure it has been registered
2026-06-29 00:52:06 [main] [WARN] o.a.h.c.HugeConfig - The config option 'arthas.disabled_commands' is redundant, please ensure it has been registered
2026-06-29 00:52:06 [main] [INFO] o.a.h.StandardHugeGraph - Close graph standardhugegraph[DEFAULT-hugegraph]
2026-06-29 00:52:06 [db-open-1] [INFO] o.a.h.b.s.r.RocksDBStore - Opening RocksDB with data path: rocksdb-data/data/m
2026-06-29 00:52:06 [db-open-1] [INFO] o.a.h.b.s.r.RocksDBStore - Opening RocksDB with data path: rocksdb-data/data/s
2026-06-29 00:52:06 [db-open-1] [INFO] o.a.h.b.s.r.RocksDBStore - Opening RocksDB with data path: rocksdb-data/data/g
2026-06-29 00:52:06 [main] [INFO] o.a.h.HugeFactory - HugeFactory shutdown
2026-06-29 00:52:06 [hugegraph-shutdown] [INFO] o.a.h.HugeFactory - HugeGraph is shutting down
Initialization finished.
Starting HugeGraphServer in daemon mode...
Connecting to HugeGraphServer (http://0.0.0.0:8080/graphs)....OK
Started [pid 1079]
Waiting for partition assignment...

[bitflicker64]

:miku /ask just to confirm — this is not a HugeGraph code issue. The pthread_create failed (EPERM) error is caused by the Docker host's seccomp profile blocking the clone syscall that the JVM needs to spawn GC threads at startup. HugeGraph's Docker image is fine; the same image works on most hosts. The fix is host-side: running with --security-opt seccomp=unconfined lifts the restriction and lets the JVM create threads normally. Can you confirm this diagnosis and whether there's anything we should add to the docs or image to surface a clearer error message for users hitting this?

[git-miku]

miku /ask

⚠️ I'm temporarily unavailable — please try again in a moment.

[bitflicker64]

:miku /ask just to confirm — this is not a HugeGraph code issue. The pthread_create failed (EPERM) error is caused by the Docker host's seccomp profile blocking the clone syscall that the JVM needs to spawn GC threads at startup. HugeGraph's Docker image is fine; the same image works on most hosts. The fix is host-side: running with --security-opt seccomp=unconfined lifts the restriction and lets the JVM create threads normally. Can you confirm this diagnosis and whether there's anything we should add to the docs or image to surface a clearer error message for users hitting this?

[git-miku]

miku /ask

⚠️ I'm temporarily unavailable — please try again in a moment.

[bitflicker64]

:miku /ask just to confirm — this is not a HugeGraph code issue. The pthread_create failed (EPERM) error is caused by the Docker host's seccomp profile blocking the clone syscall that the JVM needs to spawn GC threads at startup. HugeGraph's Docker image is fine; the same image works on most hosts. The fix is host-side: running with --security-opt seccomp=unconfined lifts the restriction and lets the JVM create threads normally. Can you confirm this diagnosis and whether there's anything we should add to the docs or image to surface a clearer error message for users hitting this?

[git-miku]

miku /ask

Your diagnosis is correct. This is not a HugeGraph code issue but a Docker host configuration problem. The pthread_create failed (EPERM) error occurs when the Docker host's seccomp profile blocks the clone syscall that the JVM needs to spawn GC threads at startup.

The HugeGraph Docker image is fine - it uses standard eclipse-temurin:11-jre-jammy and the entrypoint script simply passes through JVM options without any thread creation restrictions.

Documentation Recommendations

Consider adding a troubleshooting note to the Docker documentation about this seccomp issue:

File to update: hugegraph-server/hugegraph-dist/docker/README.md or docker/README.md

Add a section like:

## Troubleshooting

### pthread_create failed (EPERM)

If you encounter `pthread_create failed (EPERM)` errors during container startup, this may be caused by your Docker host's seccomp profile blocking the `clone` syscall that the JVM needs to spawn GC threads. 

**Solution**: Run the container with `--security-opt seccomp=unconfined`:

```bash
docker run -itd --name=hugegraph -p 8080:8080 --security-opt seccomp=unconfined hugegraph/hugegraph:1.7.0

This issue is host-specific and depends on your Docker daemon's security configuration.

The current Docker documentation doesn't mention this seccomp-related issue, so adding it would help users encountering this problem. 

## Notes

The HugeGraph codebase doesn't include any error handling for this specific seccomp-related failure since it occurs at the JVM level during thread creation, which is outside the application's control. The entrypoint script and startup scripts don't have visibility into this low-level threading failure.