PDA

View Full Version : Connection timeouts



itm
2014-08-03, 14:09
I run LMS 7.7.2 on Windows Server 2008. I always find that the first request sent to the server each day from a mobile device (e.g. the Logitech Android app) always results in a connection timeout. This can be song search, or a simple list of New Music for example. I have to repeat the request several times before it will return any result. After the first successful query everything is fine - it's as if the server is slow to "wake up" (even though the Windows server is running 24/7), and this causes timeouts with connected devices.
I get the same problem with both the Logitech Android app and Squeeze Commander.
Has anyone else noticed this, and is there anything I can do to fix it?

toby10
2014-08-04, 01:35
What about an actual hardware player attempting to connect by itself (no App)? Same result? Sure computer is not going into sleep/hibernation? Any chance the computer is getting a different IP (maybe router is re-leasing IP's nightly)?

Squeezed_Rotel
2014-08-04, 03:09
I have always experienced this behavior using 7.3 through 7.8. My server is a W7 box that sleeps 24/7, or until a boom or iPad sends a wake up (wol). In my case, the server never completes the wake up in time to prevent the "waking up server...connecting...cannot connect..." string of messages...
A repeat of the process is of course always successful i.e. no timeout.

Mnyb
2014-08-04, 03:28
I have always experienced this behavior using 7.3 through 7.8. My server is a W7 box that sleeps 24/7, or until a boom or iPad sends a wake up (wol). In my case, the server never completes the wake up in time to prevent the "waking up server...connecting...cannot connect..." string of messages...
A repeat of the process is of course always successful i.e. no timeout.

On an actual squeezebox you just have to wait and dont touch any buttons (if you do touch a button you may have to repaet the conection attempt ) , I know because i WOL my server from cold ie booting it up .

itm
2014-08-05, 02:13
What about an actual hardware player attempting to connect by itself (no App)? Same result? Sure computer is not going into sleep/hibernation? Any chance the computer is getting a different IP (maybe router is re-leasing IP's nightly)?

I tried a search from a Squeezebox Boom first thing this morning and it didn't time out. Maybe it's just the Android apps that give up before the server has responded? Does anyone know if it's possible to fix this, or if there are other Android apps which are more patient when waiting for replies from LMS?

pablolie
2014-08-09, 12:17
i desisted to try to use WOL, i could never get it to work so it wouldn't irritate me. the last thing i want when i want to chill listening to music is an error message greeting me every time. :-) hence i built a relatively low power but good performance machine that i just leave always on. shame. if anyone has a fool-proof method i am also very interested. then again my stereo pulls 80w in standby mode, so saving 25w on the server side isn't a huge deal. but between the two they do amount to 25% of my electricity bill, i have calculated (which is moderate thanks to many other saving measures). always-on does add up.

Mnyb
2014-08-10, 00:10
I have hit a compromise , I WOL from completely shut off , booting my HP microserver , but then it does not sleep .

So I just boot it when I get home from work , touching any of my players then let my server run during the evening and then turns it off when I go to bed .

Some weekends it may run 24/7 :P forgetting to turn it off Saturday night .

itm
2014-08-10, 04:32
Just to confirm - my Windows LMS runs 24/7 and I still get a timeout on the first connection of the day (or when it's been idle for a few hours and the HDD has gone into sleep mode). So presumably the timeouts are happening while waiting for the HDD to spin up.

To correct my earlier post - I DO also get this problem with Logitech hardware (it happened on my Squeezebox Boom yesterday).