PDA

View Full Version : Can't Squeezebox Server to do a re-scan



Stoker
2011-12-08, 10:55
Hi

I added a new CD to my collection a couple of days ago and when I tried to do a re-scan: "Settings:look for new and changed music" from the web interface the rescan failed. I have also tried a complete rescan with the same result.

When I look at the scan log (/var/log/squeezeboxserver/scanner.log) I can see amongst other things, the following:


[11-12-08 17:38:40.9790] Slim::Schema::Storage::throw_exception (82) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=sli mserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 950
[11-12-08 17:38:40.9802] Slim::Schema::Storage::throw_exception (82) Backtrace:

[11-12-08 17:38:40.9813] main::main (299) Warning: Issuing rollback() for database handle being DESTROY'd without explicit disconnect() at /usr/sbin/squeezeboxserver-scanner line 299.
[11-12-08 17:38:40.9823] main::main (311) Error: Failed when running main scan: [Carp::Clan::__ANON__(): DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=sli mserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 950
]
[11-12-08 17:38:40.9830] main::main (312) Error: Skipping post-process & Not updating lastRescanTime!
[11-12-08 17:38:40.9867] Slim::Schema::Storage::throw_exception (82) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=sli mserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 950
[11-12-08 17:38:40.9877] Slim::Schema::Storage::throw_exception (82) Backtrace:

[11-12-08 17:38:40.9890] Slim::Schema::Storage::dbh (53) Warning: Unable to connect to the database - trying to bring it up!

It looks like squeezebox server can't connect to the database. Does anyone have any idea what might be wrong? I've not changed anything recently. I'm using version 7.5.1 on Ubuntu. I can still access my library from the squeezebox and the web interface to the server, but without the new music so it would seem that the file system is still OK. Maybe the database is corrupt?

Is there anyway I can force squeezebox server to delete and then rebuild a new database?

garym
2011-12-08, 14:17
Hi

I added a new CD to my collection a couple of days ago and when I tried to do a re-scan: "Settings:look for new and changed music" from the web interface the rescan failed. I have also tried a complete rescan with the same result.

When I look at the scan log (/var/log/squeezeboxserver/scanner.log) I can see amongst other things, the following:


[11-12-08 17:38:40.9790] Slim::Schema::Storage::throw_exception (82) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=sli mserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 950
[11-12-08 17:38:40.9802] Slim::Schema::Storage::throw_exception (82) Backtrace:

[11-12-08 17:38:40.9813] main::main (299) Warning: Issuing rollback() for database handle being DESTROY'd without explicit disconnect() at /usr/sbin/squeezeboxserver-scanner line 299.
[11-12-08 17:38:40.9823] main::main (311) Error: Failed when running main scan: [Carp::Clan::__ANON__(): DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=sli mserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 950
]
[11-12-08 17:38:40.9830] main::main (312) Error: Skipping post-process & Not updating lastRescanTime!
[11-12-08 17:38:40.9867] Slim::Schema::Storage::throw_exception (82) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=sli mserver','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 950
[11-12-08 17:38:40.9877] Slim::Schema::Storage::throw_exception (82) Backtrace:

[11-12-08 17:38:40.9890] Slim::Schema::Storage::dbh (53) Warning: Unable to connect to the database - trying to bring it up!

It looks like squeezebox server can't connect to the database. Does anyone have any idea what might be wrong? I've not changed anything recently. I'm using version 7.5.1 on Ubuntu. I can still access my library from the squeezebox and the web interface to the server, but without the new music so it would seem that the file system is still OK. Maybe the database is corrupt?

Is there anyway I can force squeezebox server to delete and then rebuild a new database?

stop SbS, then delete the cache files from the folder they are sitting in (not sure which one for your install). Then start SbS and do a clear and rescan of your . That should rebuild your database.

Stoker
2011-12-10, 08:23
Thanks for the info Gary.

Does anyone know anything about the files that I should delete? Possible locations, names or partial names that I could search for?

I'm using Squeezebox server version 7.5.1 on Ubuntu.

Cheers

MeSue
2011-12-10, 10:33
Does anyone know anything about the files that I should delete? Possible locations, names or partial names that I could search for?



This should be listed under the information tab in the settings on the WebUI.

Mnyb
2011-12-10, 10:35
This should be listed under the information tab in the settings on the WebUI.

brute force approach delete the content of the cache folder .

Who location si spelled out as Sue sugested .

Stoker
2011-12-12, 05:52
Don't know whether there was just something wrong with my install or what but when I deleted the files in the cache directory (I stopped SBS first, deleted the contents of the cache directory and then re-started SBS)I could no longer get the web interface to respond and my Squeezebox couldn't connect either. I tried re-booting the server machine as well as several re-starts all to no avail.

In the end I just un-installed SBS and installed the latest version, and everything seems to be working now!

Cheers