Logs
Read and filter MuPiBox update and system logs in the browser, keep the log across reboots and enable a verbose player log for troubleshooting.
Under Maintenance → Logs you read logs directly in the browser – without SSH.
Sources
| Source | Content |
|---|---|
| Updates (persistent) | one file per update with all stages, boot confirmation or rollback – the last 15 updates |
| Player, touch interface, Spotify, audio | the respective services |
| Network / Wi-Fi | Wi-Fi connections and addresses |
| System agent, update services, kernel | system changes, update helper services, hardware messages |
| All MuPiBox services, whole system | everything together |
Passwords, Wi-Fi keys and tokens are redacted before they are shown.
Filtering
- Level: all, warnings and errors, errors only. Errors are marked red, warnings yellow.
- Filter: plain text (any case) or a regular expression between slashes, e.g.
/error|failed/. The expandable help shows clickable examples and the most important characters. An invalid expression is marked red. - Lines and Refresh every 5 s for live watching.
- Download saves the visible lines as a text file – handy for bug reports.
Keeping the system log across reboots
Normally the system log lives in memory and only reaches back to the last start. With this switch (off by default) the box keeps it across reboots – at most 40 MB. Then "Previous boot" works too, e.g. to see why the box crashed.
- It writes to the SD card; not needed for everyday use.
- Switching it off deletes the stored log.
Verbose player log
For troubleshooting playback problems: logs every player command, every load and the messages of the playback program for 1, 4 or 24 hours. Addresses appear without access keys. It switches itself off when the time is up.