[Bug] start-hugegraph.sh reports "Port 8080 already used" when port appears free?

Open

#2,756 opened on Apr 26, 2025 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 38/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: bash, java
Domain: backend, databases

Research direction

Start with bin/start-hugegraph.sh and reproduce the reported sequence after a forced server stop. Compare its port-check behavior with lsof -i :8080 and inspect the startup state left after a crash. Done means a free port is not reported as occupied and the server starts successfully on the first retry.

Written by the indexing model from the issue text.

Description

bug

Bug Type (问题类型)

server status (启动/运行异常)

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.5.0 (Apache Release Version)
OS: 16 G RAM, Ubuntu 24.04.2 LTS

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

apache-hugegraph-server-incubating-1.5.0/bin$ ./start-hugegraph.sh 
The port 8080 has already been used

apache-hugegraph-server-incubating-1.5.0/bin$ sudo lsof -i :8080

apache-hugegraph-server-incubating-1.5.0/bin$ ./start-hugegraph.sh 
Starting HugeGraphServer in daemon mode...
Connecting to HugeGraphServer (http://0.0.0.0:8080/graphs)...OK
Started [pid 44430]

Problem Description:

After a server crash or being killed forcefully
Running ./start-hugegraph.sh to start the server fails with the error "Port 8080 has already been used".
However, checking with lsof -i :8080 confirms that port 8080 is not actually being listened on by any process.
Sometimes, simply re-running the start script works.

Dominant language: Java
Stars: 3.2k
Forks: 637
Avg merge: 3d 18h
Merged PRs (30d): 23

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.