Bugzilla – Bug 3968
Unable to connect to SlimServer.
Last modified: 2008-09-15 14:39:24 UTC
After upgrading to the latest nightly builds, I am no longer able to launch the SlimServer application. The only change on the system is the slimserver packge. Reverting to Debian's Slimserver 6.3.0 package resolves the problem. I am using Debian's Testing Distribution. I have attached one cycle of log error messages below. Thanks, David 060818 18:33:16 [ERROR] Error message file '/usr/share/slimserver/MySQL/errmsg.sys' had only 463 error messages, but it should contain at least 466 error messages. Check that the above file is the right version for this program! 060818 18:33:16 [ERROR] Aborting 2006-08-18 18:33:46.9813 ERROR: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver:mysql_socket=/var/cache/slimserver/slimserver-mysql.sock','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 624 2006-08-18 18:33:46.9817 ERROR: Backtrace follows: 2006-08-18 18:33:46.9825 Backtrace: frame 0: Slim::Schema::Storage::throw_exception (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 630) frame 1: DBIx::Class::Storage::DBI::_connect (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 588) frame 2: DBIx::Class::Storage::DBI::_populate_dbh (/usr/share/perl5/Slim/Schema/Storage.pm line 32) frame 3: Slim::Schema::Storage::_populate_dbh (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 515) frame 4: DBIx::Class::Storage::DBI::ensure_connected (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 529) frame 5: DBIx::Class::Storage::DBI::dbh (/usr/share/perl5/Slim/Schema.pm line 118) frame 6: Slim::Schema::init (/usr/share/perl5/Slim/Music/Info.pm line 61) frame 7: Slim::Music::Info::init (/usr/sbin/slimserver line 380) frame 8: main::init (/usr/sbin/slimserver line 454) frame 9: main::main (/usr/sbin/slimserver line 1053) 2006-08-18 18:33:46.9832 ERROR: Couldn't connect to database! Fatal error: [Transport endpoint is not connected] Exiting! 2006-08-18 18:33:46.9836 Backtrace: frame 0: Slim::Schema::init (/usr/share/perl5/Slim/Music/Info.pm line 61) frame 1: Slim::Music::Info::init (/usr/sbin/slimserver line 380) frame 2: main::init (/usr/sbin/slimserver line 454) frame 3: main::main (/usr/sbin/slimserver line 1053) 2006-08-18 18:33:46.9843 ERROR: forceCommit: Trying to commit transactions before DB is initialized! 2006-08-18 18:33:46.9894 ERROR: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=slimserver:mysql_socket=/var/cache/slimserver/slimserver-mysql.sock','slimserver',...) failed: Can't connect to MySQL server on '127.0.0.1' (111) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 624 2006-08-18 18:33:46.9897 ERROR: Backtrace follows: 2006-08-18 18:33:46.9905 Backtrace: frame 0: Slim::Schema::Storage::throw_exception (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 630) frame 1: DBIx::Class::Storage::DBI::_connect (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 588) frame 2: DBIx::Class::Storage::DBI::_populate_dbh (/usr/share/perl5/Slim/Schema/Storage.pm line 32) frame 3: Slim::Schema::Storage::_populate_dbh (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 515) frame 4: DBIx::Class::Storage::DBI::ensure_connected (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 529) frame 5: DBIx::Class::Storage::DBI::dbh (/usr/share/perl5/Slim/Schema.pm line 242) frame 6: (eval) (/usr/share/perl5/Slim/Schema.pm line 242) frame 7: Slim::Schema::disconnect (/usr/sbin/slimserver line 1019) frame 8: main::cleanup (/usr/share/perl5/Slim/bootstrap.pm line 259) frame 9: Slim::bootstrap::sigint (/usr/share/perl5/Slim/bootstrap.pm line 290) frame 10: Slim::bootstrap::END (/usr/sbin/slimserver line 0) frame 11: (eval) (/usr/sbin/slimserver line 0) 060818 18:33:53 [ERROR] Error message file '/usr/share/slimserver/MySQL/errmsg.sys' had only 463 error messages, but it should contain at least 466 error messages. Check that the above file is the right version for this program! 060818 18:33:53 [ERROR] Aborting
1. Please do not pre-set target. 2. This is basically a support issue for the moment, and as there are not a huge number of users unable to connect, not appropriate for severity level. have a look at this thread. http://forums.slimdevices.com/showthread.php?t=24225 make sure you have an up to date version of mysql
*** Bug 3989 has been marked as a duplicate of this bug. ***
Further to my comments about a workaround on bug 3989, just holding the mysql-server package at 5.0.22 isn't enough -- slimserver starts and appears to run, but crashes with a database error the first time you try to play anything. To get it working, you need to keep the version for all the mysql packages at 5.0.22: $ cat /etc/apt/preferences Package: slimserver Pin: origin slimdevices Pin-Priority: 1000 Package: mysql-server-5.0 Pin: version 5.0.22 Pin-Priority: 1001 Package: mysql-client-5.0 Pin: version 5.0.22 Pin-Priority: 1001 Package: mysql-common Pin: version 5.0.22 Pin-Priority: 1001 Package: libmysqlclient15off Pin: version 5.0.22 Pin-Priority: 1001 Package: libmysqlclient15-dev Pin: version 5.0.22 Pin-Priority: 1001
So what is our policy on this, Dan? Do we support only the mysql that we package? Should we put giant warnings in all of the unix packages that you must use it with a specific mysql version?
Chris - for Debian, we reuse the system MySQL. There's some changes here which I need to make in order to make it a smooth transition. If the version is not the same as the errmsg that we ship.
Fixed in change 9504 & change 9508