Logs and Diagnostics
Use logs to confirm when a fault happened and which subsystem reported it. Change one setting at a time after you have a timestamp.
Where to look
| Source | Typical content |
|---|---|
| GRiMbOS System → Connection Status | Live connection lamps. Not a historical log. |
| GRiMbOS System → System Status → Technical details | Raw health JSON. Sanitize before sharing. |
| Packaged launcher console or Windows log next to the install | Startup errors, Twitch, plugin load |
Linux journalctl for the grimbot service on Debian packages |
Same class of messages |
Exact file names depend on the package. Start from the directory that contains Start GRiMbot.bat or start-grimbot.sh.
Capture a useful extract
- Record the local time of the symptom.
- Reproduce the fault once.
- Copy only the lines around that time.
- Remove tokens, Client Secrets, cookies, and private addresses.
- Keep the feature name, GRiMbot version, and the exact error string.
A full diagnostic bundle can contain secrets. Do not upload one to a public wiki, chat, or untrusted host.
Evidence order
Follow How to use this manual. System Status, then Connection Status, then logs, then the narrowest documented fix.