taodeng/ocp
1
0
Fork 0
mirror of https://github.com/dtzp555-max/ocp.git synced 2026-07-19 09:44:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: remove outdated troubleshooting workarounds

Browse Source 
Removed v3.0.x migration guide, old idleTimeoutSeconds workaround
(auto-handled by setup.mjs since v3.2.1), and manual session cleanup
instructions. Replaced with concise troubleshooting for common issues.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
taodeng
2026-04-12 13:29:05 +10:00
co-authored by Claude Opus 4.6
parent f8ca9b85b0
commit e326cee9dd
1 changed files with 9 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+9 -36
View File
@@ -391,52 +391,25 @@ After installing the gateway plugin, use `/ocp` slash commands in your chat:
## Troubleshooting ## Troubleshooting
### Requests fail with exit 143 / SIGTERM after ~60 seconds ### Requests fail or agents stuck
**Symptom:** Claude returns errors or stops responding after about 60 seconds, especially during tool use (Bash, Read, etc.).
**Cause:** OpenClaw's gateway has a default `idleTimeoutSeconds` of 60 seconds. When Claude calls tools, the token stream pauses while the tool executes — if that takes longer than 60s, the gateway kills the connection.
**Fix:** `setup.mjs` (v3.2.1+) sets this automatically. If you installed an older version, add this to `~/.openclaw/openclaw.json`:
```json
{
"agents": {
"defaults": {
"llm": {
"idleTimeoutSeconds": 0
}
}
}
}
```
Then restart: `openclaw gateway restart`
### Agents stuck in "typing" but never respond
Usually caused by stuck sessions from previous timeout errors. Fix:
```bash ```bash
# Clear all sessions # Clear sessions and restart
ocp clear ocp clear
# Restart both services
ocp restart ocp restart
# If using OpenClaw gateway
openclaw gateway restart openclaw gateway restart
``` ```
If that doesn't help, manually clear the session store: ### Usage shows "unknown"
Usually caused by an expired Claude CLI session. Fix:
```bash ```bash
# Find and reset stuck Telegram sessions claude auth login
cat ~/.openclaw/agents/main/sessions/sessions.json ocp restart
# Remove entries with "telegram" channel, then restart gateway
``` ```
## Upgrading from v3.0.x
If you installed OCP before v3.1.0, the auto-start service used names that OpenClaw's gateway detected as conflicting (`ai.openclaw.proxy` on macOS, `openclaw-proxy` on Linux). Running `node setup.mjs` or `ocp update` will automatically migrate to the new neutral names.
## Environment Variables ## Environment Variables
| Variable | Default | Description | | Variable | Default | Description |