search

apache / incubator-hugegraph

A graph database that supports more than 100+ billion data, high performance and scalability (Include OLTP Engine & REST-API & Backends)
https://hugegraph.apache.org
Apache License 2.0
2.58k stars 512 forks source link

[Question] set restserver.url to http://0.0.0.0:8080 not work in 1.2 #2425

Closed LijunYu81 closed 4 months ago

LijunYu81 commented 5 months ago

Problem Type (问题类型)

server status (启动/运行异常)

Before submit

Environment (环境信息)

Your Question (问题描述)

I download the latest 1.2.0 version with "wget https://downloads.apache.org/incubator/hugegraph/1.2.0/apache-hugegraph-incubating-1.2.0.tar.gz" changed restserver.url to http://0.0.0.0:8080 or real ip in conf/rest-server.properties do db init with "bin/init-store.sh" bin/start-hugeserver.sh,then I got below error:

[root@iZuf68j5ei93s92673e81gZ apache-hugegraph-incubating-1.2.0]# bin/start-hugegraph.sh Starting HugeGraphServer in daemon mode... Connecting to HugeGraphServer (http://0.0.0.0:8080/graphs)...............The operation timed out(30s) when attempting to connect to http://0.0.0.0:8080/graphs

please advice how to change restserver.url to support remote access

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

No response

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

No response

dosubot[bot] commented 5 months ago

🤖

你好 @LijunYu81！我是 Dosu，您的友善的开源项目机器人。我在这里帮助您解决bug，回答问题，并成为贡献者，同时等待着人工维护者。我正在查看您的问题，很快会给您一个完整的答案。

imbajin commented 5 months ago

Two ways to check:

  1. miss the most important error log? (or restart the server to see the logs/*)
  2. try docker version to check the diff?
LijunYu81 commented 5 months ago

Two ways to check:

  1. miss the most important error log? (or restart the server to see the logs/*)
  2. try docker version to check the diff?

I checked logs/hugegraph-server.log, no log for this action

imbajin commented 5 months ago

Two ways to check:

  1. miss the most important error log? (or restart the server to see the logs/*)
  2. try docker version to check the diff?

I checked logs/hugegraph-server.log, no log for this action

@aroundabout submit a PR #2403 that enhance the error log while running the server(like network problems), maybe could try to use the docker latest version or modify the script to show it

dosubot[bot] commented 5 months ago

🤖

It seems like you're encountering issues with the error logs for the HugeGraph server. Unfortunately, as a technical support representative, I don't have the ability to create pull requests or issues directly in the repository. However, I can guide you on how to enhance the error log while running the server.

To enhance the error log, you can consider modifying the server's logging configuration to capture more detailed information about network problems or any other issues you're encountering. This can help in diagnosing and troubleshooting the problem effectively.

As for using the Docker version, you can try running the HugeGraph server using the Docker image to see if the behavior differs. This can help in isolating the issue and understanding if it's related to the server setup or environment.

If you need further assistance with modifying the script or configuring the server for enhanced error logging, feel free to ask for more specific guidance.

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

LijunYu81 commented 5 months ago

it is my first try on hugegraph, after yesterday's failure on startup, it automatically started up.... out of control absolutely....

[root@iZuf68j5ei93s92673e81gZ apache-hugegraph-incubating-1.2.0]# jps 502135 Jps 493135 HugeGraphServer

imbajin commented 5 months ago

it is my first try on hugegraph, after yesterday's failure on startup, it automatically started up.... out of control absolutely....

[root@iZuf68j5ei93s92673e81gZ apache-hugegraph-incubating-1.2.0]# jps 502135 Jps 493135 HugeGraphServer

Thanks for ur patience, start-timeout doesn't means the server process ran bad, the start script will auto-check the network connectivity so that may take a long time when meet some network problems(like DNS issue)

However, timeout without error message/log is really confused to most of the users, so the PR enhanced it, and u could try the latest docker image to test it & help it become better

github-actions[bot] commented 5 months ago

Due to the lack of activity, the current issue is marked as stale and will be closed after 20 days, any update will remove the stale label