[Bug] describe the main problem

[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 (期望与实际表现)

pd 已经能正常启动
curl -s http://hdp1:8620/actuator/health | jq .status
"UP"
curl -s http://hdp1:8620/actuator/health | jq .status
"UP"
curl -s http://hdp1:8620/actuator/health | jq .status
"UP"
store 已经能正常启动
curl -s -H 'Authorization: Basic c3RvcmU6c3RvcmU=' http://hdp1:8620/v1/stores |jq .message
"OK"
curl -s -H 'Authorization: Basic c3RvcmU6c3RvcmU=' http://hdp2:8620/v1/stores |jq .message
"OK"
curl -s -H 'Authorization: Basic c3RvcmU6c3RvcmU=' http://hdp3:8620/v1/stores |jq .message
"OK"
hugegraph-server 的 hugegraph.properties 配置内容
gremlin.graph=org.apache.hugegraph.auth.HugeFactoryAuthProxy
vertex.cache_type=l2
edge.cache_type=l2
#vertex.default_label=vertex
backend=hstore
serializer=binary
store=hugegraph

pd config

pd.peers=hdp1:8686,hdp2:8686,hdp3:8686

task config

task.scheduler_type=distributed
task.schedule_period=10
task.retry=0
task.wait_timeout=10

search config

search.text_analyzer=jieba
search.text_analyzer_mode=INDEX

rocksdb backend config

rocksdb.data_path=./rocksdb
rocksdb.wal_path=./rocksdb/wal
hugegraph-server 的 gremlin-server.yaml 配置文件 只修改和增加的如下内容

这是修改的

host: hdp1
port: 8182

在文件末尾增加这些内容

authentication: {
authenticator: org.apache.hugegraph.auth.StandardAuthenticator,
authenticationHandler: org.apache.hugegraph.auth.WsAndHttpBasicAuthHandler,
config: {tokens: conf/rest-server.properties}
}
hugegraph-server 的 rest-server.properties 配置文件
restserver.url=http://hdp1:8080
gremlinserver.url=http://hdp1:8182

graphs=./conf/graphs
batch.max_write_ratio=80
batch.max_write_threads=0

configuration of arthas

arthas.telnet_port=8562
arthas.http_port=8561
arthas.ip=127.0.0.1
arthas.disabled_commands=jad
auth.authenticator=org.apache.hugegraph.auth.StandardAuthenticator

rpc.server_host=hdp1
rpc.server_port=8091
server.id=server-1
server.role=master
log.slow_query_threshold=1000
memory_monitor.threshold=0.85
memory_monitor.period=2000
usePD=true
在第一台节点上执行初始化报错了
hugegraph-server/bin/init-store.sh

Initializing HugeGraph Store...
main dict load finished, time elapsed 2827 ms
model load finished, time elapsed 71 ms.
Exception in thread "main" java.lang.IllegalArgumentException: Undefined vertex label: '~user'
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:167)
at org.apache.hugegraph.util.E.checkArgument(E.java:52)
at org.apache.hugegraph.StandardHugeGraph.vertexLabel(StandardHugeGraph.java:857)
at org.apache.hugegraph.auth.HugeGraphAuthProxy.lambda$vertexLabel$2(HugeGraphAuthProxy.java:272)
at org.apache.hugegraph.auth.HugeGraphAuthProxy.lambda$verifySchemaPermission$24(HugeGraphAuthProxy.java:945)
at org.apache.hugegraph.auth.HugeGraphAuthProxy.verifyResPermission(HugeGraphAuthProxy.java:970)
at org.apache.hugegraph.auth.HugeGraphAuthProxy.verifyResPermission(HugeGraphAuthProxy.java:956)
at org.apache.hugegraph.auth.HugeGraphAuthProxy.verifySchemaPermission(HugeGraphAuthProxy.java:943)
at org.apache.hugegraph.auth.HugeGraphAuthProxy.verifySchemaPermission(HugeGraphAuthProxy.java:936)
at org.apache.hugegraph.auth.HugeGraphAuthProxy.vertexLabel(HugeGraphAuthProxy.java:271)
at org.apache.hugegraph.auth.EntityManager.queryEntity(EntityManager.java:152)
at org.apache.hugegraph.auth.EntityManager.query(EntityManager.java:134)
at org.apache.hugegraph.auth.StandardAuthManager.findUser(StandardAuthManager.java:183)
at org.apache.hugegraph.auth.StandardAuthenticator.requireInitAdminUser(StandardAuthenticator.java:83)
at org.apache.hugegraph.auth.StandardAuthenticator.initAdminUser(StandardAuthenticator.java:52)
at org.apache.hugegraph.auth.StandardAuthenticator.initAdminUserIfNeeded(StandardAuthenticator.java:223)
at org.apache.hugegraph.cmd.InitStore.main(InitStore.java:89)
Initialization finished.
部署这个集群共使用三台节点 hdp1 、hdp2 、hdp3
只初始化hdp1节点就出现如上问题，连提示输入密码都没有
Vertex/Edge example (问题点 / 边数据举例)
Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

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

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

[github-actions]

Resolving the IllegalArgumentException: Undefined vertex label: '~user' Error

The error you're encountering during the init-store.sh process on your HugeGraph-Server node is due to the system being unable to find the schema definition for the ~user vertex label. This label is essential for the authentication mechanism.

####Cause Analysis
The init-store.sh script is responsible for initializing the backend storage and creating the necessary system schema, including those for authentication. The error originates from StandardAuthenticator.initAdminUserIfNeeded, which attempts to find or create the admin user. This process relies on the HugeGraphAuthProxy to interact with the graph schema.

Recommended Steps to Resolve

