[19-08-02 17:08:32.1099] Request 0.62725 : Plugins::Spotty::Connect::_connectEvent [19-08-02 17:08:32.1120] IO 0.63400 : Slim::Web::HTTP::processHTTP [19-08-02 17:08:33.4516] Request 1.31422 : Plugins::Spotty::Connect::_connectEvent [19-08-02 17:08:33.4534] IO 1.31720 : Slim::Web::HTTP::processHTTP [19-08-02 17:08:34.7415] Request 1.26792 : Plugins::Spotty::Connect::_connectEvent [19-08-02 17:08:34.7434] IO 1.27143 : Slim::Web::HTTP::processHTTP [19-08-02 17:09:34.4085] Page Build 30.11427 : Page: music/93ceefd8/cover_240x240_m [19-08-02 17:09:34.4088] IO 30.11629 : Slim::Web::HTTP::processHTTP [19-08-02 17:10:50.0742] Page Build 30.02197 : Page: music/21343/cover.jpg [19-08-02 17:10:50.0747] IO 30.02361 : Slim::Web::HTTP::processHTTP [19-08-02 17:11:20.3023] Page Build 30.06126 : Page: music/21344/cover.jpg [19-08-02 17:11:20.3027] IO 30.06318 : Slim::Web::HTTP::processHTTP
Ok, something about the web server seems to be utterly wrong. >30s to get an image isn't good. Would the log file continue like that?
Would those images be huge? Eg. load http://yourserver:9000/music/21344/cover.jpg - what is its size (both dimensions and file size)?
-- Michael _______________________________________________ Squeezecenter mailing list Squeezecenter@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/squeezecenter
