Bug 16411 - receiver setup with 7.5.1 r7996 broken
: receiver setup with 7.5.1 r7996 broken
Status: RESOLVED INVALID
Product: SB Receiver
Classification: Unclassified
Component: General
: unspecified
: PC Other
: P1 critical (vote)
: 7.5.1
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-28 14:47 UTC by Ben Klaas
Modified: 2010-08-02 08:53 UTC (History)
2 users (show)

See Also:
Category: Bug


Attachments
console output during setup and failed receiver connection (25.04 KB, text/plain)
2010-07-28 15:02 UTC, Ben Klaas
Details
Successful setup of receiver (33.63 KB, text/plain)
2010-07-29 03:36 UTC, Felix Mueller
Details
failure log with applet.SetupSqueezebox set to DEBUG (90.90 KB, text/plain)
2010-07-29 05:19 UTC, Ben Klaas
Details
another failed setup log, this one without cruft from another player's UDAP broadcast (35.15 KB, text/plain)
2010-07-29 05:28 UTC, Ben Klaas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Klaas 2010-07-28 14:47:03 UTC
I've yet to have a successful receiver setup with controller 7.5.1 r8996

This is not at all the same problem that caused us to push out the controller-only fix last month. This seems to be a problem with receiver connecting to the network, which is pretty black box to me.

I also end up getting an error message that says "We couldn't connect to %s", which is also a bug.

My test steps are to factory reset a receiver by doing a long hold on the front panel button. then i factory reset a controller and go through setup, selecting "Setup Receiver" in the choose player menu. It sees the receiver and appears to start getting it on to the network, but not all the way through. Receiver starts at blinking red light, then it goes solid-- briefly white, and then blue. The controller eventually times out and gives the buggy Problem Connecting message.

QA to reproduce.
Felix, any thoughts on this? I've tried with two different receivers with the same result.
Comment 1 Ben Klaas 2010-07-28 15:02:12 UTC
Created attachment 6921 [details]
console output during setup and failed receiver connection

Choose player and Setup receiver setup steps are flagged in the output
Comment 2 Chris Owens 2010-07-28 15:32:34 UTC
I have confirmed this bug.  

Isn't Jive skipping a step here?  Shouldn't it have already connected itself to the server by the time it tries telling Ray to connect?
Comment 3 Ben Klaas 2010-07-28 19:14:15 UTC
Felix, I'm going to assign to you to start. I'm happy to help out in any way I can.
Comment 4 Ben Klaas 2010-07-28 19:17:33 UTC
Also Chris, I don't think there's a skipped step here. Since the controller got a choose player list (in my case, one populated with other players as well as the "setup receiver" item), I think the server connection was there already.

It's difficult to tell because the log is less helpful than I'd like it to be, but it appears that the receiver is on the network but not connected to the server (hence the blue light).
Comment 5 Felix Mueller 2010-07-29 03:30:20 UTC
Hmm, I am unable to reproduce. I tried many things to deliberately break it, but so far it always succeeded. I went through all three setup types (wireless, wired, bridged) at least three times and it always was ok.

Test setup:

- Jive running 7.5.1 r8996
- AP using channel 6 (same channel we use for the ad-hoc network to add noise)
- Local SS running (susevm)
- Second wired Receiver (not yet setup, also on channel 6, more noise)

Test procedure:

- Factory reset receiver (press and hold button until fast red blinking)
- Factory reset controller (via menu Factory Reset)
- Connect controller to wireless AP
- Connect to existing SN account
- Select receiver to setup
- Wait until setup is done (i.e. controller on home menu, receiver dark white light)
Comment 6 Felix Mueller 2010-07-29 03:36:40 UTC
Created attachment 6922 [details]
Successful setup of receiver
Comment 7 Felix Mueller 2010-07-29 04:04:51 UTC
Looking at Ben's log I can think of two things that might have gone wrong:

- Receiver did not get a valid ip address and is using a self-assigned one
- Router / Switch is confused and did not properly update it's network table

In both cases Controller would fail to talk to Receiver.

Some ideas to try:

- Try rebooting your wireless router and / or the device that runs the DNS server. (I've seen my router getting confused sometimes and then it would just stop serving IP addresses.)

- Delete the Receiver from your SN account. (I don't think that makes a difference, but who knows.)

- Rerun setup with applet.SetupSqueezebox log set to debug, maybe that will reveal something. (After factory reset break out of setup, set the log option, then go back into setup using 'Return to Setup')
Comment 8 Ben Klaas 2010-07-29 05:19:17 UTC
Created attachment 6923 [details]
failure log with applet.SetupSqueezebox set to DEBUG

point at which I pressed go on setting up receiver 16:00:89 is flagged in the console output. Search for string GO
Comment 9 Ben Klaas 2010-07-29 05:19:58 UTC
Also to note, in the last checkin the receiver with mac address ending 16:00:89 shows up in the device list of my dhcp server/wifi router with a valid IP address.
Comment 10 Ben Klaas 2010-07-29 05:28:47 UTC
Created attachment 6924 [details]
another failed setup log, this one without cruft from another player's UDAP broadcast

This output begins at the point where I hit GO on setting up the receiver
Comment 11 Ben Klaas 2010-07-29 06:10:38 UTC
After spending time with Felix on this today, this bug is appearing to be invalid. Turns out I was using old/bad hardware for my tests yesterday (one was a PB1, the other was not but is suspected to be bad). The PB1 hardware did not have firmware that handled the last UUID step correctly.

I've now done setup successfully with three known good SB Receivers.

Chris, I'm pushing this back your way because the last remaining piece of information is trying to understand why yours failed in the same manner mine did yesterday. Is your hardware old?
Comment 12 Chris Owens 2010-07-29 16:02:26 UTC
The Jive hardware was old or the Ray hardware?  I think my Jive is relatively new, but the Ray may be old.  I will try with a newer Ray.
Comment 13 Ben Klaas 2010-07-29 20:41:10 UTC
Retest with newer Ray hardware.

man, what are the odds we both tested with outdated ray hardware...

Chris, if it turns out you were using a pre-MP unit that had firmware too old to correctly get setup, I'd recommend immediately scrapping that unit.
Comment 14 SVN Bot 2010-07-30 07:44:50 UTC
 == Auto-comment from SVN commit #9005 to the jive repo by fmueller ==
 == http://svn.slimdevices.com/jive?view=revision&revision=9005 ==

Bug: 16411 
Description: Fix missing parameter for help text.
Comment 15 Felix Mueller 2010-07-30 07:50:13 UTC
The above is a fix for the issue with "We couldn't connect to %s" where nothing would be displayed for %s.

I only put the fix into 7.6 as it is a minor issue.
Comment 16 Chris Owens 2010-07-30 12:24:51 UTC
I confused myself by eventually making it work on my suspect Ray, but in the end I have to conclude that that was the problem, and threw out the unit.  

On known-MP units, setup seems to work fine.