一键启动超时

[qingtianlong97]

[HiClaw] 等待 Manager Agent 就绪（超时: 300s）...
[HiClaw] 等待中... (300s/300s)
[HiClaw ERROR] Manager Agent 在 300s 内未就绪。请检查: docker logs hiclaw-manager
(base) [root@xxx data]# docker logs hiclaw-manager
2026-03-06 01:39:11,236 INFO Set uid to user 0 succeeded
2026-03-06 01:39:11,238 INFO supervisord started with pid 1
2026-03-06 01:39:12,241 INFO spawned: 'minio' with pid 18
2026-03-06 01:39:12,245 INFO spawned: 'tuwunel' with pid 19
2026-03-06 01:39:12,247 INFO spawned: 'higress-apiserver' with pid 20
2026-03-06 01:39:12,249 INFO spawned: 'higress-controller' with pid 21
2026-03-06 01:39:12,252 INFO spawned: 'higress-pilot' with pid 23
2026-03-06 01:39:12,254 INFO spawned: 'higress-gateway' with pid 24
2026-03-06 01:39:12,257 INFO spawned: 'higress-console' with pid 31
2026-03-06 01:39:12,260 INFO spawned: 'element-web' with pid 38
2026-03-06 01:39:12,263 INFO spawned: 'mc-mirror' with pid 42
2026-03-06 01:39:12,265 INFO spawned: 'setup-host-symlinks' with pid 46
2026-03-06 01:39:12,268 INFO spawned: 'manager-agent' with pid 52
2026-03-06 01:39:12,270 INFO success: setup-host-symlinks entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2026-03-06 01:39:12,275 INFO exited: setup-host-symlinks (exit status 0; expected)
2026-03-06 01:39:12,281 INFO exited: tuwunel (exit status 101; not expected)
2026-03-06 01:39:13,262 INFO success: minio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,262 INFO success: higress-apiserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,262 INFO success: higress-controller entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,262 INFO success: higress-pilot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,262 INFO success: higress-gateway entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,263 INFO success: higress-console entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,263 INFO success: element-web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,263 INFO success: mc-mirror entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,266 INFO success: manager-agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:13,283 INFO spawned: 'tuwunel' with pid 126
2026-03-06 01:39:13,316 INFO exited: tuwunel (exit status 101; not expected)
2026-03-06 01:39:14,307 INFO exited: higress-console (exit status 1; not expected)
2026-03-06 01:39:14,345 INFO spawned: 'higress-console' with pid 161
2026-03-06 01:39:14,375 INFO exited: higress-console (exit status 1; not expected)
2026-03-06 01:39:16,289 INFO spawned: 'tuwunel' with pid 260
2026-03-06 01:39:16,291 INFO spawned: 'higress-console' with pid 262
2026-03-06 01:39:16,322 INFO exited: tuwunel (exit status 101; not expected)
2026-03-06 01:39:16,323 INFO exited: higress-console (exit status 1; not expected)
2026-03-06 01:39:19,302 INFO spawned: 'higress-console' with pid 296
2026-03-06 01:39:19,333 INFO spawned: 'tuwunel' with pid 306
2026-03-06 01:39:19,333 INFO exited: higress-console (exit status 1; not expected)
2026-03-06 01:39:19,362 INFO exited: tuwunel (exit status 101; not expected)
2026-03-06 01:39:20,306 INFO gave up: tuwunel entered FATAL state, too many start retries too quickly
2026-03-06 01:39:22,386 INFO spawned: 'higress-console' with pid 384
2026-03-06 01:39:22,415 INFO exited: higress-console (exit status 1; not expected)
2026-03-06 01:39:22,595 INFO gave up: higress-console entered FATAL state, too many start retries too quickly
2026-03-06 01:39:23,024 INFO exited: higress-gateway (exit status 0; expected)
2026-03-06 01:39:24,028 INFO spawned: 'higress-gateway' with pid 394
2026-03-06 01:39:25,153 INFO success: higress-gateway entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-06 01:39:25,161 INFO exited: higress-gateway (exit status 0; expected)
2026-03-06 01:39:26,165 INFO spawned: 'higress-gateway' with pid 433
2026-03-06 01:39:26,886 INFO exited: higress-gateway (exit status 0; not expected)
2026-03-06 01:39:27,890 INFO spawned: 'higress-gateway' with pid 482
2026-03-06 01:39:28,586 INFO exited: higress-gateway (exit status 0; not expected)
2026-03-06 01:39:30,591 INFO spawned: 'higress-gateway' with pid 523
2026-03-06 01:39:31,364 INFO exited: higress-gateway (exit status 0; not expected)
2026-03-06 01:39:34,370 INFO spawned: 'higress-gateway' with pid 573
2026-03-06 01:39:35,137 INFO exited: higress-gateway (exit status 0; not expected)
2026-03-06 01:39:36,139 INFO gave up: higress-gateway entered FATAL state, too many start retries too quickly
2026-03-06 01:42:13,388 INFO exited: manager-agent (exit status 1; not expected)
2026-03-06 01:42:13,391 INFO spawned: 'manager-agent' with pid 1205
2026-03-06 01:42:14,411 INFO success: manager-agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