1. Verify Configuration Files: Ensure that your hugegraph.properties, gremlin-server.yaml, and rest-server.properties are correctly configured as per the recommendations in the documentation.
2. Clean Initialization: If this is a fresh deployment, ensure no previous schema data exists. If it's not a fresh deployment, you might need to clear the existing schema data for the authentication system before re-running init-store.sh.
3. Re-run init-store.sh: After verifying the configurations and cleaning up any existing schema data, re-execute hugegraph-server/bin/init-store.sh.

Note

If the issue persists, please provide more details about your environment and configuration for further assistance.

I'm an AI bot powered by DeepWiki + Groq, here to help answer your questions. Feel free to quote-reply with any follow-up questions you might have!

---

✅ Powered by DeepWiki + Groq — answer based on actual repo documentation.

[bitflicker64]

Resolving the IllegalArgumentException: Undefined vertex label: '~user' Error

The error you're encountering during the init-store.sh process on your HugeGraph-Server node is due to the system being unable to find the schema definition for the ~user vertex label. This label is essential for the authentication mechanism.

####Cause Analysis The init-store.sh script is responsible for initializing the backend storage and creating the necessary system schema, including those for authentication. The error originates from StandardAuthenticator.initAdminUserIfNeeded, which attempts to find or create the admin user. This process relies on the HugeGraphAuthProxy to interact with the graph schema.

Recommended Steps to Resolve

1. Verify Configuration Files: Ensure that your hugegraph.properties, gremlin-server.yaml, and rest-server.properties are correctly configured as per the recommendations in the documentation.
2. Clean Initialization: If this is a fresh deployment, ensure no previous schema data exists. If it's not a fresh deployment, you might need to clear the existing schema data for the authentication system before re-running init-store.sh.
3. Re-run init-store.sh: After verifying the configurations and cleaning up any existing schema data, re-execute hugegraph-server/bin/init-store.sh.

Note

If the issue persists, please provide more details about your environment and configuration for further assistance.

I'm an AI bot powered by DeepWiki + Groq, here to help answer your questions. Feel free to quote-reply with any follow-up questions you might have!

✅ Powered by DeepWiki + Groq — answer based on actual repo documentation.

tell me the exact

[github-actions]

Exact Steps to Resolve the Issue

To resolve the IllegalArgumentException: Undefined vertex label: '~user' error, follow these exact steps:

1. Backup Configuration Files: First, make a backup of your hugegraph.properties, gremlin-server.yaml, and rest-server.properties files to prevent any loss of configuration data.
2. Verify hugegraph.properties: Ensure that the hugegraph.properties file contains the correct configuration for the authentication mechanism. Specifically, check the gremlin.graph property is set to org.apache.hugegraph.auth.HugeFactoryAuthProxy.
3. Check gremlin-server.yaml: Verify that the gremlin-server.yaml file has the correct configuration for the authentication handler. The authenticator should be set to org.apache.hugegraph.auth.StandardAuthenticator, and the authenticationHandler should be set to org.apache.hugegraph.auth.WsAndHttpBasicAuthHandler.
4. Clean Storage Directory: Delete the contents of the storage directory specified in the rocksdb.data_path property in hugegraph.properties to ensure a clean initialization.
5. Re-run init-store.sh: Execute the hugegraph-server/bin/init-store.sh script again to re-initialize the storage and create the necessary schema.

Example Configuration

Here's an example of what the relevant parts of your hugegraph.properties and gremlin-server.yaml files should look like:

# hugegraph.properties
gremlin.graph=org.apache.hugegraph.auth.HugeFactoryAuthProxy
rocksdb.data_path=./rocksdb
rocksdb.wal_path=./rocksdb/wal

# gremlin-server.yaml
authentication: {
  authenticator: org.apache.hugegraph.auth.StandardAuthenticator,
  authenticationHandler: org.apache.hugegraph.auth.WsAndHttpBasicAuthHandler,
  config: {tokens: conf/rest-server.properties}
}

Note

If the issue persists after following these exact steps, please provide more details about your environment and configuration for further assistance.

I'm an AI bot powered by DeepWiki + Groq, here to help answer your questions. Feel free to quote-reply with any follow-up questions you might have!

---

✅ Powered by DeepWiki + Groq — answer based on actual repo documentation.

[Pranjal2007v]

assign it to me

[bitflicker64]

/assign-check @Pranjal2007v 7d

[github-actions]

🤖 Contributor Bio — @Pranjal2007v

Field	Value
🍴 Forked repo	✅ Yes
📅 Account created	9mo ago
👥 Followers	3
📦 Public repos	17
🔨 Commits in this repo	0
✅ PRs merged in this repo	0
📝 Issues opened in this repo	0

---

Requested deadline: 7 days

A maintainer can approve with:

/approve-assign @Pranjal2007v

🤖 Assign Bot — bio pulled from GitHub API

[bitflicker64]

/approve-assign @Pranjal2007v

[github-actions]

✅ @Pranjal2007v has been assigned by @bitflicker64.

⏰ Deadline: 2026-05-14 (7 days from now)

Please post an update at least once before the deadline. The bot will warn you 3 days before and unassign if there's no activity by 2026-05-14.

🤖 Assign Bot

[github-actions]

⚠️ Deadline reminder — @Pranjal2007v

You have 3 days left (deadline: 2026-05-14) to post an update on this issue.

If you need more time or can't continue, please let the maintainers know so someone else can pick this up.

🤖 Assign Bot

[github-actions]

⏰ Time's up — @Pranjal2007v has been unassigned.

The 7-day deadline passed with no update on this issue. This issue is now open for someone else to pick up.

@Pranjal2007v — if you'd still like to work on this, ask a maintainer to re-assign you.

🤖 Assign Bot