Squeezebox Server plugin fails to start

[ViperGeek]

This is a continuation of an OT thread fragment I started in another thread (http://www.patriotmemory.com/forums/showthread.php?7080-Default-MySQL-username-and-password-%28RESOVLED%29) about default MySQL passwords.

I'm having problems getting the Logitech SqueezeCenter plug-in to start. I've uninstalled it and installed it a bunch of times. I've deleted the squeezebox database, assuming it'll recreate upon installation. Nothing will get the Squeeze Center to retain a status of ON.

I initially thought it might have something to do with the fact that I changed the root password in MySQL, but resetting the root password and recreating the slimserver user and database still hasn't helped.

I found the Squeezebox Wiki page that talks about using an existing MySQL database (http://wiki.slimdevices.com/index.php/ExistingMySQLInstance), which was very interesting, but still hasn't resolved my problem. For those curious, the page walks through creating the slimserver database and granting access to it by an account called slimserver. The credentials used by the Squeezebox Server plugin can be found in the file /APP/SQUEEZE/squeezeboxserver/prefs/server.prefs:

[root@javelin]# grep db server.prefs
dbpassword: ''
dbusername: slimserver

which I used when creating the slimserver account in MySQL, but still I've come up with no solution.

Does anyone have any ideas on what else to try?

- Dave

[ViperGeek]

More indication that my database or installation is FUBAR. This is from /APP/SQUEEZE/squeezeboxserver/Logs/server.log :

[11-07-26 18:40:14.6659] main::init (326) Starting Squeezebox Server (v7.5.5, r32521, Fri Jun 24 05:06:56 CST 2011) perl 5.010000
[11-07-26 18:40:19.3381] Slim::Schema::Storage::throw_exception (82) Error: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=3306;
database=slimserver','slimserver',...) failed: Access denied for user ''@'localhost' to database 'slimserver' at /VOLUME1/PLUGINAPP/SQUEEZE/squeezeboxserver/CPAN/DBIx/Class/Storage/DBI.pm line 950

Not quite sure why '' (null) is the username being attempted.

- Dave

[ViperGeek]

SUCCESS!!!

The issue wasn't the blank username, but rather the @'localhost' part that was messing up the works. When following the aforementioned instructions to create a new database and user, I ended up with an entry in the user table that looks like this:

Host = '%'
User = 'slimserver'
Password = ''

I then added another record in the user table of the mysql database as follows:

Host = 'localhost'
User = 'slimserver'
Password = ''

and the server started.

- Dave

[BadIntentions]

did you have the mysql plugin running when you install squeezebox server?

[ViperGeek]

did you have the mysql plugin running when you install squeezebox server?

Yes. MySQL was running during each of the failed, and the one successful installations. Modifying the slimserver MySQL account seems to have done it.

Of course, now I'm back to the issue where nothing gets indexed (ref. this thread (http://www.patriotmemory.com/forums/showthread.php?7079-Any-luck-with-the-Logitech-Squeezebox-Server-plug-in)). Squeezebox Server is running, but not finding any music. :(

- Dave

[BadIntentions]

same issue, with mysql vanishing?

[ViperGeek]

same issue, with mysql vanishing?

Yes, I still get "MySQL server has gone away" after some amount of time. The actual MySQL plugin continues to run and even my PHP admin session continues to work. It seems to be a timeout with the TCP connection to 127.0.0.1 (internal loopback), although that's just a SWAG.

Another interesting oddity is that, after the full hour+ of indexing, there are ZERO entries in the major tables of the slimserver database, and VOLUME1 is completely idle. One would expect some sort of drive churning as Squeezebox indexed my music.

- Dave

[BadIntentions]

After researching, it appears that its an issue that lots of people are experineince with 7.5.4 and above versions of squeezecenter. I'll look at packaging 7.5.3 for the Javelin (if i can :P)

[ViperGeek]

You're my hero!!!

Even if you can't package a down-rev version of SqueezeCenter, at least I can stop picking at the problem and frustrating myself. Phew!

- Dave

[BadIntentions]

It appears there is some sort of issue with the version of JSON:XS shipped with the plugin. The plugin appears to be a universal version intended for both types of CPU that could be found in this device (there was at one point an Intel Tolopai version available, but Patriot never went forward with it).

I am going to see if i can make the other version i have run...

[ViperGeek]

It appears there is some sort of issue with the version of JSON:XS shipped with the plugin

Interesting. According to CPAN, it looks like the Squeezebox Server plugin includes the latest version:


cpan[1]> i JSON:XS
CPAN: Storable loaded ok (v2.18)
Going to read /root/.cpan/Metadata
Database was generated on Wed, 27 Jul 2011 05:30:09 GMT
Module id = JSON::XS
CPAN_USERID MLEHMANN (Marc Lehmann <schmorp@schmorp.de>)
CPAN_VERSION 2.3
CPAN_FILE M/ML/MLEHMANN/JSON-XS-2.3.tar.gz
UPLOAD_DATE 2010-08-17
MANPAGE JSON::XS - JSON serialising/deserialising, done correctly and fast
INST_FILE /APP/SQUEEZE/perl/local/lib/perl/5.10.0/JSON/XS.pm
INST_VERSION 2.3

Of course, that doesn't mean anything if other components are outdated, or if the latest version is the problem.

BTW, I tried 'test JSON:XS' out of morbid curiosity and realized 'make' doesn't exist in the Javelin/Promise distribution. Is there a make binary compatible with our pretty, white box available?

- Dave

[ViperGeek]

After researching, it appears that its an issue that lots of people are experineince with 7.5.4 and above versions of squeezecenter. I'll look at packaging 7.5.3 for the Javelin (if i can :P)

Have you heard any more about a fix for this issue? I keep the service running in the hopes that the MySQL server won't "go away" in time for the MP3 scan to complete, but I'm still getting:

[11-08-08 17:19:23.1100] Slim::Schema::Storage::throw_exception (82) Error: DBI Exception: DBD::mysql::st execute failed: MySQL server has gone away [for Statement "SELECT me.name, me.value FROM metainformation me WHERE ( name = ? )" with ParamValues: 0='isScanning']

I'm convinced that MySQL isn't actually dying, but rather the previous DB operation never actually started and Slim::Schema::Storage is timing out.

- Dave