Bugzilla – Bug 747
RadioIO loses lock often; poor re-start
Last modified: 2011-03-16 04:18:41 UTC
Last bug report, then I'll shut up :-) The RadioIO streams seem to lose their lock very often. I can't tell whether that's an issue with the station itself, or with Slimserver. What I can tell, is that Slimserver doesn't re-start nicely. I now have to press 'play' again when this happens (the stream always starts immediately again after pressing the button). It would be nice if Slimserver was a bit more persistent in trying to keep the stream going. Not a showstopper, but still a bit awkward since I like to listen to RadioIOAmbient when going to sleep... Not a situation where you want to keep getting up to press buttons...
Wim: Can you turn on d_source and d_remotestream debugging and post the output when the stream disconnects?
Looking at the recent log entries (but that's only the last minute or so) that you can access from the Slimserver interface, there's a big bunch of these: > 2005-03-13 14:19:18.8472 reduced chunksize to 3703 for metadata > 2005-03-13 14:19:18.8480 would have blocked, will try again later > 2005-03-13 14:19:18.8998 reduced chunksize to 3703 for metadata > 2005-03-13 14:19:18.9005 would have blocked, will try again later > 2005-03-13 14:19:18.9526 reduced chunksize to 3703 for metadata > 2005-03-13 14:19:18.9535 would have blocked, will try again later > 2005-03-13 14:19:19.0057 reduced chunksize to 3703 for metadata > 2005-03-13 14:19:19.0065 would have blocked, will try again later > 2005-03-13 14:19:19.0586 reduced chunksize to 3703 for metadata > 2005-03-13 14:19:19.0593 would have blocked, will try again later There's perhaps a bigger log file that goes back further than one minute? If so, can you point me towards the location of that one? (on OS X)
Can you try this with the latest nightly release? There have been some recent changes regarding HTTP and blocking. Thanks.
Cannot reproduce. If you still see this with 6.0, please reopen.
Tried it for a while with the latest 5.4.1 build, but that didn't help. (Sorry, took a while too reply, too busy at the moment to listen much.) I did notice at one point, when I ran to the computer quickly after the stream dropped, that the entire Slimserver went down when the problem occurred. The prefs panel stated stated that the server was off suddenly. Anyway, although I'm hesitant to use beta versions for software I use every day, I guess I'll have to bite the bullet now. I'll try v.6, and if there's still a problem after that I'll reopen the bug report.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.