Release notes for Excito B3 software version 2.3.1

[johannes]

This is a new minor upgrade. The upgrade is available only as a software upgrade.

How to upgrade
To upgrade a running system, make sure you don't have any activities running such as uploads, downloads, print jobs etc. Then log in as admin in web-ui. Choose "Settings" menu entry. Choose "Software update" in the sub menu.
Note: Make sure to keep the "hotfix" option checked (see below). Press the "Update system" button.

Since the update service depends on root access to the MySQL database, if you have changed the default MySQL password the update will fail. If it has been changed, run the update from the command line. Default options should be ok, but you need to provide your MySQL root password.

New features and major changes
* Squeezebox server update to 7.6.1
* Some security updates from debian
* Various bug fixes

Note regarding the hotfix
For this update to complete, the hotfix is required to run. There are two options:

1) Keep the hotfix option enabled during upgrade
2) Update from command line interface. As root, run:

Code: Select all

change_distribution elvin
apt-get -c /etc/apt/bubba-apt.conf -y update
apt-get -c /etc/apt/bubba-apt.conf -y dist-upgrade

The hotfix is not required when updating from the command line.

Note - new updater
A major part of this update is a new software update service. When updating the update service, strange things can happen, so:
* If the update doesn't go all the way but hangs just before it should be finished (99 or 100%) this is normal. This is in the transition to the new updater logic. Just wait a few minutes and then reload the page.
* After the update - restart your B3.
* The updater might look like it hangs, it doesn't'! Please don't reload the page, be patient, it starts again.

[AzP]

Yaaay! Every new update is so much fun, even though it's a small one

[johannes]

Also note two consequences of this update:

• sources.list will be reset since we have modified the structure
• hotfixes will always run on the new updater system. If you wish to avoid hotfixes in the future, run updates from the command line

[albert]

hi Johannes,

I had to do the update manually, and it seemed to have updated nicely. I noticed that the squeezecenter client (SoftSqueeze) wasn't able to connect so I checked the logs /var/log/squeezecenter/server.log and found lots of entries, like this:
[11-10-26 19:52:21.1899] Carp::Clan::__ANON__ (225) Warning: Carp::Clan::__ANON__(): DBI Connection failed: DBI connect('database=squeezecenter;hostname=;port=','squeezecenter',...) failed: Access denied for user 'squeezecenter'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1176
[11-10-26 19:52:21.1936] Slim::Schema::forceCommit (1997) Warning: Trying to commit transactions before DB is initialized!
2011-10-26 19:52:21 SqueezeCenter died. Restarting.

It looks like the database can't be contacted. I don't mind reinitializing the database, but before I screw up lots of things, what can I do?

Cheers,

Albert

[Binkem]

I get the following when trying to update using the command-line

