Music Scanner aborting quickly on v9.0.2/v9.0.3-nightly
Describe the bug Suddenly unable to scan my library at all from Windows, tested on v9.0.2 and v9.0.3.
To Reproduce Steps to reproduce the behavior: 0. (If needed, configure the Lyrion service to 'Run As' a user with appropriate share access)
- Go to 'Server Settings - Basic Settings'
- Click on 'Media Folders'
- Configure a UNC-style path e.g. '\\localhost\someshare'
- Let the scanner try to rebuild the library
- View the scanner log
Expected behavior Any files in 'someshare' should be scanned and added to the library.
Screenshots
System Information (please complete the following information):
- Windows 10 Pro
- Material skin
- Chrome
- LMS version 9.0.3 - 1748542788 @ Fri May 30 03:52:11 CUT 2025
- No players involved in the report
Additional context
scanner.log is attached, as is the latest server.log (seems un-interesting)
For searchability, the relevant error seems to be:
[25-06-05 22:22:04.3636] main::main (346) Error: Failed when running main scan: [Carp::Clan::__ANON__(): DBI Exception: DBD::SQLite::st execute failed: called with 1 bind variables when 3 are needed [for Statement "
INSERT INTO scanned_files
(url, timestamp, filesize)
VALUES
(?, ?, ?)
" with ParamValues: 1='file:////10.0.0.100/audio/Isiliel%20-%20Qliffoth%20(2024)/Isiliel%20-%20Qliphoth.flac', 2=1747822880, 3=65234255] at C:/Program Files/Lyrion/server/Slim/Schema/Storage.pm line 126
You're saying "suddenly unable": can I assume that the same setup did work in the past?
The message logged is really odd, as it says "1 variable when 3 needed", but then lists all three of them. Maybe you shut down LMS, delete the library.db* from the cache folder and start over?
BTW: I'd recommend you head over to https://forums.lyrion.org where you'll likely get better support.
Will do, thanks for the suggestion. To be clear, yeah, this has been working for quite a long time (maybe since 2022 on this host?), and I don't feel like I've done anything wildly surgical to it recently. I'll zap the cache dir contents maybe completely and just let it figure things out.
Amusingly, this bump in the road made me finally get things going as I like on my real FreeBSD host, so maybe I'm done needing the Windows build.
Thanks again.