Bugzilla – Bug 9004
Problems connecting with slow server
Last modified: 2009-10-05 14:28:52 UTC
Sent via PM by JJD: Many people have been complaining about the controller losing connection to the music source. I have been experiencing this as well (see: http://forums.slimdevices.com/showpost.php?p=324795&postcount=246) I think I have found the how to solve the issue. After experimenting with some different disk units I found out that the throughput of the disk is extremely important. A slow (network) drive causes the problem instantly. It does not matter if you have the Database/Cache on the internal fsat drive. If the actual track files (MP# or whatever) reside on the slow disk the problem occurs as soon as the individual songs have to be presented on the controller. I think you have build in some max. response times in the slim server software that are exceeded at that moment combined with some strange error handling. My suggestion increase the delay time (or give users the ability to change it) and adapt the error handling. I hope this hleps to make the product more stable.
Extra info. Even with all songs on the slower Network Drive. The squeeze Center software works fine, but the controller loses the connection to the SB. This problem may have someting to do with Bug 311 as well, because I have my songs on a network drive.
*** Bug 9018 has been marked as a duplicate of this bug. ***
Oops! Sorry about the duplicate! Here were my comments on the issue: I started seeing very similar behavior last Thursday... it turns out that on Thursday one of the drives in my NAS array started having errors and the network access to that unit has been extremely slow ever since. Fast enough to stream music, but too slow for the Controller I guess. Almost every time I use the controller now it looses connection to the SqueezeCenter server even though music is playing just fine. I have to attribute this change in behavior to the slow back-end storage of the music library.. (4200+ flac songs over NFS).
Give Matt an SD card so he can get a log. We should focus on the connection issues, not the async IO issues that may in some sense be the root cause. QA to also try reproducing with a music library on a network drive.
Bumping to 7.3 and increasing the priority
*** Bug 9176 has been marked as a duplicate of this bug. ***
Ross to check against new schema build. Try DD-WRT with port slowed down.
To slow things down I've set scanner priority to the highest, set artwork resampling to resize, and rescanned a large library on my ReadyNAS. SqueezeCenter running on the NAS doesn't handle this well. 7.2 and 7.2.1 the Controller gets a blue icon while trying to browse music during the scan, and it never recovers even after the scan is complete. When you browse to music it attempts to connect to the source but fails. 7.3 (r3253) also gets into this state with the blue icon / fail to reach source, but when the scan completes the Controller reconnects.
Ping Brandon on status ....
I also had exactly these problems with my ReadyNAS NV+. I ended up buying a ReadyNas PRO. I believe the NV+ is to slow or the software not optimized for it...
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code. Feel free to move it back if it's specific to the single original product.
Reset priority before triage.
Removing new_schema tag, this isn't directly related to new_schema
Has anyone running SC 7.4 seen this error happen again?
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
QA has been unable to reproduce this with 7.4. Please retest with that version, if you still see an issue please reopen and provide logs.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.