Last week, I upgraded my SS on Ubuntu from ver. 6.5 to 6.5.1. Since then, I cannot access the server from a web browser.
I "netsat | a" and did not find any application using port 9000.
I ran ps ax | grep slim and saw the following:
woshodin@ubuntu:~$ ps ax | grep slim
5727 ? Ss 0:01 /bin/bash /usr/sbin/slimserver_safe /usr/sbin/slimserver --prefsfile /etc/slimserver/slimserver.pref --logfile /var/log/slimserver/slimserver.log --cachedir /var/cache/slimserver
9555 ? R 0:01 /usr/bin/perl -w /usr/sbin/slimserver --prefsfile /etc/slimserver/slimserver.pref --logfile /var/log/slimserver/slimserver.log --cachedir /var/cache/slimserver
The slimserver.log file contains numerous entries like this:
2007-02-03 12:47:26.4489 ERROR: forceCommit: Trying to commit transactions before DB is initialized!
Database error: Duplicate column name 'contributor' at /usr/share/perl5/DBIx/Migration.pm line 115.
2007-02-03 12:47:40.5259 ERROR: forceCommit: Trying to commit transactions before DB is initialized!
Database error: Duplicate column name 'contributor' at /usr/share/perl5/DBIx/Migration.pm line 115.
2007-02-03 12:47:58.3960 ERROR: forceCommit: Trying to commit transactions before DB is initialized!
Database error: Duplicate column name 'contributor' at /usr/share/perl5/DBIx/Migration.pm line 115.
2007-02-03 12:48:19.4112 ERROR: forceCommit: Trying to commit transactions before DB is initialized!
Database error: Duplicate column name 'contributor' at /usr/share/perl5/DBIx/Migration.pm line 115.
2007-02-03 12:48:35.3610 ERROR: forceCommit: Trying to commit transactions before DB is initialized!
The system monitor does indicate that SS is running. I successfully upgraded my backup SS on my Windows XP laptop. My Squeezeboxes successfully run off that one.
I am a linux novice. I have ran my SS on ubuntu for over a year though.
I appreciate your assistance and guidance.
Results 1 to 3 of 3
-
2007-02-11, 20:07 #1Junior Member
- Join Date
- Feb 2007
- Posts
- 3
No Slimserver Access After 6.5.1 Upgrade on Ubuntu
-
2007-02-11, 22:10 #2Junior Member
- Join Date
- Feb 2007
- Posts
- 3
Forget it
Problem solved. After a week of brain damage, I decided to upgrade to MySQL 5.0 and completely remove and reinstall Slimserver.
This appears to solve the problem.
-
2007-02-12, 08:34 #3Member
- Join Date
- Sep 2006
- Location
- Aarhus, Denmark
- Posts
- 41
Nice you got it up and running again :-)
I upgraded from 6.5 to 6.5.1 on Ubuntu by running
sudo apt-get update
sudo apt-get upgrade
(answered yes to keep my old slimserver startup script)
and everything just worked...
/Kristian

Reply With Quote
