Bugzilla – Bug 15292
No or wrong fault handling by Radio for loss of MYSB connection
Last modified: 2010-02-06 03:04:19 UTC
When using the Radio with MySqueezebox.com (European Server: Frankfurt/Germany), the MYSB connection is lost at least once per day. This might be related to the fact that most private internet users in Europe are using a DSL connection with dynamic IP which is usually forced to reconnect at least once per day. Note that if I talk of a connection loss in the following, I don't mean the loss of internet or local network connection, but the obvious loss of the connection between Radio and MYSB. The behavior described here happens while the the LAN and internet connection are perfectly valid and when MYSB is fully available (via PC and SB Classic). Also the MYSB displays the Radio as connected and doesn't show any error message or warning when e.g. changing the alarm setup. In case of such an MYSB connection problem, the Radio behaves erratic as it obviously doesn't realize the situation or at least doesn't handle it correctly. In the diagnosis screen it shows that it is connected to and registered with MYSB (with IP address), but most of the MYSB related buttons and menu items don't work any more. E.g if pressing the alarm button, just a sound is played, but nothing happens. Same for most menu items. There are only a few items (e.g. the Last.fm application) which can be used to exit this state. Even worse, when an alarm happens in this state, the alarm menu is not shown and the duration of the alarm seems to be random. Sometimes it plays for a few minutes, sometimes it plays only for a few seconds, at least one time it played so short that it was more of a short clicking. Sometimes the alarm continues for a while, when you press the knob, sometimes it doesn't. Again, the only way to exit this state is going back to the main menu (which usually works) and then e.g. selection Last.fm (I think that normal internet radio works as well, but I settled to use Last.fm). Needless to say that this renders the alarm function via MYSB more or less useless in large parts of Europe. The only thing close to a workaround currently is to configure the DSL reconnection to a time before going to bed but after getting up - if the provides supports this. Then again, even then providers tend to do maintenance at night, so this doesn't work reliably either. Tested with 7.4.1 v7915. PLEASE don't shift this serious issue to 8.0.0 or declare it a duplicate of some unrelated network issue. This is a serious design flaw of the Radio (and/or MYSB) and ruins the reputation of the whole brand in Europe.
Does the radio get a valid local address after one of this outages? Can it be 'pinged' from another device on the local net? Is there a forum thread on this problem that you could add to the 'URL' field of the bug for easy review of comments?
>Does the radio get a valid local address after one of this outages? >Can it be 'pinged' from another device on the local net? > I tried to make it as clear as possible, but again: the Radio's local IP is not changed, the local network has no issues at all. Anyway, once again: if I tell my router to disconnect the VDSL connection, wait a few seconds, then reconnect, it gets another IP address by my ISP. This doesn't affect the local IP addresses of course. After this manual reconnect (as well as after the forced reconnects by my ISP), there's about a 90% chance that the Squeezebox enters the described error state. I can ping the Radio in this state with the same local IP it always gets from the router (DHCP via MAC-address). Also MYSB recognizes the router's new IP after a while when I refresh the browser window. Then I can even remote control the Radio via MYSB and the Radio plays internet Radio and all. So the MYSB connection is obviously not completely lost. Still, the Radio's caught in some error state since I can't access the alarm menu etc. as described above. Note that this doesn't happen at every single reconnect, but if the reconnect needs a few seconds, the chance is very, very high. Is there a forum thread on this problem that you could add to the 'URL' field of the bug for easy review of comments? > AFAIK, there is no common thread that focuses _only_ on this problem, since there are obviously much more alarm related issues. Also there are more related postings in the German forum.(In reply to comment #1) > Does the radio get a valid local address after one of this outages? Can it be > 'pinged' from another device on the local net? > > Is there a forum thread on this problem that you could add to the 'URL' field > of the bug for easy review of comments?
There is a theory that this may have to do with the recent load issues experienced by the european mysb data center. QA to try to get a reproducible case.
(In reply to comment #3) > There is a theory that this may have to do with the recent load issues > experienced by the european mysb data center. > It happened about every days since I bought the Radio over two months ago. So I can't see any relation to the "load issues" which only began to happen in late November. Besides, in the latter case, the Radio simply can't connect (blue WLAN icon, sometimes there is a error description, sometimes there isn't). The case described here however differs in that both sides think that there is a connection, and it even partly works (e.g. remote control via server), but still the Radio itself is unable to use the MYSB connection correctly (e.g. to display the alarm setup).
One link to a related post in the board (Deutsch) is this one: http://forums.slimdevices.com/showthread.php?p=505747#post505747
I can confirm that I saw the same at least twice in the beginning of having a SB-Radio (back in the beginning of november when there weren't load problems).
Ben has been working on this bug as part of his large array of alarm fixes. QA needs to test his changes.
I would guess that this is probably a duplicate of bug 15444, which is now fixed.
This bug has been fixed in 7.4.2 as some of the changes to improve reliability of Radio connection to MySB.com. Includes bug 15444, bug 15485, and bug 11455, which have all been fixed. All of these fixes are in the 7.4.2 and 7.5 beta releases. I would suggest updating to 7.4.2 to verify that your issues have been resolved. *** This bug has been marked as a duplicate of bug 15444 ***
Also, code on MySqueezebox.com has been updated to reflect fixes for these issues. Please report back if there are still issues.
(In reply to comment #10) > Also, code on MySqueezebox.com has been updated to reflect fixes for these > issues. Please report back if there are still issues. Indeed I didn't observe any of the connection losses as described above in the last few days. Since my Radio is still on 7.4.1 v7915, I already began to wonder if something was fixed on the server side or if there was a "silent" update on the Radio side. So the changes on the server side improved the situation indeed. It might be a bit early to say that the issue is fixed completely, but at least there IS an improvement. Thanks for looking into this.