Bugzilla – Bug 3448
MySQL errors on startup
Last modified: 2008-09-15 14:39:24 UTC
May 25 nightly build slimserver fails to start with the following error messages: Argument "mysql" isn't numeric in numeric gt (>) at /PerlApp/DBIx/Migration.pm line 207. DBD::mysql::st execute failed: Table 'slimserver.genres' doesn't exist at C:\Program Files\SlimServer\server\CPAN/DBIx/Class/Storage/DBI.pm line 525. DBD::mysql::st execute failed: Table 'slimserver.tracks' doesn't exist at C:\Program Files\SlimServer\server\CPAN/DBIx/Class/Storage/DBI.pm line 525. DBIx::Class::ResultSet::count(): Error executing 'SELECT COUNT( * ) FROM tracks me' (): DBD::mysql::st execute failed: Table 'slimserver.tracks' doesn't exist at C:\Program Files\SlimServer\server\CPAN/DBIx/Class/Storage/DBI.pm line 525.
6.5 is flaky at the moment due to the vast splitscanner merge yesterday, so maybe this will disappear as manifold bugs are fixed, but for now I'll just leave it assigned to me to test as 6.5 recovers.
Fixed in change 7761 Will be in the June 6th nightly.
Now the June 6 release has the following errors: DBIx::Class::Storage::DBI::dbh(): DBI Connection failed: install_driver(SQLite) failed: Can't load 'auto/DBD/SQLite/SQLite.dll' for module DBD::SQLite: load_file:The specified module could not be found at /PerlApp/DynaLoader.pm line 212. at (eval 433) line 3 Compilation failed in require at (eval 433) line 3. Perhaps a required shared library or dll isn't installed where expected at C:\Program Files\SlimServer\server\CPAN/DBIx/Class/Storage/DBI.pm line 407 ERROR: forceCommit: Trying to commit transactions before DB is initialized! Had to create DBD::SQLite::dr::imp_data_size unexpectedly at /PerlApp/DBI.pm line 1182. Use of uninitialized value in subroutine entry at /PerlApp/DBI.pm line 1182. Had to create DBD::SQLite::db::imp_data_size unexpectedly at /PerlApp/DBI.pm line 1182. Use of uninitialized value in subroutine entry at /PerlApp/DBI.pm line 1182.
Worked fine for me on WinXP using the .exe version!
the sqlite messages are a bit odd, now that 6.5 should be using mysql. I suspect an upgrade script has fallen through the cracks, or a prefs file restored from backup at some point? Try removing the db... prefs from slimserver.pref and see if that clears it up. If you aren't tied to the rest of the prefs, you can just delete the whole file if you don't feel like editing it.
This should be fixed any number of ways now.. we are force-upgrading the use of SQLite to MySQL in the prefs. Please use the latest nightly. Thanks.