Bugzilla – Bug 4488
Roku SoundBridge Firmware 2.5.174 hangs SlimServer
Last modified: 2007-01-19 14:01:52 UTC
I own both a SqueezeBox v3 and a Roku SoundBridge M500. Originally I planned to leave the SoundBridge offline after buying the SqueezeBox, but someone emailed asking for help running SlimServer with their SqueezeBox, and besides, I just brought up a sound system in the basement... I had recently taken the Roku SoundBridge Firmware 2.5.174 upgrade. Internet radio worked fine, but when I went to connect to the SlimServer like it used to do, it complained that it couldn't establish a connection. Upstairs in my living room my SqueezeBox display went blank and would not respond. The SlimServer pane on my Mac Control panel reported nothing amiss. But I had to click on "StopServer" and "StartServer" to get SlimServer going again such that my SqueezeBox would play. This problem occurrs with both 6.5b3 and 6.5.0. I realize that Roku's firmware has a sketchy port of the Slim Protocol. Even so, your server should not be able to be hung by anything a client sends you so you really should fix this bug. I will also report this problem to the Roku Forum. It is worth testing this against 6.5.1? -wdc
The software is open source; I don't have any hard feelings against anyone for using it. Is there any useful information in the log files? You can change what information gets logged on the Server settings -> Debugging page. I suggest starting with d_slimproto and d_source, and having a look to see if there's any obvious ERROR items. There's information on how to view the resulting logs at http://faq.slimdevices.com/index.php?sid=101&lang=en&action=artikel&cat=2&id=109&artlang=en
Thanks for replying. Thanks also for the pointer to the FAQ item, and the suggestion of the d_slimproto debug option. Oddly, I thought I'd tried setting that option and looking in syslog output, but I didn't find the relevant output. Looking in ~/Library/Logs/slimserver.log, as the FAQ suggests, I did find the tell tale log entry I describe below. I inquired about this situation in the SlimServer Forum, and got significant help there. See: http://forums.slimdevices.com/showthread.php?t=29586 Summary: Apparently it's a known bug and it's been fixed in 6.5.1. Instead of setting d_slimproto in the web interface, I followed instructions to start it in a terminal window with command line option "--d_slimproto It gave a tell-tale error output: Can't locate object method "peerport" via package "Slim::Player::Squeezebox" at /Library/PreferencePanes/SlimServer.prefPane/Contents/server/Slim/Networking/Slimproto.pm line 754. 2006-11-10 11:35:39.1792 Got to the END. 061110 11:37:14 [Note] /Library/PreferencePanes/SlimServer.prefPane/Contents/server/Bin/darwin/mysqld: Normal shutdown That was identified by andyg as "a known bug, fixed in 6.5.1". On his recommendation, I took the latest nightly of 6.5.1, and indeed it remedied the problem I was experiencing. Suggestion: What y'all should probably do is find out which bug this is a duplicate of in your bug database, and mark this report as "duplicate" of that fixed bug. Thanks again for a great server product, and the opportunity to report bugs, and for the help in understanding things a little better.
I searched but couldn't find the bug in the DB. It's suboptimal but I'll just mark this one as resolved.