docs: refresh gateway status deep mirrors

This commit is contained in:
Peter Steinberger
2026-04-04 19:06:30 +01:00
parent f3ce1bdb4f
commit 3bf538d720
4 changed files with 14 additions and 4 deletions

View File

@@ -1452,6 +1452,11 @@ Subcommands:
- `gateway install|uninstall|start|stop|restart`
- `gateway run`
Notes:
- `gateway status --deep` adds a system-level service scan. Use `gateway probe`,
`health --verbose`, or top-level `status --deep` for deeper runtime probe detail.
Common RPCs:
- `config.set` (validate + write full config; use `baseHash` for optimistic concurrency)

View File

@@ -127,7 +127,7 @@ All of these run on the main Gateway port and use the same trusted operator auth
```bash
openclaw gateway status
openclaw gateway status --deep
openclaw gateway status --deep # adds a system-level service scan
openclaw gateway status --json
openclaw gateway install
openclaw gateway restart
@@ -137,6 +137,9 @@ openclaw logs --follow
openclaw doctor
```
`gateway status --deep` is for extra service discovery (LaunchDaemons/systemd system
units/schtasks), not a deeper RPC health probe.
## Remote access
Preferred: Tailscale/VPN.

View File

@@ -183,7 +183,7 @@ openclaw gateway status
openclaw status
openclaw logs --follow
openclaw doctor
openclaw gateway status --deep
openclaw gateway status --deep # also scan system-level services
```
Look for:
@@ -191,6 +191,7 @@ Look for:
- `Runtime: stopped` with exit hints.
- Service config mismatch (`Config (cli)` vs `Config (service)`).
- Port/listener conflicts.
- Extra launchd/systemd/schtasks installs when `--deep` is used.
Common signatures:

View File

@@ -92,7 +92,7 @@ Then commands such as these will run inside that container automatically:
```bash
openclaw dashboard --no-open
openclaw gateway status --deep
openclaw gateway status --deep # includes extra service scan
openclaw doctor
openclaw channels login
```
@@ -191,7 +191,8 @@ Quadlet note:
- **Stop container:** `podman stop openclaw`
- **Remove container:** `podman rm -f openclaw`
- **Open dashboard URL from host CLI:** `openclaw dashboard --no-open`
- **Health/status via host CLI:** `openclaw gateway status --deep`
- **Health/status via host CLI:** `openclaw gateway status --deep` (RPC probe + extra
service scan)
## Troubleshooting