[Bug] start server failed but still port in use
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 636
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 14
Description
### Bug Type (问题类型)
server status (启动/运行异常)
### 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.0.0 (Apache Release Version)
- Backend: RocksDB SSD
- OS: 6 CPUs, 20 G RAM, WSL Ubuntu 22.04
### Expected & Actual behavior (期望与实际表现)
I'm following the docto run the quickstart section。[official doc](https://hugegraph.apache.org/docs/quickstart/hugegraph-server/#512-rocksdb)
When I run the following command:`bin/init-store.sh`
it goes like this:
> sheli@sheli:~/project/incubator-hugegraph/hugegraph-server/apache-hugegraph-incubating-1.2.0$ ./bin/start-hugegraph.sh
Starting HugeGraphServer in daemon mode...
Connecting to HugeGraphServer (http://127.0.0.1:8080/graphs)................
curl: (7) Failed to connect to 127.0.0.1 port 8080 after 0 ms: Connection refused
The operation timed out(30s) when attempting to connect to http://127.0.0.1:8080/graphs
See /home/sheli/project/incubator-hugegraph/hugegraph-server/apache-hugegraph-incubating-1.2.0/logs/hugegraph-server.log for HugeGraphServer log output.
Later I found out that a certain file could not be downloaded because my dns did not configure the github IP.
due to the log:
> curl: (28) Failed to connect to github.com port 443 after 299341 ms: Connection timed out
Here goes the strange part, after I configured the dns, I run the shell again, and I got `The port 8182 has already been used`.
So the shell set 30s timeout, but the server start anyway after curl timeout, which was near 300s. BTW, the started server did not return a `200`.
### Vertex/Edge example (问题点 / 边数据举例)
_No response_
### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.