Cannot connect to database!

[Xhorder]

Help,

I upgraded from 7.5 to 7.5.1 and now it won't start. I get the following error in the log:

[10-07-09 18:21:47.8367] main::init (323) Starting Squeezebox Server (v7.5.1, r30836, Tue Jun 1 06:57:07 MDT 2010) perl 5.010001
[10-07-09 18:22:18.0553] Slim::Utils::MySQLHelper::createSystemTables (506) FATAL: Couldn't connect to database: [Can't connect to local MySQL server through socket '/var/lib/squeezeboxserver/cache/squeezebox-mysql.sock' (2)]

There don't seem to be any errors in mysql-log-errors.txt in var/lib/squeezeboxserver/cache.

How can I troubleshoot this? How do I get a more detailed error log?

I'm running Mandriva 2010.1, kernel 2.6.33, perl 5.10.1

thanks

[Xhorder]

Replying to myself.

Nothing I do helps. (and the wiki seems horribly outdated BTW)

--I've uninstalled and reinstalled from scratch: no change.

--I've tried running from the command line and get a different error!:

[csh@localhost libexec]$ ./squeezeboxserver --d_server --d_info --d_mysql
modules.conf not found at /usr/lib/perl5/vendor_perl/Slim/bootstrap.pm line 387.
BEGIN failed--compilation aborted at ./squeezeboxserver line 135.

--I've tried everything to enable more debugging messages to no avail. How do I get more detailed logs!!???

I'm quitting banging my head against the wall for today... Very unhappy and frustrated.

[AnotherTribe]

Sounds like an old instance of SBS may be grabbing the port (?). After removing did you check for any running processes related to SBS? Did you bounce the box before reinstalling just to make sure nothing is lurking in the background? Just throwing a few ideas out there to assist.

[Xhorder]

Thanks for the reply, but nothing else is running.

A few, hopefully simpler, questions that I hope someone can answer:

- Is server.prefs supposed to be an empty file? doesn't see right

- What is the password for user "squeezeboxserver"?

- Is there some config file where I can put debug switches that will actually work when doing a "service squeezeboxserver start"?

I've been running squeezebox server for years and years and I've NEVER has such problems as I am now. Anyway... PLEASE HELP!! I'm desperate to get my squeezebox back!

[Xhorder]

replying to myself again

I forgot to mention, I get the following errors when doing a "service squeezeboxserver start":


[Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
100711 12:26:00 [Warning] '--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.
100711 12:26:00 [Warning] '--default-collation' is deprecated and will be removed in a future release. Please use '--collation-server' instead.

[AnotherTribe]

Thanks for the reply, but nothing else is running.

A few, hopefully simpler, questions that I hope someone can answer:

- Is server.prefs supposed to be an empty file? doesn't see right

- What is the password for user "squeezeboxserver"?

- Is there some config file where I can put debug switches that will actually work when doing a "service squeezeboxserver start"?

I've been running squeezebox server for years and years and I've NEVER has such problems as I am now. Anyway... PLEASE HELP!! I'm desperate to get my squeezebox back!

My server.prefs is populated.

I do not know the password for the user 'squeezebozserver', never had the need to know it.

When you uninstalled did you also remove all config files etc before attempting a reinstall? I am not familiar enough with Mandriva, Debian has a 'purge' option for it's package manager. I still would do a manual search and rename or remove any left over config files and/or directories. You will have to of course need reconfigure from scratch, reinstall plugins etc.

[Xhorder]

Well, I think it's gotta be some screwy Mandriva thing...

I just nuked the root directory, installed Mandriva 2010.1 from scratch, followed by sbs 7.5.1

Exact same results

[pfarrell]

> Well, I think it's gotta be some screwy Mandriva thing...
>
> I just nuked the root directory, installed Mandriva 2010.1 from
> scratch, followed by sbs 7.5.1

I ran my SBS on mandriva for years. Then they "improved" something
and I could never get the update to work. This was years ago, so sorry
that I don't remember what mandriva version and what SBS version was.

I moved to pure Debian and have been on it for years. Its wonderful and
since I run Ubuntu on my main desktop and laptop, all the tools I care
about are there.

I also like that Debian is more stable, releases are much less frequent.

I keep my server in the basement and I don't want to touch it. It runs
for months untouched.

I just SSH in and do a "apt-get update" cycle periodically


--
Pat Farrell
http://www.pfarrell.com/

[Xhorder]

Well, I got it running by using the tarball version instead of the rpm. The rpm package I guess is not compatible with Mandriva 2010.1

I agree that Mandriva used to be better than it is now... I've just used it for so long I'm hesitant to change.

[pfarrell]

> I agree that Mandriva used to be better than it is now... I've just
> used it for so long I'm hesitant to change.

I completely understand. The good thing about having zillions of distros
is that you can pick the one you like.

I stayed with Mandriva at least a year for the same hesitant topic

--
Pat Farrell
http://www.pfarrell.com/

[AndyF]

I've also done a clean install of Mandriva 2010.1 and got the same unable to connect to MySQL daemon error message.

I've found a solution. Edit the following file:

/usr/share/squeezeboxserver/MySQL/my.tt

and change the following line (which comes immediately below the line "[mysqld]"):

innodb

to:

plugin-load=ha_innodb.so


Then start the squeezeboxserver service and it should be able to start the mysqld daemon.

I guess this problem has occurred because Mandriva are using a newer version of mysql. So I expect this is going to hit users of a lot of other distros as the new versions of those distros are released.

Note that I have no knowledge of the workings of MySQL, I just got lucky. There is probably a more correct solution but this works for me.

[QuasiGoreng]

I also encountered the same problem after upgrading Mandriva to 2010.1.

Solved this by using an external MySQL instance, something that I was wanting to do sometime anyway.

Here's one howto:
wiki.slimdevices.com/index.php/Using_an_existing_MySQL_instance