Logs and troubleshooting¶

7. Logs and diagnostics¶

7.1 The logs of a box¶

Log	Content
page, tab "Log" (admin)	the last 5000 entries, live, with filters for level and text; "Save as file"
`/srv/tinyjukebox/log/tinyjukebox.log` (+ `.1` … `.4`)	the complete log; it stays over a restart
`journalctl -u tinyjukebox`	warnings and errors, and what the start script says; gone after a restart
`/srv/tinyjukebox/state/history.log`	one line per switch of version: when, from, to, why, by whom
`/var/log/tinyjukebox-install.log`	what the installer did

The service itself: sudo systemctl status tinyjukebox, sudo systemctl restart tinyjukebox. After a crash systemd starts it again by itself.

7.2 The logs of the library¶

Log	Content
page of the library, tab "Log"	the log of the library, and that of every box: warnings, errors and events the boxes sent, with filters; "Save as file"
NAS: `/var/packages/tinyjukebox-library/var/library.log`	the log of the library; at the start its fingerprint
NAS: `var/server.log`	why a start failed
NAS: `/var/log/packages/tinyjukebox-library.log`	what the scripts of the package printed
Docker: `docker logs library`	the output of the library, the generated password of `admin`

The tab "Log" of the library helps when a box is not at hand: the boxes send their warnings and errors to the library, without passwords, keys or tag UIDs. A box that cannot start reports that too; the tab "Boxes" then shows "cannot start since …" (library.md, section 4.22).

7.3 More detail in the log¶

The box logs at the level INFO. For a search, set it to DEBUG:

A box of the installer has no config file of its own. Copy the one of its slot first: cp /srv/tinyjukebox/current/config/tinyjukebox.yaml /srv/tinyjukebox/config/.
In /srv/tinyjukebox/config/tinyjukebox.yaml set log-level: DEBUG.
sudo systemctl restart tinyjukebox.
After the search, remove the copy again and restart the service: from then on the file would be the config of every version, also of every later one.

7.4 Buttons, LED and reader¶

The tab "System" has the card "Hardware" for admins: what the drivers say about the buttons, the LED and the RFID reader, twice a second. If a button has no effect, it shows whether the button arrives at the box at all. Checking the hardware by hand on the console: operations.md, section 9.2.

9. If something does not work¶

The manual lists what a user can do (manual, section 12). For an admin:

Symptom	Look at	Cause and action
LED stays red	`sudo systemctl status tinyjukebox`, `journalctl -u tinyjukebox`	the service does not run or fails on start, e.g. an invalid config: the message names the path
No tag is recognized	the log: `RFID - …`	the line says why: the reader cannot be started, it does not answer (wiring, supply), or the program of the version is not trusted – then run the installer again
Web page not reachable	`sudo systemctl status tinyjukebox`	the service does not run; or the name `….local` is not found: use the address of the box
LED red, white, magenta, yellow in turn; nothing plays	tab "System"; `tinyjukebox-slot status`	the library is too old for the version of the box: update the library (section 4.3), or go back on the box (section 4.2)
The box does not get a new version	`tinyjukebox-slot status`, `tinyjukebox-slot check`; tab "Versions" of the library	update mode "by hand only" or "off"; the version is not `use`; the box went back from it before; the library has no access to the releases (section 3.7)
The box runs an older version again	`/srv/tinyjukebox/state/history.log`, tab "Boxes" of the library	the new version failed its probation and the box went back; the line says why
The page of the box says the library is not connected	tab "System", section "Library"; the log	the NAS is off or not in this WLAN: the box plays what it has and delivers its changes later
The library does not start	`var/server.log` on the NAS; `docker logs library`	the line says why, e.g. `var/library.yaml` is missing

More symptoms, with the lines of the log: operations.md, section 9.3.