Bugzilla – Bug 14972
SBC unable to WOL server after 7.4.x upgrade (when SBR was moved to mySqueezeBox.com)
Last modified: 2012-04-15 09:32:40 UTC
After upgrading to SqueezeBox Server 7.4.0 (now 7.4.1 final), the SqueezeBox Controller no longer sends WOL signal to the last connected local server, if the Squeezebox Receiver it was connected to mySqueezeBox.com when the server was shut down. When I turn on the SBC and choose Music to access the local server, I simply get a message saying: "Get SqueezeBox Server software on www.mysqueezebox.com, og make sure it's installed and running on a computer on the network" No matter how many times I turn off/on the SBC or click Music, no WOL is sent. IMPORTANT!!! This problem *only* occurs when the SqueezeBox Receiver is moved to mySqueezebox.com and the local server (running SqueeezeBox Server) is subsequently shut down. This step is important if you test the issue! If the SBR is *not* moved from the local server, WOL works fine. Please note that: - If I WOL the server from another PC and then turn on the SBC, everything works normally - but of course this isn't practical. - This setup worked perfectly with SqueezeCenter 7.3, and matching SBC firmware - The problem is also posted here: http://forums.slimdevices.com/showthread.php?t=70448 - The SBC is using firmware 7.4 r7915 - I tried reinstalling the SBS (SqueezeBox Server) software and the SBC firmware. No change.
I'm getting pretty much the same results here with 7.4.1. I can duplicate this bug pretty consistently. When the packet is not being sent, if I go to mysqueezebox.com and disconnect the Duet, the duet then correctly sends the WOL packet. If I send the WOK packet via my phone or laptop the duet then works correctly, but this is not ideal. This is also another case in which IPENG seems to work better than the controller, it always seems to send the WOL packet at the correct time and in the correct way. kantblue
Hi didn't have time to post when voted. I'm also having similar issues but I'm using the SB Classic. I've tried testing as suggested in the first post and get the same results. If you'd like me to do any futher testing as I'm using a different platform let me know.
Seeing the same behaviour as Innocence with the 7.4.1 upgrade. Had totally consistent WOL function prior to this when running firmware associated with 7.3.x. WOL packet seemed to get sent everytime the SBC started or tried to access the local library under 7.3.x. Only have WOL packets sent correctly if SBC has connected to the local library on the previous seesion rather than www.mysqueezebox.com, also as already reported.
I am out of the office Tuesday 22nd Dec, if you require help on a technical problem please log a call back and one of my collegues will get back to you. If you require help on an urgent RSAA issue, please contact Mick Price Best regards Andy
Same as described by Innocence. This is a severe error in my opinion. A major factor in purchasing the Squeezebox was de-tethering from the storage. If I have to walk upstairs and turn on the server every time, it becomes much less useful. Please bump this up. Thanks! Mike
I am out of the office until the new year, if you require help on a technical problem please log a call back and one of my collegues will get back to you. If you require help on an urgent RSAA issue, please contact roland.fortune@hp.com Best regards Andy
Changing priorities due to management guidance.
Felix does this fall into your area?
I listen to Last.fm radio a lot, and so my players are usually connected to mysqueezebox.com and the SBS server is hibernated. If I want to wake the server with my Boom, I just have to tell it to switch libraries. With the Controller, this only works directly after it has been powered up. I select My Music and get a message that this choice requires switching libraries. Then I can select my server and a WOL package is submitted. If the Controller has been running for some time and I have been playing some music through mysqueezebox.com, it completely forgets about my server. If I then select My Music it tells me to go and install the SBS software, first. I can obviously work around it by power cycling the Controller, but taking into account the time it takes to boot, that is not a preferred option. (quoted from this forum thread: http://forums.slimdevices.com/showthread.php?t=75016)
Any word on this? I'd like to know if this is an error that will be fixed or if it is a policy decision to disable WOL.
I'd like a statement too. I'm very dissatisfied that this important feature suddently stopped working and that they're apparently doing nothing to fix it. Only thing they've done with this bug since I reported it is to make it a lower priority :(
(In reply to comment #11) > I'd like a statement too. I'm very dissatisfied that this important feature > suddently stopped working and that they're apparently doing nothing to fix it. > Only thing they've done with this bug since I reported it is to make it a lower > priority :( Agreed. Frankly this seems such an easy one to fix that I can't believe we now have to wait for v8 for it to be sorted out? I mean - seriously - the WOL module is clearly already there in the code. Really I think this bug just needs fixing, but in the meantime, could you not: a) Have the controller send a WOL packet whenever the user accesses their list of albums or artist? b) re-instate the old behaviour of pressing the blue button on the front of the receiver to send a WOL packet? c) add in a specific "Send WOL packet" command option on a settings menu? d) add an app to do this in "My Apps"? This obviously seems like a trivial issue to whoever is prioritising these things but it's something I looked into before buying the Duet and if it hadn't been working I wouldn't have considered purchasing it: my server is two flights of stairs above my hi-fi so it's a major pain for me. I would stress that this isn't a long-standing minor issue: it is something which was previously working and is now broken. As a coder myself, I realise that users always say "it seems like it should be easy" but... really... this should be easy... I really would appreciate a re-prioritisation of this bug or, failing that, a statement as to why it will be delayed and answers as to why an interim solution as above can't be put in place.
point taken. flagged for discussion in bug meeting.
As others,I am also hoping this bug gets higher priority action. The issue is not purely one of convenience - I'm sure some will choose to leave their Squeezebox Server machine permanently powered up as a workaround. This bug is seriously hindering those who may otherwise have reduced power wastage by having the server power up only when required.
Same problem for me: after a completely clean install of 7.4.2 r30215, neither of my SB3s (firmware 130) will WOL Squeezebox Server any more. Hugely frustrating.
Added my votes here I saw this before but it got no attention then There are this duplicate: I saw this behaviur 2009-12-07 09:14 PST and files this bug https://bugs-archive.lyrion.org/show_bug.cgi?id=15259 This was then called a duplicate of: https://bugs-archive.lyrion.org/show_bug.cgi?id=10191 This from 2008-12-01 this bug is still unassigned !? Unassigned after almost 3 years ?
(In reply to comment #15) > Same problem for me: after a completely clean install of 7.4.2 r30215, neither > of my SB3s (firmware 130) will WOL Squeezebox Server any more. Hugely > frustrating. Just to be clear. Bug 14972 talks about WOL sent from SB Controller and _not_ from a SB3 / Classic. Have you connected your SB3 to your Squeezebox Server at least once after you upgraded? This should give SB3 the opportunity to learn the servers MAC address. If you still see this issue with your SB3s please open a separate bug. Thank you Felix
New bug opened for the SB3: Bug 15808
Felix to investigate for possible 7.5.0 checkin. If it is risky, we will delay until the next release. Thanks, Felix!
I think my initial idea to add a WOL option to the "To enable 'My Music' try the folloging:..." message screen is wrong. Some more testing showed that we probably should keep the last remote SC the device was connected to in the list. (Similar as we do on ip3k players where the last SC is still available to connect to.) So when "My Music" then is selected the last SC is still listed and selecting it starts the "Connecting to..." spinny and that also sends the WOL packet.
Created attachment 6594 [details] Proposed patch This patch keeps the last remote SC in the list even when connected to SN.
Update hours worked
Alan to review the patch
I have the exact same problem. I have two Duets-two controllers and two players. My server, which hibernates after half an hour of inactivity, vanishes from the available libraries in the SBC if I have been connected to mysqueezebox.com directly. I am having to do one of the following: 1. WOL my server using my laptop (works, but impractical) 2. Access mysqueezebox.com VIA the Squeezebox Server running on my dedicated music server. That way, the server never vanishes from the available libraries listed in the SB Controller even after the server hibernates. WOL works, too. While it works, I am not happy about keeping the my server running when listening to internet radio...it is an unnecessary waste of electricity which is detrimental to my wallet and the environment, and adds to the wear and tear of my server.
Felix, the patch looks good. Alan.
== Auto-comment from SVN commit #8638 to the jive repo by fmueller == == https://svn.slimdevices.com/jive?view=revision&revision=8638 == Bug: 14972 Description: Do not remove last known remote SC from music source list so it can be selected and wake on lan is sent.
Thanks, Alan, for reviewing the patch. Felix
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!
It seems that this bug is back with 7.7.2 or earlier. After installing 7.7.2, my Controller was caught in an endless boot cycle. I had to perform a factory reset which brought back this problem.