Bug 16645 - Blue Icon while continuing to play
: Blue Icon while continuing to play
Status: RESOLVED DUPLICATE of bug 16617
Product: SB Radio
Classification: Unclassified
Component: Connectivity (Server)
: Include FW version in comment
: PC Windows (legacy)
: -- normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-01 09:29 UTC by Ryan
Modified: 2011-03-16 04:47 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments
Log from Radio in Comment #3 (248.40 KB, text/plain)
2010-11-17 10:39 UTC, Mickey Gee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan 2010-11-01 09:29:28 UTC
fw 9009

The player was setup wifi connected to MSB.com and playing an internet radio stream. It had been running for quite awhile when the connection icon switched to blue.

The player was performing local control of itself.

At MSB.com the remote appeared to but could not actually control the unit.

Logging into MSB.com as an admin. checking status of the player the player indicated connected and the controller was not. 

This may be related to a local server having become available after the player was setup playing on MSB.com. 

This may be related to bug 16575 and bug 16258
Comment 1 Mickey Gee 2010-11-02 10:40:39 UTC

*** This bug has been marked as a duplicate of bug 16617 ***
Comment 2 Mickey Gee 2010-11-02 10:41:44 UTC
Ooops ... not resolved yet.
Comment 3 Mickey Gee 2010-11-17 10:36:59 UTC
I have a wired Baby with r9218. I started it playing before the weekend, and afterwards it had a blue icon. Checking Diagnostics screen it confirms that it is wired and is connected to MySB.com. Checking MySB.com says it is connected too.

In this state, I choose Internet Radio and it prompts for a Squeezebox Server instance to switch to and never prompts for reconnection to MySB.com -- probably because it thinks it's connected.

This is possibly the same as Ryan's situtation, so I'm including it here. Adding logs, but not sure they're helpful.
Comment 4 Mickey Gee 2010-11-17 10:39:23 UTC
Created attachment 7039 [details]
Log from Radio in Comment #3
Comment 5 Alan Young 2010-11-17 23:02:33 UTC
This is almost certainly a duplicate of bug 16617. 

For an extended period the player could not connect to SN, neither SlimProto nor Comet. Finally, at 00:05:15 it connected but then got told to go away:

Nov 16 00:05:15 squeezeplay: INFO   net.slimproto - SlimProto.lua:577 connect to baby.squeezenetwork.com (184.73.179.154)
Nov 16 00:05:15 squeezeplay: INFO   net.slimproto - SlimProto.lua:135 Send HELO: reconnect-bit=0 bytesReceived(H,L)=0,0
Nov 16 00:05:23 squeezeplay: WARN   net.thread - NetworkThread.lua:146 network thread timeout for Task(SocketHttp {mysqueezebox.com_Chunked}(W))
Nov 16 00:05:23 squeezeplay: ERROR  net.http - SocketHttp.lua:373 SocketHttp {mysqueezebox.com_Chunked}:t_sendRequest.pump: inactivity timeout
Nov 16 00:05:23 squeezeplay: stack traceback:
Nov 16 00:05:23 squeezeplay: 	/usr/share/jive/jive/net/SocketHttp.lua:373: in function 'pump'
Nov 16 00:05:23 squeezeplay: 	/usr/share/jive/jive/net/SocketTcp.lua:200: in function 'writePump'
Nov 16 00:05:23 squeezeplay: 	/usr/share/jive/jive/net/Socket.lua:186: in function </usr/share/jive/jive/net/Socket.lua:184>
Nov 16 00:05:23 squeezeplay: INFO   net.comet - Comet.lua:627 Comet {mysqueezebox.com}: _handshake error: inactivity timeout
Nov 16 00:05:23 squeezeplay: INFO   net.comet - Comet.lua:997 Comet {mysqueezebox.com}: handleAdvice state=CONNECTING
Nov 16 00:05:23 squeezeplay: INFO   squeezebox.server - SlimServer.lua:734 disconnected mysqueezebox.com idleTimeoutTriggered: nil
Nov 16 00:05:23 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:367 notify_serverDisconnected: SlimServer {mysqueezebox.com} is now disconnected
Nov 16 00:05:23 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:380 notify_serverDisconnected: SlimServer {mysqueezebox.com} - disconnected, but no server alarm in progress : nil
Nov 16 00:05:23 squeezeplay: INFO   net.comet - Comet.lua:1038 Comet {mysqueezebox.com}: advice is handshake, connect in 0 seconds
Nov 16 00:05:37 squeezeplay: INFO   squeezebox.server - SlimServer.lua:710 connected mysqueezebox.com
Nov 16 00:05:37 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:348 notify_serverConnected: SlimServer {mysqueezebox.com} is now connected
Nov 16 00:05:37 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:351 local player connection status is false
Nov 16 00:05:38 squeezeplay: INFO   squeezebox.server - SlimServer.lua:722 self.mac being set to---->nil
Nov 16 00:05:39 squeezeplay: WARN   net.comet - Comet.lua:876 Comet {mysqueezebox.com}: _response, nil id=nil failed: POST body too large (max=51200)
Nov 16 00:05:39 squeezeplay: WARN   net.comet - Comet.lua:956 Comet {mysqueezebox.com}: _response, unknown error: POST body too large (max=51200)
Nov 16 00:05:39 squeezeplay: INFO   net.comet - Comet.lua:997 Comet {mysqueezebox.com}: handleAdvice state=CONNECTED
Nov 16 00:05:39 squeezeplay: INFO   squeezebox.server - SlimServer.lua:734 disconnected mysqueezebox.com idleTimeoutTriggered: nil
Nov 16 00:05:39 squeezeplay: INFO   applet.AlarmSnooze - AlarmSnoozeApplet.lua:367 notify_serverDisconnected: SlimServer {mysqueezebox.com} is now disconnected
Nov 16 00:05:39 squeezeplay: WARN   applet.AlarmSnooze - AlarmSnoozeApplet.lua:380 notify_serverDisconnected: SlimServer {mysqueezebox.com} - disconnected, but no server alarm in progress : nil
Nov 16 00:05:39 squeezeplay: INFO   net.comet - Comet.lua:1035 Comet {mysqueezebox.com}: advice is none server told us not to reconnect

This is probably as a result of the half-completed Comet connection attempts that had been occurring in the previous period. The SN-side fixes that workaround the issues discussed in bug 16617 were unable to handle this case. The SP f/w fixes that are checked into 7.6 would fix this.

*** This bug has been marked as a duplicate of bug 16617 ***