Bugzilla – Bug 4424
Squeezebox timeout for connect to Slimserver is too short
Last modified: 2009-01-29 09:47:29 UTC
If running Slimserver on a box which needs to be brought out of suspend to disk (e.g. Suspend2) using Wake on LAN magic packet when the Squeezebox is powered on at the remote, there may well be a delay of 30 seconds or more after SB power on before Slimserver is available. The problem is that the Squeezebox times out after approx 10 seconds if Slimserver cannot be reached, and goes back to power off state. This is not fatal, because after waiting for 20 seconds or so (in my case) the SB can be powered back on again at the remote control. But useability would be improved by a firmware change either to increase the timeout to say 60 seconds or to make the timeout period changeable as a setup parameter.
Now when 'green computing' is so often in headlines, setups with servers shut down when not needed are becoming more common. I'm running the Slimserver on computer acting as my MythTV backend and tt (MythTV) has the option to start server adjustable amount of seconds before recording is scheduled to start. Adding an adjustable delay between 'waking up slimserver' and 'connecting to slimserver' would be a major enhancement on the usability of such setup.
This seems to have been fixed since the last time I saw it. Is anyone still seeing this? Is this really the problem described, or is are you really seeing another bug (which I can't find at the moment) that the player doesn't seem to be reconnecting, regardless of whether the server is awake or asleep? Or are you also sure that you didn't have your power-off display set to dark, so that when it reconnects, the display goes dark?
I see this problem - WOL from a XP standby state causes the following sequence: 1. waking up squeezecenter 2. connecting to squeezecenter 3. error messages in the server log: [08-07-01 11:00:39.6400] Slim::Networking::Async::DNS::resolve (208) DNS server 192.168.123.254 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-07-01 11:00:39.6445] Slim::Networking::Async::DNS::resolve (208) DNS server 68.87.72.130 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-07-01 11:00:39.6478] Slim::Networking::Async::DNS::resolve (208) DNS server 192.168.123.254 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-07-01 11:00:39.6524] Slim::Networking::Async::DNS::resolve (208) DNS server 68.87.72.130 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-07-01 11:00:39.6892] Slim::Networking::Async::DNS::resolve (208) DNS server 192.168.123.254 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error HTTP/1.1 200 OK Server: SqueezeCenter (7.0 - 17793) Connection: Keep-Alive Date: Tue, 01 Jul 2008 16:03:15 GMT Content-Length: 859 Content-Type: text/plain [08-07-01 11:00:39.6400] Slim::Networking::Async::DNS::resolve (208) DNS server 192.168.123.254 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-07-01 11:00:39.6445] Slim::Networking::Async::DNS::resolve (208) DNS server 68.87.72.130 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-07-01 11:00:39.6478] Slim::Networking::Async::DNS::resolve (208) DNS server 192.168.123.254 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-07-01 11:00:39.6524] Slim::Networking::Async::DNS::resolve (208) DNS server 68.87.72.130 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error [08-07-01 11:00:39.6892] Slim::Networking::Async::DNS::resolve (208) DNS server 192.168.123.254 couldn't resolve IP address for www.squeezenetwork.com: Send: Unknown error 4. SB3 box shuts off, "goes dark" Screensave when off is set to NONE. (clock seems to prevent auto standby). 5. wait a few seconds, press power, and Free Your Music then Library - everythings fine. Seems that SB3, or more likely, Squeezecenter (given the error messages in the log, and the behavior of the SB3) just need to wait a longer for XP to sort itself after waking up. Thanks for your assistance. Not a priority bug, just a minor nusance.
This bug shoudl be re-opened - it is not fixed. The issue is that for a server that takes a long time to wake up from a WOL - the time out is too short. My server is set to hibernate and save state to disk - so it takes quite a while to wake up and come back to life. By that time the Squeezebox has given up waiting. They do eventualy catch up with each other - but it's not pretty!