156 lines
4.2 KiB
Markdown
156 lines
4.2 KiB
Markdown
# Errors Log
|
|
|
|
## [ERR-20260210-001] cron tool deadlock
|
|
|
|
**Logged**: 2026-02-10T23:00:00 CST
|
|
**Priority**: high
|
|
**Status**: resolved
|
|
**Area**: config
|
|
|
|
### Summary
|
|
The internal `cron` tool causes deadlock/timeout when called directly. Agent times out after 10s waiting for response.
|
|
|
|
### Error
|
|
```
|
|
Tool execution timed out
|
|
Gateway logs show 80s+ response times
|
|
```
|
|
|
|
### Context
|
|
- Attempted to use `cron.add` to create scheduled job
|
|
- Calls hang indefinitely
|
|
- Gateway becomes unresponsive to subsequent cron calls
|
|
|
|
### Suggested Fix
|
|
Use `exec` to run CLI commands instead of calling `cron` tool directly:
|
|
```bash
|
|
exec: openclaw cron list
|
|
exec: openclaw cron add --name "job" ...
|
|
```
|
|
|
|
### Resolution
|
|
- **Resolved**: 2026-02-10T23:00:00 CST
|
|
- **Fix**: Installed ez-cronjob skill, documented CLI workaround
|
|
- **Notes**: Always prefer `exec` + CLI over direct `cron` tool calls
|
|
|
|
### Metadata
|
|
- Reproducible: yes
|
|
- Related Skills: ez-cronjob
|
|
- See Also: LRN-20260210-001
|
|
|
|
## [ERR-20260211-001] youtube-summarizer tool not triggered
|
|
|
|
**Logged**: 2026-02-11T12:30:00 CST
|
|
**Priority**: high
|
|
**Status**: in_progress
|
|
**Area**: workflow
|
|
|
|
### Summary
|
|
YouTube URL was posted in #youtube-summaries channel, but I responded conversationally instead of triggering the transcription tool.
|
|
|
|
### Error
|
|
Agent detected YouTube URL but did not:
|
|
1. Recognize it as a transcription trigger
|
|
2. Run `python tools/youtube-summarizer.py [URL]`
|
|
3. Return formatted transcript/summary
|
|
|
|
### Context
|
|
- URL posted in #youtube-summaries (dedicated channel)
|
|
- yt-dlp is installed and ready
|
|
- Tool exists at `tools/youtube-summarizer.py`
|
|
- Agent responded like a chatbot instead of executing tool
|
|
|
|
### Suggested Fix
|
|
Scan ALL incoming messages for YouTube URL patterns. When detected:
|
|
1. Extract video ID
|
|
2. Run summarizer script via exec tool
|
|
3. Post formatted output back to channel
|
|
|
|
### Resolution
|
|
- **Status**: In progress
|
|
- **Next step**: Test proper URL detection
|
|
|
|
### Metadata
|
|
- Reproducible: yes
|
|
- Related Files: tools/youtube-summarizer.py, notes/youtube-summaries-channel.md
|
|
- Tags: youtube, transcription, workflow, tool-execution
|
|
|
|
## [ERR-20260214-001] OpenClaw reset wipes gateway state
|
|
|
|
**Logged**: 2026-02-14T20:00:00 CST
|
|
**Priority**: high
|
|
**Status**: resolved
|
|
**Area**: gateway
|
|
|
|
### Summary
|
|
Rolling back OpenClaw version (to fix Discord bug) wiped all gateway state: cron jobs, session routing, agent configs. Workspace files survived, but runtime data lost.
|
|
|
|
### Error
|
|
```
|
|
Gateway service: stopped (state Ready)
|
|
cron list: empty (all jobs gone)
|
|
```
|
|
|
|
### Context
|
|
- Reset to v2026.2.9 to fix Discord session key bug
|
|
- Gateway service stopped, cron jobs disappeared
|
|
- Agent still worked (Discord plugin independent)
|
|
|
|
### Suggested Fix
|
|
After any OpenClaw reinstall/reset:
|
|
1. Check `openclaw gateway status`
|
|
2. Restart if stopped: `openclaw gateway restart`
|
|
3. Restore cron jobs via scripts or manual recreation
|
|
4. Verify all jobs running: `openclaw cron list`
|
|
|
|
### Resolution
|
|
- **Resolved**: 2026-02-14T22:00:00 CST
|
|
- **Fix**: Restarted gateway, recreated all cron jobs
|
|
- **Notes**: Gateway state != workspace files. State is ephemeral.
|
|
|
|
### Metadata
|
|
- Reproducible: yes (any reinstall)
|
|
- Related: Discord gateway bug v2026.2.12+
|
|
- See Also: LRN-20260214-001
|
|
|
|
---
|
|
|
|
## [ERR-20260214-002] Discord permissions reset on re-add
|
|
|
|
**Logged**: 2026-02-14T20:30:00 CST
|
|
**Priority**: medium
|
|
**Status**: resolved
|
|
**Area**: discord
|
|
|
|
### Summary
|
|
When OpenClaw was removed and re-added to Discord server (during reset troubleshooting), bot permissions were reset. Could not post to #news-brief.
|
|
|
|
### Error
|
|
```
|
|
message tool: Missing Access
|
|
cron job: succeeded but delivery failed
|
|
```
|
|
|
|
### Context
|
|
- Re-added bot to fix Discord connection issues
|
|
- Forgot to re-grant channel permissions
|
|
- News brief generated but not delivered 2026-02-15 8 AM
|
|
|
|
### Suggested Fix
|
|
After re-adding bot to Discord:
|
|
1. Verify bot can post to each channel
|
|
2. Check `Manage Messages`, `Send Messages` perms
|
|
3. Test post: `message send to [channel]`
|
|
4. Fix before automated jobs run
|
|
|
|
### Resolution
|
|
- **Resolved**: 2026-02-15T11:00:00 CST
|
|
- **Fix**: Corey re-added channel permissions
|
|
- **Notes**: Document all channels bot needs access to
|
|
|
|
### Metadata
|
|
- Reproducible: yes (any re-add)
|
|
- Related: OpenClaw reset
|
|
|
|
---
|