Bugzilla – Bug 15627
Local player difficult/impossible to connect to new source after current server is made unavailable
Last modified: 2010-02-25 18:21:18 UTC
After shutting tiny SC and ejecting SD card cannot play from any source. Constant spinny when internet Radio or app selected. Wired connection Pings MSB.com okay. Cycled power restores function fw 8459
Ping Ryan
Hmm... interesting: first time I unmount the drive it is ok. Second time no more. It's repeating the following lines over and over again: Feb 8 14:05:31 squeezeplay: ERROR net.http - SocketHttp.lua:388 SocketHttp {Squeezebox Touch_Chunked}:t_sendRequest.pump: connection refused Feb 8 14:05:31 squeezeplay: stack traceback: Feb 8 14:05:31 squeezeplay: /usr/share/jive/jive/net/SocketHttp.lua:388: in function 'pump' Feb 8 14:05:31 squeezeplay: /usr/share/jive/jive/net/SocketTcp.lua:200: in function 'writePump' Feb 8 14:05:31 squeezeplay: /usr/share/jive/jive/net/Socket.lua:186: in function </usr/share/jive/jive/net/Socket.lua:184> Feb 8 14:05:31 squeezeplay: INFO net.comet - Comet.lua:804 Comet {Squeezebox Touch}: _getEventSink error: connection refused Feb 8 14:05:31 squeezeplay: INFO net.comet - Comet.lua:997 Comet {Squeezebox Touch}: handleAdvice state=CONNECTING Feb 8 14:05:31 squeezeplay: INFO squeezebox.server - SlimServer.lua:714 disconnected Squeezebox Touch idleTimeoutTriggered: nil Feb 8 14:05:31 squeezeplay: INFO applet.AlarmSnooze - AlarmSnoozeApplet.lua:308 notify_serverDisconnected: SlimServer {Squeezebox Touch} is now disconnected Feb 8 14:05:31 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:321 notify_serverDisconnected: SlimServer {Squeezebox Touch} - disconnected, but no server alarm in progress : nil Feb 8 14:05:31 squeezeplay: INFO net.comet - Comet.lua:1038 Comet {Squeezebox Touch}: advice is retry, connect in 2.471 seconds Feb 8 14:05:31 squeezeplay: INFO net.slimproto - SlimProto.lua:598 connect to 192.168.0.2 (192.168.0.2) Feb 8 14:05:31 squeezeplay: INFO net.slimproto - SlimProto.lua:769 connection error: closed, reconnecting in 1.538 seconds Feb 8 14:05:32 squeezeplay: INFO net.slimproto - SlimProto.lua:598 connect to 192.168.0.2 (192.168.0.2) Feb 8 14:05:32 squeezeplay: INFO net.slimproto - SlimProto.lua:769 connection error: closed, reconnecting in 3.127 seconds Feb 8 14:05:33 squeezeplay: ERROR net.http - SocketHttp.lua:388 SocketHttp {Squeezebox Touch_Chunked}:t_sendRequest.pump: connection refused Feb 8 14:05:33 squeezeplay: stack traceback: Feb 8 14:05:33 squeezeplay: /usr/share/jive/jive/net/SocketHttp.lua:388: in function 'pump' Feb 8 14:05:33 squeezeplay: /usr/share/jive/jive/net/SocketTcp.lua:200: in function 'writePump' Feb 8 14:05:33 squeezeplay: /usr/share/jive/jive/net/Socket.lua:186: in function </usr/share/jive/jive/net/Socket.lua:184> Feb 8 14:05:33 squeezeplay: INFO net.comet - Comet.lua:804 Comet {Squeezebox Touch}: _getEventSink error: connection refused Feb 8 14:05:33 squeezeplay: INFO net.comet - Comet.lua:997 Comet {Squeezebox Touch}: handleAdvice state=CONNECTING Feb 8 14:05:33 squeezeplay: INFO squeezebox.server - SlimServer.lua:714 disconnected Squeezebox Touch idleTimeoutTriggered: nil Felix/Ben - I'm not so familiar with the server switching code. Any more idea than I have?
Felix - that's definitely beyond my SP knowledge... May I ask you to take over? Thanks!
Even though I can reproduce this bug, I am unable to fix it. Sorry.
Vahid - this is the bug I was talking about in the meeting. Thanks for looking at it. You should be able to reproduce fairly easy with Ryans description. What I see is that server connected notifications are coming in for servers we aren't connected to anymore. For instance if you connect to TinySC and SN and a BigSC are around too you will see these for SN and BigSC: Feb 11 17:47:55 squeezeplay: INFO squeezebox.server - SlimServer.lua:714 disconnected mysqueezebox.com idleTimeoutTriggered: true and shortly after that: you will see connected notifications for these servers again (which I think is wrong and causing the problem)
Vahid, the fix I am working on for bug 15633 will most likely also cover this bug too.
I think that this is a general problem whenever the server that SP is using gets shut down, and not related to a local (TinySC) instance.
*** Bug 15613 has been marked as a duplicate of this bug. ***
I tested this with the latest version of the firmware as of today and is working fine.
*** This bug has been marked as a duplicate of bug 15633 ***