Bugzilla – Bug 13336
Setup DUET fails when upgrading from 7.3x to 7.4
Last modified: 2009-10-05 14:37:51 UTC
If I have a duet attached to 7.3.3 r6038 or 7.4 r5580, then upgrade to 7.4 r7007 the Jive will forget about the attached Ray and fail to connect to SN. Even if I had the pair connected to a local server, the Jive will 'auto' connect to SN and fail I have to factory reset to get Jive to connect (to it's self) to any server.
One for felix to look at.
James: What was the original setup? Standard wired or standard wireless?
Felix: I tried both Standard Wireless and Standard Wired
But SBR keep it's connection to SC or SN and can still be controlled from let's say the webpage? It's only SBC which forgets about the current player it was controlling before the upgrade?
This may be caused by switching back end servers. Controllers are on Prod.SN when using 7.3.x or current 7.4 Upgrading the firmware will force the units on to TEST.sn, where customers may never had put their player in the first place or may not have an account. The controller isn't associated with test.sn so gets into a bad state at this point.
Also, the new firmware will cause the controller to be both Player and Controller (SP standard now) so that may be a contributing factor to this error condition
(In reply to comment #4) > But SBR keep it's connection to SC or SN and can still be controlled from let's > say the webpage? It's only SBC which forgets about the current player it was > controlling before the upgrade? Yes, the Ray is connected to SC and controllable just fine
r7035 appears much better, this time during a 7.3 > 7.4 upgrade the Jive remembered and reconnected to Ray & SC with no issues. Need to test SN as source next
From a Factory Reset state (Jive/Ray on 7.3 firmware) connecting to 7.4 SBS running r7035. Ray upgrades and connects to SBS OK Jive attempts to connect to MySB.com (not SBS) then fails. If I back out of the failed menu, and walk through on device setup, it will complete. But, ray is now on SC and Jive is on MySB.com, so they won't see each other.
Tom: Do you have an idea what's going wrong here? Thanks.
James: Do I understand correct that we have two initial scenarios here: A) Controller and Receiver are previously connected to SN (prod) B) Controller and Receiver are previously connected to local SBS After the update Receiver is still connected to it's previous source, but Controller connects itself to SN (test) due to the auto switching mode? So for the two scenarios this will happen: A) Controller <-> SN (test) / Receiver <-> SN (prod) B) Controller <-> SN (test) / Receiver <-> SBS Scenario A is only a temporal issue as long as we have two SN (prod and test). When we launch Controller will connect to SN (prod) so scenario A should be fine. Scenario B needs some mechanism where we save Controllers previous connection and reinstate it after the update. Tom: Is there a mechanism in the auto-switching code where a connection to the previous server (local SBS) can be forced in the upgrading case?
in short, yes ==================================== James Richardson Lead QA Engineer Logitech INC. SMBU Phone: +1.650.210.5776 Email: james_richardson@logitech.com http://www.logitechsqueezebox.com/ ----- Original Message ----- From: bugs@bugs.slimdevices.com To: jrichardson@slimdevices.com Sent: Monday, August 31, 2009 12:45:11 AM GMT -08:00 US/Canada Pacific Subject: [Bug 13336] Setup DUET fails when upgrading to 7.4 >r5580 https://bugs-archive.lyrion.org/show_bug.cgi?id=13336 Felix Mueller <felix@slimdevices.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |bug_meeting --- Comment #11 from Felix Mueller <felix@slimdevices.com> 2009-08-31 00:45:08 PDT --- James: Do I understand correct that we have two initial scenarios here: A) Controller and Receiver are previously connected to SN (prod) B) Controller and Receiver are previously connected to local SBS After the update Receiver is still connected to it's previous source, but Controller connects itself to SN (test) due to the auto switching mode? So for the two scenarios this will happen: A) Controller <-> SN (test) / Receiver <-> SN (prod) B) Controller <-> SN (test) / Receiver <-> SBS Scenario A is only a temporal issue as long as we have two SN (prod and test). When we launch Controller will connect to SN (prod) so scenario A should be fine. Scenario B needs some mechanism where we save Controllers previous connection and reinstate it after the update. Tom: Is there a mechanism in the auto-switching code where a connection to the previous server (local SBS) can be forced in the upgrading case?
Assigned to me to get more detail.
Felix, not sure if your duet work recently is covering this issue. If not, let's discuss
James: I've (hopefully) improved the Jive / Ray setup process for 7.4 (r7488) which should help the issue you described in comment #9. Please be aware that 7.4 Jive / Ray setup to a local SC only works if there is no path to SN at all. It is my understanding that if SN is available Jive and Ray always connect to SN (without option for the user to select SC). I believe that is a marketing decision to get people to register on SN. For the other issue where an upgrade from 7.3.x would make Jive and Ray end up on different servers, i.e. SC and SN, I'd like you to retest so we know where we stand with all the recent changes. Thanks Felix
Which will be infuriating to people who set up the SC first, and enter their SN id/password the easy way. They then have to do it again with the scroll wheel, which is enough to make you want to return the beast!
I'm still running into a bit if a problem with the Jive/Ray setup. But I think I have to wait for work on bug 14021 and 12207 to finish before I can continue Marc: bug 13801 covers your comment 16
Changing summary to properly reflect the limited scope of this bug instance
This appears to be working with latest firmware, however there is an error in our test setup that needs to be fixed before we can validate all setup paths.
Closing this bug as it's not specific to a single error. new bugs specific to setup scenarios will be opened as they are found.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.