Bugzilla – Bug 3466
Web Interface only shows Squeezebox
Last modified: 2008-09-15 14:39:24 UTC
Slimserver was working fine under Ubuntu Breezy. When upgraded to Dapper, the web interface only shows the Squeezebox display, that is only the right hand side of the screen. The left hand side, where the server interface should display, is blank. The same result occurs on another PC, running a clean install of Unbuntu Dapper and slimserver 6.5b1. The slimserver log reports: "1998 ERROR: plugin error - Clients: plugin not found"
Now mainly resolved. By starting the slimserver from the command line the web interface could then be accessed. Using the debug mode "slimserver --d_server" produced a message "Your data source needs to be configured. Please open your web browser go to the following URL, and click on the "Server Settings" link." However, when rebuilding the database, (I had selected "clear library and rescan everything") the following appeared in the server messages: ERROR: executeSQLFile: Couldn't open file [/usr/sbin/SQL/mysql/schema_clear.sql] : No such file or directory I copied the SQL directory under /usr/sbin and it then worked. Then I used softsqueeze to play a track and half way through the server messages reported:- 2006-05-30 20:32:51.9420 Got sigint. 2006-05-30 20:32:51.9423 SlimServer cleaning up. 2006-05-30 20:32:51.9847 Got to the END. [1]- Killed slimserver --d_server [2]+ Killed slimserver stop Now restarted and rebuilding database.
I'm still seeing this on the latest 6.5b1 package on Dapper. As far as I can tell, something has broken in the mysql db support, as I'm seeing the following in the log: 060529 12:56:07 InnoDB: Started; log sequence number 0 43634 /usr/sbin/mysqld: ready for connections. Version: '4.1.15-Debian_1ubuntu5' socket: '/var/cache/slimserver/slimserver-mysql.sock' port: 9092 Source distribution 2006-05-29 12:56:10.5199 Your data source needs to be configured. Please open your web browser, 2006-05-29 12:56:10.5201 go to the following URL, and click on the "Server Settings" link. 2006-05-29 12:56:10.5202 The URL to access SlimServer is now: http://ender:9000/ 2006-05-29 12:56:12.0135 Use of uninitialized value in numeric lt (<) at /usr/share/perl5/Slim/Player/Player.pm line 174. 2006-05-29 12:56:12.0137 Use of uninitialized value in array slice at /usr/share/perl5/Slim/Player/Player.pm line 175. 2006-05-29 12:56:12.0138 Use of uninitialized value in array slice at /usr/share/perl5/Slim/Player/Player.pm line 175. 060529 12:56:46 [Note] /usr/sbin/mysqld: Normal shutdown 060529 12:56:46 InnoDB: Starting shutdown... DBIx::Class::Storage::DBI::dbh(): 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 407 InnoDB: Unable to lock ./ibdata1, error: 11 InnoDB: Check that you do not already have another mysqld process InnoDB: using the same InnoDB data or log files. 060529 12:56:49 InnoDB: Retrying to lock the first data file 060529 12:56:49 InnoDB: Shutdown completed; log sequence number 0 128421 060529 12:56:49 [Note] /usr/sbin/mysqld: Shutdown complete
This summary doesn't realy reflect what is going on. the server is dying, not failing to render the web pages. The "client plugin not found" thing is reported elsewhere (bug 3477), and I am not sure why the mysqld crash in comment 2 was felt to be related. Michael, did you manage to rebuild? Jeremy, check your running processes for a rogue copy of mysqld and kill it.
There have been a lot of changes since this report was filed regarding the start/stopping of MySQL by SlimServer. My latest testing on Ubuntu 5.10 (and 6.x) indicates everything is fine. Please reopen, or create a new report if you have a specific case you can reproduce using the latest nightly of 6.5 Thanks