[maksim0930]

同样问题。

[davidfrz]

同样问题 INFO gave up: manager-agent entered FATAL state, too many start retries too quickly

[johnlanni]

从日志看，有多个组件启动失败：tuwunel (exit 101)、higress-console (exit 1)、higress-gateway (exit 0)

根据 FAQ，这种情况通常是 Docker 内存不足 导致的。

解决方案：

1. 检查 Docker Desktop 内存设置，确保至少分配 4GB 内存
   • Docker Desktop → Settings → Resources → Memory
2. 增加内存后，重新运行安装脚本，选择删除并重新安装

bash <(curl -sSL https://higress.ai/hiclaw/install.sh)

安装脚本会检测到已有安装，选择删除可以清除陈旧数据重新开始。

---

From the logs, multiple components failed to start: tuwunel (exit 101), higress-console (exit 1), higress-gateway (exit 0)

According to the FAQ, this is usually caused by insufficient Docker memory.

Solution:

1. Check Docker Desktop memory settings, ensure at least 4GB is allocated
   • Docker Desktop → Settings → Resources → Memory
2. After increasing memory, re-run the installation script and choose delete and reinstall

bash <(curl -sSL https://higress.ai/hiclaw/install.sh)

The installer will detect the existing installation. Choosing delete will wipe stale data and start fresh.

[samchaolau]

同样的问题

[davidfrz]

当前问题通过更改共享目录能够生效

[lovenets]

当前问题通过更改共享目录能够生效

遇到同样问题，怎么更改呢？

[johnlanni]

您好！从您提供的日志看，有几个组件启动失败：

问题分析：

1. tuwunel 一直报错退出（exit status 101）
2. higress-console 启动失败（exit status 1）
3. higress-gateway 最终进入 FATAL 状态
4. manager-agent 虽然最后进入 RUNNING 状态，但整体服务不完整

可能原因：

1. 内存不足：建议将 Docker 内存调整到 4GB 以上
2. 配置脏数据：建议删除重装清除脏数据

解决方案：

1. 调整 Docker Desktop 内存：Settings → Resources → Memory
2. 重新执行安装命令，选择删除重装：

bash <(curl -sSL https://higress.ai/hiclaw/install.sh)

安装脚本检测到已有安装时会询问处理方式，选择删除后重装即可清除脏数据。

更多详情请参考 FAQ 中的"Manager Agent 启动超时或失败"章节。

[laojia-08]

同样的问题，有个前提是：Mac M4芯片的podman有这个问题，docker可正常安装，希望尽快修复这个bug

---

The same problem, there is a premise: Mac M4 chip podman has this problem, docker can be installed normally, I hope this bug will be fixed as soon as possible

[sailer132]

我也是这个问题，请问啥时候可以修复呢

[johnlanni]

@sailer132 看下manager-agent的日志呢，参考下faq里查看日志的方法

---

@sailer132 Let’s take a look at the log of manager-agent. Please refer to the method of viewing logs in the FAQ

[sailer132]

2026-03-15 17:33:27 2026-03-15 17:33:27,523 INFO Set uid to user 0 succeeded
2026-03-15 17:33:27 2026-03-15 17:33:27,526 INFO supervisord started with pid 1
2026-03-15 17:33:28 2026-03-15 17:33:28,532 INFO spawned: 'minio' with pid 31
2026-03-15 17:33:28 2026-03-15 17:33:28,534 INFO spawned: 'tuwunel' with pid 32
2026-03-15 17:33:28 2026-03-15 17:33:28,537 INFO spawned: 'higress-apiserver' with pid 34
2026-03-15 17:33:28 2026-03-15 17:33:28,539 INFO spawned: 'higress-controller' with pid 36
2026-03-15 17:33:28 2026-03-15 17:33:28,541 INFO spawned: 'higress-pilot' with pid 37
2026-03-15 17:33:28 2026-03-15 17:33:28,545 INFO spawned: 'higress-gateway' with pid 44
2026-03-15 17:33:28 2026-03-15 17:33:28,552 INFO spawned: 'higress-console' with pid 69
2026-03-15 17:33:28 2026-03-15 17:33:28,558 INFO spawned: 'element-web' with pid 79
2026-03-15 17:33:28 2026-03-15 17:33:28,561 INFO spawned: 'mc-mirror' with pid 81
2026-03-15 17:33:28 2026-03-15 17:33:28,562 INFO spawned: 'setup-host-symlinks' with pid 111
2026-03-15 17:33:28 2026-03-15 17:33:28,563 INFO spawned: 'manager-agent' with pid 117
2026-03-15 17:33:28 2026-03-15 17:33:28,565 INFO success: setup-host-symlinks entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2026-03-15 17:33:28 2026-03-15 17:33:28,830 INFO exited: setup-host-symlinks (exit status 0; expected)
2026-03-15 17:33:29 2026-03-15 17:33:29,558 INFO success: minio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,558 INFO success: tuwunel entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,558 INFO success: higress-apiserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,558 INFO success: higress-controller entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,558 INFO success: higress-pilot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,558 INFO success: higress-gateway entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,558 INFO success: higress-console entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,558 INFO success: element-web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,561 INFO success: mc-mirror entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:29 2026-03-15 17:33:29,743 INFO success: manager-agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:33:30 2026-03-15 17:33:30,983 INFO exited: higress-console (exit status 134; not expected)
2026-03-15 17:33:31 2026-03-15 17:33:31,063 INFO spawned: 'higress-console' with pid 2793
2026-03-15 17:33:31 2026-03-15 17:33:31,128 INFO exited: higress-console (exit status 134; not expected)
2026-03-15 17:33:32 2026-03-15 17:33:32,783 INFO spawned: 'higress-console' with pid 2867
2026-03-15 17:33:32 2026-03-15 17:33:32,828 INFO exited: higress-console (exit status 134; not expected)
2026-03-15 17:33:35 2026-03-15 17:33:35,803 INFO spawned: 'higress-console' with pid 2897
2026-03-15 17:33:35 2026-03-15 17:33:35,850 INFO exited: higress-console (exit status 134; not expected)
2026-03-15 17:33:38 2026-03-15 17:33:38,893 INFO spawned: 'higress-console' with pid 2975
2026-03-15 17:33:39 2026-03-15 17:33:39,095 INFO exited: higress-console (exit status 134; not expected)
2026-03-15 17:33:39 2026-03-15 17:33:39,170 INFO gave up: higress-console entered FATAL state, too many start retries too quickly
2026-03-15 17:36:42 2026-03-15 17:36:42,294 INFO exited: manager-agent (exit status 1; not expected)
2026-03-15 17:36:42 2026-03-15 17:36:42,295 INFO spawned: 'manager-agent' with pid 4041
2026-03-15 17:36:43 2026-03-15 17:36:43,872 INFO success: manager-agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-03-15 17:39:47 2026-03-15 17:39:47,589 INFO exited: manager-agent (exit status 1; not expected)
2026-03-15 17:39:47 2026-03-15 17:39:47,595 INFO spawned: 'manager-agent' with pid 5123
2026-03-15 17:39:49 2026-03-15 17:39:49,277 INFO success: manager-agent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
这个是docker容器的所有日志

[sailer132]

内存应该是够的

[icmdw]

感谢反馈！这个问题与 FAQ 中的"Manager Agent 启动超时或失败"高度相关。

问题分析

从日志看，manager-agent 反复启动失败（exit status 1）：

exited: manager-agent (exit status 1; not expected)
gave up: manager-agent entered FATAL state, too many start retries too quickly

排查步骤

1. 查看详细错误日志

docker exec -it hiclaw-manager cat /var/log/hiclaw/manager-agent.log
日志中会显示具体的启动失败原因。

2. 常见原因

情况一：内存不足

Docker VM 分配的内存不足。建议将内存调整到 4GB 以上：

• Docker Desktop → Settings → Resources → Memory

情况二：配置脏数据

可能是升级过程中配置损坏。建议重新执行安装命令，选择删除重装：

bash <(curl -sSL https://higress.ai/hiclaw/install.sh)
安装脚本检测到已有安装时会询问处理方式，选择删除后重装即可清除脏数据。

情况三：Mac M 系列芯片 + 低版本 Docker

如果你使用的是 Apple Silicon Mac，且 Docker Desktop 版本低于 4.39.0，可能存在兼容性问题。建议升级到 4.39.0 或更高版本。

请提供 manager-agent.log 的内容，我可以帮你进一步定位问题。

更多常见问题请参考 FAQ 文档

建议增加一种排查方向：如果查看详细错误日志 docker exec -it hiclaw-manager cat /var/log/hiclaw/mc-mirror.log存在mc命令permission denied报错且使用的是Linux系统，可能是由于开启了SELinux 的安全拦截导致，尝试在启动脚本docker卷挂载命令添加:z参数解决

WORKSPACE_MOUNT_ARGS="-v ${HICLAW_WORKSPACE_DIR}:/root/manager-workspace:z"
HOST_SHARE_MOUNT_ARGS="-v ${HICLAW_HOST_SHARE_DIR}:/host-share:z"
HOST_SHARE_MOUNT_ARGS="-v ${HICLAW_HOST_SHARE_DIR}:/host-share:z"