docs: update troubleshooting section with service restart instructions and log checking commands

This commit is contained in:
bsiggel
2026-03-08 18:49:45 +00:00
parent 9e7e163933
commit ba657ecd3b

View File

@@ -723,12 +723,15 @@ bitbylaw/
| Issue | Solution | | Issue | Solution |
|-------|----------| |-------|----------|
| Step not registered | Check `_step.py` suffix, restart iii engine | | Step not registered | Check `_step.py` suffix, restart: `sudo systemctl restart motia.service` |
| Import errors | Check logs: `grep -i importerror iii.log` | | Import errors | Check logs: `journalctl -u motia.service \| grep -i importerror` |
| Code changes not applied | Auto-reload should work, force restart: `sudo systemctl restart motia.service` |
| ApiResponse validation | Use `status=200` not `status_code=200` |
| Redis unavailable | Service works with warnings, check `REDIS_HOST` | | Redis unavailable | Service works with warnings, check `REDIS_HOST` |
| `'_log' not found` | Inherit from `BaseSyncUtils` or implement `_log()` | | `'_log' not found` | Inherit from `BaseSyncUtils` or implement `_log()` method |
| Webhook not triggering | Verify endpoint in iii Console, check EspoCRM config | | Webhook not triggering | Verify endpoint: `curl http://localhost:3111/_console/functions` |
| xAI upload fails | Verify `XAI_API_KEY` and `XAI_MANAGEMENT_KEY` | | xAI upload fails | Set `XAI_API_KEY` and `XAI_MANAGEMENT_KEY` in `/etc/systemd/system/motia.service` |
| View logs | `journalctl -u motia.service -f` (follow) or `--since "10 minutes ago"` |
--- ---