insserv: warning: script 'sabnzbdplus' missing LSB tags and overrides
insserv: There is a loop between service minidlna and sabnzbdplus if stopped
insserv: loop involving service sabnzbdplus at depth 2
insserv: loop involving service minidlna at depth 1
insserv: Stopping sabnzbdplus depends on minidlna and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing squeezecenter (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
apache2.2-common
apache2-mpm-prefork
libapache2-mod-php5
bubba-frontend
bubba
bubba-backend
squeezecenter

This was because of my sabnzbd script not being correct. I removed it from /erc/init.d and now the update seems to work

[albert]

Well,

I seem to have fixed it myself (the squeezecenter startup problem, that is).

I stoppend squeezecenter with the webinterface (services).
Then I removed squeezecenter, including the mysql database that belongs to squeezecenter:

apt-get remove --purge squeezecenter

(check that you remove the mysql database as well by choosing the right options on the questions),
when passwords are asked, just press return. Then do

apt-get update

And reinstall (for a second time!) squeezecenter:

apt-get install squeezecenter

Again, when asked for passwords, just press enter.

Now, the only logs in the /var/log/squeezecenter/server.log file is:

root@b3:/var/log/squeezecenter# cat server.log
2011-10-26 20:37:59 squeezecenter_safe started.
[11-10-26 20:38:07.2026] main::init (350) Starting Squeezebox Server (v7.6.1, rTRUNK, UNKNOWN) perl 5.010001
[11-10-26 20:38:11.5143] Slim::Utils::SQLiteHelper::init (61) Warning: DBD::SQLite version 1.34 or higher required
2011-10-26 20:38:11 SqueezeCenter died. Restarting.
[11-10-26 20:38:19.7032] main::init (350) Starting Squeezebox Server (v7.6.1, rTRUNK, UNKNOWN) perl 5.010001
[11-10-26 20:38:23.9323] Slim::Utils::Misc::msg (1236) Warning: [20:38:23.9300] Class::C3::Componentised::load_components(): Use of DBIx::Class::UTF8Columns is strongly discouraged. See documentation of DBIx::Class::UTF8Columns for more info
[11-10-26 20:38:29.3095] main::checkDataSource (1050) Warning: Schema updated or no tracks in the database, initiating scan.

And I can connect to the server now. It takes quite a while to rebuild the database (as it is about 50 GB of music files), but I just let it run.

Albert

[johannes]

Ok, thanks for this information. If anyone else sees the squeecebox server issue please let us know.

[ahoff]

Följande paket har beroenden som inte kan tillfredsställas:
squeezecenter : Beroende av: libjson-xs-perl (>= 2.300) men 2.290-1 kommer att installeras
E: Trasiga paket

[johannes]

Hi Åke,

You ran using command line, right? What commands did you use? Towards what repo did you update?

Thanks

[ryz]

Ok, thanks for this information. If anyone else sees the squeecebox server issue please let us know.

Problems with squeecebox might come from the fact that the script /usr/sbin/squeezecenter_safe is broken. At least it is on my B2. This is the script that is started and stopped from the init script. The problem is that when the init script send a stop signal to the squeezecenter_safe script the squeezecenter_safe script will forward that to the real squeezenter daemon and then quit immediately without waiting for the daemon to actually stop. This make the init script believe that the daemon is stopped when it is not. So if you tell the init script to do a restart of squeezcenter it most likely will start an new daemon before the old one has finished.

The function

Code: Select all

function clean_up {
  # Kill the SqueezeCenter daemon if it is running
  kill $SLIMPID
  echo `date "+%F %H:%M:%S"` "squeezecenter_safe stopped." >> /var/log/squeezecenter/server.log
  exit
}

should be changed to

Code: Select all

function clean_up {
  # Kill the SqueezeCenter daemon if it is running
  kill $SLIMPID
  echo `date "+%F %H:%M:%S"` "squeezecenter_safe stopped." >> /var/log/squeezecenter/server.log
  wait $SLIMPID
  exit
}

[ahoff]

Hi Åke,

You ran using command line, right? What commands did you use? Towards what repo did you update?

Thanks

First I did:

Code: Select all

change_distribution elvin
apt-get -c /etc/apt/bubba-apt.conf -y update
apt-get -c /etc/apt/bubba-apt.conf -y dist-upgrade

Then I did like albert:

Code: Select all

apt-get remove --purge squeezecenter
apt-get update
apt-get install squeezecenter

I might mention that I'm running a B2.

[johannes]

Ah, this is a B3-only update still, updating from the 2.4-RC1 installer for B2 is unsupported and untested, and might not work properly (it may actually downgrades some stuff). Sorry, should have emphasized that.

[DanielM]

[*]hotfixes will always run on the new updater system. If you wish to avoid hotfixes in the future, run updates from the command line[/list]

Does this mean that I don't get the hotfixes if I run from the command line? I always do that, mostly because I like control over what's happening, but also because "apt-get update && apt-get dist-upgrade" fits good with my fingers Anyway, what exactly do we mean by "hotfixes" here?

/Daniel

[Binkem]

I'm having a lot of problems with my squeezeserver since the last update. It doesn't seem to want to communicate with my squeezebox radio, remote of Android App anymore. If I play music to them using the web-app (bubba:9000) my squeezebox radio and receiver play the music, but I cannot access the collecion in any way and the web-app doesn't recognise my players. It seems that squeezecenter cannot use one or more of its posts?

My server.log:

2011-10-27 21:01:52 squeezecenter_safe started.
[11-10-27 21:02:01.2777] main::init (350) Starting Squeezebox Server (v7.6.1, rTRUNK, UNKNOWN) perl 5.010001
[11-10-27 21:02:02.1937] Slim::Utils::Misc::msg (1236) Warning: [21:02:02.1915] Class::C3::Componentised::load_components(): Use of DBIx::Class::UTF8Columns is strongly discouraged. See documentation of DBIx::Class::UTF8Columns for more info
[11-10-27 21:02:09.6251] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:02:09.6290] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:02:10.0473] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:02:32.1989] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:02:39.7257] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:02:39.7291] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:03:14.7694] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:03:14.7727] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:03:16.2294] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:03:44.8583] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:03:44.8624] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:04:14.9671] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:04:14.9703] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:04:45.0596] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:04:45.0629] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:05:15.1511] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:05:15.1545] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:05:45.2507] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:05:45.2539] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:06:15.3337] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:06:15.3374] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:06:45.4260] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:06:45.4293] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:07:13.9038] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:07:14.8252] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:07:15.5012] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:07:15.5045] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!
[11-10-27 21:07:50.5692] Slim::Control::Request::execute (1883) Error: While trying to run function coderef [Slim::Control::Queries::serverstatusQuery]: [Can't locate object method "_subq_count_select" via package "Slim::Schema::Storage" at /usr/share/squeezecenter/lib/DBIx/Class/ResultSet.pm line 1280.
]
[11-10-27 21:07:50.5725] Slim::Web::JSONRPC::requestMethod (413) Request failed with error: Bad dispatch!

[johannes]

Anyway, what exactly do we mean by "hotfixes" here?

Yes, good question. This is "Hotfix" to Excito:

Before updating, if hotfix is enabled, some information is gathered and stored on our server. This information is:
- mac adress, IP adresses
- raid/lvm configuration
- used disk space
- package versions of some selected packagages
- Bx serial number

The meaning is that we could use this information for error-hunting. As of yet we have never needed to though.

Furthermore, the hotfix allows a script to download from our server (of course after key authentication check) and run on your Bx, before the actual apt-get update stuff. The meaning of this is to give us a possibility to fix a system so broken that the updater won't run. For instance, the prior update (2.3) unveiled a bug in our updater that made the updater not finish off properly on some systems. Hence, now there is a hotfix (v.2.3.1) that restores the system to a good state before upgrading.

Running from command line, normally the hotfixes aren't required (that kind of fixing is often easilly done
manually on the command line) and if they ever would be those scripts can be downloaded and run manually.

Hope this made sense.