Bugzilla – Bug 7334
Music files on spun down NAS gives player error on player start
Last modified: 2009-10-30 08:49:04 UTC
I have all my music files stored a share on a NAS (QNAP TS 209 Pro). The share is mounted on my Linux box, and the mounted folder is specified as Music Folder in SqueezeCenter. The NAS is set to spin down when not used. I use my player as Alarm Clock, and when the Alarm starts the following happens: The player turns on. The NAS spins up. The player says something like "Playing from ..." The player then says "Lost connection to the Server. Please check that the server......" The NAS is done spinning up. The player finds the server again, and the Name of the first song is displayed, and the progress bar starts to fill out, but NO music is played, so no good as alarm clock At the end of the first song the player stops with the progress bar filled, and saying "Playing" If I then press the FWD button the player starts the next track, and this time with sound. My guess is that the SqueezeCenter is trying to access the music files, and while waiting for the NAS to wake up, the process talking to the player, is not responding (hence the error from the player). When I access the mounted folder from the Linux box (both with a ls and with the file explorer), I don't get any timeouts. I just have to wait for the NAS to spin up before the files are shown. I have also experienced the same kind of problems when starting the player using the remote (e.g. starting the player by pressing Play on the remote) If I can do any testing, please let me know which Logging settings to turn on.
Forgot this: I'm running on Nightly 17707, but the problem has been there on all the versions of 7.0a I have been running on, since I started using the NAS.
The player is losing it's connection to the server and so is getting confused about playing. How long does it take to spin up, Lars?
Just did a test: ls'ed the mounted folder on my linux box. After 9 secs I received the file list. At the same time the LED indicated that the NAS was ready. I have sometimes seen the file-list arrive before the LED indication - perhaps because part of the information was cached on the NAS. I also think I have seen that 9 secs are around the official start-up time for the NAS.
This may be a hard problem to fix, moving target to Future for now.
Please can you enable logging for 'network.protocol.slimproto' at level 'info' and 'player.source' at level 'info' and allow the problem to occur and then attach the logfile to this bug. Thanks.
Setting to 'monitor' target to get more information and evaluate how many customers are experiencing this problem. The requested log file info would be helpful.
Moving monitor bugs