PDA

View Full Version : 6.5.4 upgrade problem



eschurig
2007-10-03, 12:16
I've been running slimserver 6.5.0 on debian Sarge 3.1 for a long time without problems but decided it was time to upgrade today. I stopped the slimserver and used aptitude to install version 6.5.4. My sources.list file contains deb http://debian.slimdevices.com stable main.

Everything seemed to have gone smooth but when I try to connect to slimserver using my web browser at http://localhost:9000/ I get a "Connection was refused when trying to contact localhost:9000.

ps reveals slimserver running:
4464 ? 00:00:01 slimserver
3110 ? 00:00:00 slimserver_safe

I tried restarting slimserver once using /etc/init.d/slimserver restart.

Logfile information is shown below:

071003 13:39:48 [Note] /usr/sbin/mysqld: Normal shutdown

071003 13:39:49 InnoDB: Starting shutdown...
071003 13:39:53 InnoDB: Shutdown completed; log sequence number 0 90028009
071003 13:39:53 [Note] /usr/sbin/mysqld: Shutdown complete

2007-10-03 13:39:53.3732 ERROR: forceCommit: Trying to commit transactions before DB is initialized!

2007-10-03 13:39:53.6645 ERROR: DBI Connection failed: DBI connect('hostname=127.0.0.1;port=9092;database=sli mserver: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

2007-10-03 13:39:53.6649 ERROR: Backtrace follows:

2007-10-03 13:39:53.6730 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/DBIx/Class/Storage/DBI.pm line 515)
frame 3: DBIx::Class::Storage::DBI::ensure_connected (/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 529)
frame 4: DBIx::Class::Storage::DBI::dbh (/usr/share/perl5/Slim/Schema.pm line 247)
frame 5: (eval) (/usr/share/perl5/Slim/Schema.pm line 247)
frame 6: Slim::Schema::disconnect (/usr/sbin/slimserver line 1005)
frame 7: main::cleanup (/usr/share/perl5/Slim/bootstrap.pm line 300)
frame 8: Slim::bootstrap::sigint (/usr/share/perl5/Slim/bootstrap.pm line 331)
frame 9: Slim::bootstrap::END (/usr/sbin/slimserver line 0)
frame 10: (eval) (/usr/sbin/slimserver line 0)

2007-10-03 13:41:56 slimserver_safe started.
Database error: Duplicate column name 'contributor' at /usr/share/perl5/DBIx/Migration.pm line 115.
2007-10-03 13:42:15.3711 ERROR: forceCommit: Trying to commit transactions before DB is initialized!

2007-10-03 13:42:18 Slimserver died. Restarting.
Database error: Duplicate column name 'contributor' at /usr/share/perl5/DBIx/Migration.pm line 115.
2007-10-03 13:42:31.5055 ERROR: forceCommit: Trying to commit transactions before DB is initialized!

2007-10-03 13:42:34 Slimserver died. Restarting.
Database error: Duplicate column name 'contributor' at /usr/share/perl5/DBIx/Migration.pm line 115.
2007-10-03 13:42:46.0878 ERROR: forceCommit: Trying to commit transactions before DB is initialized!

2007-10-03 13:42:49 Slimserver died. Restarting.
Database error: Duplicate column name 'contributor' at /usr/share/perl5/DBIx/Migration.pm line 115.
2007-10-03 13:43:00.2602 ERROR: forceCommit: Trying to commit transactions before DB is initialized!

These messages continue ......

Please help.

Ed

eschurig
2007-10-03, 21:40
I would just like to add one more question to my issue. If I remember correctly, when slimserver was working there were two instances of mysql running when I looked at the processes. I only see one instance so it seems something might be wrong with mysql. Am I remembering correctly concerning the two instances of mysql?

I'm not sure what to do at this point so I'm going to try to reinstall an older version of slimserver if no one has a suggestion on how to troubleshoot this problem. I already miss my music so I really need to get this working again. Any help would be greatly appreciated.

Ben Sandee
2007-10-04, 06:52
On 10/3/07, eschurig <eschurig.2xw6rb1191439201 (AT) no-mx (DOT) forums.slimdevices.com>
wrote:
>
>
> I've been running slimserver 6.5.0 on debian Sarge 3.1 for a long time
> without problems but decided it was time to upgrade today. I stopped
> the slimserver and used aptitude to install version 6.5.4. My
> sources.list file contains deb http://debian.slimdevices.com stable
> main.


Check the /var/log/slimserver folder for start logs.

If all else fails, I find one thing that can help is to make sure all
processes are stopped and then run this command:

sudo rm -rf /var/cache/slimserver/*

which will remove all MySQL files, which are easily regenerated on a
rescan. If you remove the directory completely then be sure to recreate it
with appropriate permissions.

Ben

reverber
2007-10-04, 08:07
Not sure if this helps, but Debian Stable == Etch, so [it would appear] you are installing Slimserver for Etch onto a Sarge system.

Cody

eschurig
2007-10-04, 09:26
Ben,

Thank you so much, you've made my day. Slimserver is back up. Instead of deleting the files I moved them to a backup directory in case I wanted to look at the log and startup files you talked about. I thought slimserver was stopped but as fast as the files were eliminated by the move, they reappeared and the slimserver was up and running.

I guess a lingering question would be: what did I do wrong to begin with? I did stop slimserver before udating the software. Aptitude seemed to carry on the update smoothly. I don't remember deleting the database files last time I upgraded. Did the database change significantly in a way that would cause slimserver to lock up with the old database files in place?

All that said, thanks again.

eschurig
2007-10-04, 09:37
Cody,

Yes, this was a concern I had. The download notes on the slimserver download page seem to indicate that this is still for Sarge but the stable designation would seem to indicate etch. Since aptitude didn't find any dependency problems I felt like the OS version difference wouldn't make a difference. Maybe this is simply the optimism of a linux novice.

Ben Sandee
2007-10-04, 09:55
On 10/4/07, eschurig <eschurig.2xxtk01191515402 (AT) no-mx (DOT) forums.slimdevices.com>
wrote:
>
> Thank you so much, you've made my day. Slimserver is back up. Instead
> of deleting the files I moved them to a backup directory in case I
> wanted to look at the log and startup files you talked about. I
> thought slimserver was stopped but as fast as the files were eliminated
> by the move, they reappeared and the slimserver was up and running.


Great news!

I guess a lingering question would be: what did I do wrong to begin
> with? I did stop slimserver before udating the software. Aptitude
> seemed to carry on the update smoothly. I don't remember deleting the
> database files last time I upgraded. Did the database change
> significantly in a way that would cause slimserver to lock up with the
> old database files in place?


There's probably nothing that you did wrong. It's quite possible that if
you had upgraded individually from 6.5 to 6.5.1, 6.5.2, 6.5.3 and 6.5.4 that
things might have worked out. I doubt anyone is testing the 6.5.0 to
6.5.4Debian migration. I suspect that if any testing of this is done
at all that
it is from the previous version only (i.e. 6.5.3 to 6.5.4).

I think there's a bit of an assumption that those using Linux are a bit more
technically inclined and are able to solve some problems by themselves or
use the forums to ask for help (as you did). I guess I personally feel
lucky that we get .deb packages at all. :-)

Ben

eschurig
2007-10-04, 12:18
I hadn't really thought about the multiple version jump being a factor in the upgrade but you may be right that it would have gone more smoothly if I had continually upgraded.

I also agree and am grateful for the .deb packages. I recently did my first software installation from source code. Although everything went ok, it sure is a time saver to have a .deb file.

Thanks again.