Bugzilla – Bug 2461
Scan crashes slimserver when database is MySQL and file is a wav
Last modified: 2011-03-16 04:19:50 UTC
A while back I switched the database used by Slimserver to MySQL and all worked fine. Since 6.2, Slimserver crashes when attempting to do a scan with the following error in /tmp/slimserver.log. Apparently I had some wav files in that directory and their existence caused this error. Previous versions did not crash. 2005-10-31 12:46:30.3984 DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ':///var/music/flac/astrud_gilberto/compact_jazz/beach_samba.wav Can't update 1260: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ':///var/music/flac/astrud_gilberto/compact_jazz/beach_samba.wav at /usr/local/slimserver/Slim/DataStores/DBI/DBIStore.pm line 1437 2005-10-31 12:46:30.4015 Slim::DataStores::DBI::ContributorTrack Slim::DataStores::DBI::ContributorTrack=HASH(0xa5508e8) destroyed without saving changes to role at /usr/local/slimserver/slimserver.pl line 0 This is on Mandrake 10.1.
This sounds more like a busted playlist..
The problem continued even after dropping and recreating the database from scratch so it is not a matter of having bad leftover data.
what about left over playlist files? If those are rescanned with included stale date, it could be exactly what Dan was talking about. Try moving all of your playlists temporarily, or removing teh playlist folder setting before a clear and scan.
I don't have a playlist folder and the playlist folder entry in the server setup is empty since I don't use playlists.
Well, I can no longer reproduce the problem. Unfortunately I got rid of the wav files that caused the problem and now I cannot reproduce it with a newly created wav file. I will close the bug until such time that it happens again.