SQLite DB corrupt

[Philip Meyer]

Restarted my SBS 7.6 server this morning, and noticed the following at startup. NB. It had previously been running without any noticeable problems:

[07:44:25.4033] Slim::Utils::SQLiteHelper::checkDataSource (296) Warning: Scanner database found, checking for a newer scan...
[07:44:25.4326] Slim::Schema::Storage::throw_exception (119) Error: DBI Exception: DBD::SQLite::db do failed: database disk image is malformed [for Statement "ATTACH 'D:\Squeezebox Server\beta\Cache\squeezebox-scanner.db' AS scannerdb"]
[07:44:25.4335] Slim::Schema::Storage::throw_exception (119) Backtrace:

frame 0: Slim::Utils::Log::logBacktrace (P:/Music/SlimServer/Beta/server/Slim/Schema/Storage.pm line 119)
frame 1: Slim::Schema::Storage::throw_exception (P:\Music\SlimServer\Beta\server\CPAN/DBIx/Class/Storage/DBI.pm line 1006)
frame 2: DBIx::Class::Storage:BI::__ANON__ (P:/Music/SlimServer/Beta/server/Slim/Utils/SQLiteHelper.pm line 299)
frame 3: (eval) (P:/Music/SlimServer/Beta/server/Slim/Utils/SQLiteHelper.pm line 298)
frame 4: Slim::Utils::SQLiteHelper::checkDataSource (P:\Music\SlimServer\Beta\server\slimserver.pl line 1045)
frame 5: main::checkDataSource (P:\Music\SlimServer\Beta\server\slimserver.pl line 572)
frame 6: main::init (P:\Music\SlimServer\Beta\server\slimserver.pl line 641)
frame 7: main::main (P:\Music\SlimServer\Beta\server\slimserver.pl line 1138)

[07:44:25.4340] Slim::Utils::SQLiteHelper::checkDataSource (328) Warning: Scanner database corrupted (Carp::Clan::__ANON__(): DBI Exception: DBD::SQLite::db do failed: database disk image is malformed [for Statement "ATTACH 'D:\Squeezebox Server\beta\Cache\squeezebox-scanner.db' AS scannerdb"] at P:/Music/SlimServer/Beta/server/Slim/Schema/Storage.pm line 123
), ignoring
[07:44:25.4347] Slim::Schema::Storage::throw_exception (119) Error: DBI Exception: DBD::SQLite::db do failed: SQL logic error or missing database
no such database: scannerdb [for Statement "DETACH scannerdb"]
[07:44:25.4354] Slim::Schema::Storage::throw_exception (119) Backtrace:

frame 0: Slim::Utils::Log::logBacktrace (P:/Music/SlimServer/Beta/server/Slim/Schema/Storage.pm line 119)
frame 1: Slim::Schema::Storage::throw_exception (P:\Music\SlimServer\Beta\server\CPAN/DBIx/Class/Storage/DBI.pm line 1006)
frame 2: DBIx::Class::Storage:BI::__ANON__ (P:/Music/SlimServer/Beta/server/Slim/Utils/SQLiteHelper.pm line 330)
frame 3: (eval) (P:/Music/SlimServer/Beta/server/Slim/Utils/SQLiteHelper.pm line 330)
frame 4: Slim::Utils::SQLiteHelper::checkDataSource (P:\Music\SlimServer\Beta\server\slimserver.pl line 1045)
frame 5: main::checkDataSource (P:\Music\SlimServer\Beta\server\slimserver.pl line 572)
frame 6: main::init (P:\Music\SlimServer\Beta\server\slimserver.pl line 641)
frame 7: main::main (P:\Music\SlimServer\Beta\server\slimserver.pl line 1138)

[erland]

Restarted my SBS 7.6 server this morning, and noticed the following at startup. NB. It had previously been running without any noticeable problems:

[07:44:25.4033] Slim::Utils::SQLiteHelper::checkDataSource (296) Warning: Scanner database found, checking for a newer scan...
[07:44:25.4326] Slim::Schema::Storage::throw_exception (119) Error: DBI Exception: DBD::SQLite::db do failed: database disk image is malformed [for Statement "ATTACH 'D:\Squeezebox Server\beta\Cache\squeezebox-scanner.db' AS scannerdb"]

I think you can get this if the scanner fails abruptly during a full rescan, for example if you kill the scanner process or it crashes. Could this have been the case ?

I got something similar when I had some issue in an earlier version of Custom Scan scan plugin in my development setup where I killed SBS process since the query never seemed to finish.

If the problem doesn't disappear, you can probably get around it by manually deleting the squeezebox-scanner.db file but it feels like SBS should be able to handle this itself if we are only talking about the scanner.db.

[Philip Meyer]

>I think you can get this if the scanner fails abruptly during a full
>rescan, for example if you kill the scanner process or it crashes.
>Could this have been the case ?
>
I may have done a controlled Abort Scan and then stopped SBS and restarted, which had previously worked for me. I didn't see an error at the time.

[JJZolx]

I've stopped, started, restarted and manually killed services, Ctrl-Ced out of the server running from the command line, had a blue screen or two, a couple of OS hangs that required hitting the reset button or power cycling the server, and aborted several dozen scans, and I've never had a corrupt SQLite database.