Bugzilla – Bug 4261
slimserver appears started when it's not in Mac preference pane
Last modified: 2008-12-18 11:12:53 UTC
when you install slimserver for the first time on a Mac, it can take up to a minute (!) to start. Well before this you can click on the Web button in the preference pane, which attempts to open up the web interface, but fails. I suggest that the server drop a file somewhere that indicates that it's up and ready for HTTP requests. Then the preference pane can look for the process running AND that file before encouraging folks to connect to the server.
Dean, for what target would you like this implemented?
noticed this type of problem affects windows as well. the new slimtray.exe opens the browser once it detects that the http ports are listening. This too early, as other init processes need to complete before slimserver goes into it's idle loop, processing requests. One possible option is to hold off on http->init until everythign else is done. The OSX prefPane could then detect the open port just as slimtray.pl does, if it doesn't already. the patch: Index: slimserver.pl =================================================================== --- slimserver.pl (revision 10468) +++ slimserver.pl (working copy) @@ -346,9 +346,6 @@ Slim::Utils::UPnPMediaServer::init(); } - $log->info("SlimServer HTTP init..."); - Slim::Web::HTTP::init(); - $log->info("Source conversion init.."); Slim::Player::Source::init(); @@ -379,6 +376,9 @@ checkVersion(); + $log->info("SlimServer HTTP init..."); + Slim::Web::HTTP::init(); + # otherwise, get ready to loop $lastlooptime = Time::HiRes::time();
patch to slimserver.pl in trunk at change 10470.
I'm still seeing this with 6.5.2 - 12047 OS X 10.4.9. I click start SlimServer and instantly I can click web access, which is blank for about 30 seconds and then says cannot find server.
The patch has only gone into trunk and may or may not have had any effect. Testing would have to be done using 7.0a1. If it works, then perhaps we could port a similar fix to 6.5.3. I expect this will involve a fix in the prefpane itself, which is not something I can do as it is only accessible to those with 10.4.x
Still seeing this with 7.0a1 - 12181 10.4.9. :(
Dean notes this happens at startup time when SqueezeCenter is very busy and it not yet available for web or streaming requests. He suggests it be assigned to him for pondering, but left as targeted for 7.0.
Dean is going to do the prefs pane part, but Andy volunteered to write a perl script to check to see if the port is active.
Over to Dean.
Fixed in change 14486.
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.