I managed to crash Lyrion v9.0.2 (former SqueezeBox LMS) without any reason. I suspect a reboot of the home server caused it to re-index, and it crashed and exited on some .mp3 files. So, here's a quick check to see if it is running, and what caused it to crash.
1. Go to http://192.168.0.6:9000/
The regular web interface should come up. If it doesn't, then there could be something wrong
Wrong port
1. You're accidentally set it to use another port. This could happen during install, two instances running in parallel, or another application using that port. Check the server.log file, where you probably will find 9001 or 9002 or something similar.
Solution: use a web browser, open the Lyrion web interface by going to the 'wrong' port (ie. not 9000):
https://192.168.0.6:9001 ...or something similar!
...then change it through Lyrion settings to 9000
Settings / Advanced / Network / Web Server Port Number: 9000
Server busy
2. After a fresh install Lyrion might be indexing your music files. If there are thousands of files, this can take some time, and Lyrion isn't reporting this in any way. Check with task manager if your PC is very busy. Typically, the 'Perl Interpreter' will be busy, and so will CPU, drive C: (where your database is located) and any drive where your music files reside.
Solution: just wait.
2. Check if the Lyrion service is running
Start services.msc (or create a shortcut to it)
Look for Lyrion Music Server. It should be 'Running' and the startup type should be 'Automatic (Delayed Start)'.
3. Check the contents of server.log
To make it easier to find it back, first create a shortcut to the place where Lyrion keeps its log files. This location depends on the way it was installed / upgraded. and the OS.
On my Media6 homeserver, running Windows 10, and upgraded over the years from Windows 7 to Windows 10, to Windows 10 x64, and upgraded from Logitech LMS to Lyrion 9.0.2, it's here:
C:\Documents and Settings\All Users\Application Data\Squeezebox\Logs
It can be in a different location on your machine!
The file server.log should start with something like this:
- [25-04-06 16:35:27.4091] main::init (387) Starting Lyrion Music Server (v9.0.2, 1741501853, Thu Mar 13 14:57:26 CUT 2025) perl 5.032001 - MSWin32-x64-multi-thread
- [25-04-06 16:35:38.7697] main::init (661) Server done init: http://192.168.0.6:9000
So, I'm running Lyrion v9.0.2, build 1721501853, on Windows 64.
Also, Lyrion is listening on port https://192.168.0.6:9000 for any web clients.
4. Typical APE issues (and the reason for this post)
v9.0.2 of Lyrion has some issues with .mp3 files with APE tages, as well as real .APE files.
The server.log file showed only a few lines with errors like this:
APE: [Ran out of tag data before number of items was reached]
Using MP3Tag, I found the following tag in the problematic .mp3 files:
Tag ID3v2.3 (ID3v1 ID3v2.3 APEv2)
There doesn't seem to be a real work-around to that. What I did is to re-convert the problematic files using dBPowerAmp music converter to (regular) .mp3 files.
5. Looking for other files and databases
The following folder was empty (?):
c:\ProgramData\Lyrion\
... but there is stuff here:
c:\ProgramData\SqueezeBox\
Database
In my setup, the database is located (by default) at:
c:\ProgramData\SqueezeBox\Cache\library.db
It's a lot snappier on an SSD, and it does like breathing space, so keep enough space free.
Music
You have defined the location of your music yourself. My music and playlists are stored here:
d:\music\tracks
d:\music\playlists
Putting those on an SSD makes little use, unless you dislike spinning platters 😁
More
- This may be related (.APE issues, discussed on the Lyrion community)
- More Lyrion / SqueezeBox
No comments:
Post a Comment