I was playing random music. A song finished, the next song started, but the
previous song info was showing on the now playing screen. I couldn't control
the player at all - unresponsive, but the music was still playing.
I checked the server, and noticed the following:
[22:02:56.8089] Slim::Networking::Async::HTTP::_http_read (279) Error reading
headers: Server closed connection without sending any data back at
P:\Music\SlimServer\trunk\server\CPAN/Net/HTTP/Methods.pm line 306.
...propagated at P:\Music\SlimServer\trunk\server\CPAN/Net/HTTP/NB.pm
line 32.
[22:02:56.8102] Slim::Networking::Async::HTTP::_http_error (264) Error: [Error
reading headers: Server closed connection without sending any data back at
P:\Music\SlimServer\trunk\server\CPAN/Net/HTTP/Methods.pm line 306.
...propagated at P:\Music\SlimServer\trunk\server\CPAN/Net/HTTP/NB.pm
line 32.
]
[22:02:56.8108] Slim::Networking::SimpleAsyncHTTP::onError (183) Failed to
connect to http://87.117.229.205:80/protocol_1.2 (Error reading headers: Server
closed connection without sending any data back at
P:\Music\SlimServer\trunk\server\CPAN/Net/HTTP/Methods.pm line 306.
...propagated at P:\Music\SlimServer\trunk\server\CPAN/Net/HTTP/NB.pm
line 32.
)
[22:06:14.8150] Slim::Networking::Async::_connect_error (151) Failed to
connect: Unknown error
[22:06:14.8159] Slim::Networking::Async::_async_error (248) Error: [Connect
timed out]
[22:06:14.8164] Slim::Networking::Async::HTTP::_http_error (264) Error:
[Connect timed out]
[22:06:14.8168] Slim::Networking::SimpleAsyncHTTP::onError (183) Failed to
connect to http://87.117.229.205:80/protocol_1.2 (Connect timed out)
[22:09:31.1273] Slim::Networking::Async::_connect_error (151) Failed to
connect: Unknown error
[22:09:31.1282] Slim::Networking::Async::_async_error (248) Error: [Connect
timed out]
[22:09:31.1286] Slim::Networking::Async::HTTP::_http_error (264) Error:
[Connect timed out]
[22:09:31.1289] Slim::Networking::SimpleAsyncHTTP::onError (183) Failed to
connect to http://87.117.229.205:80/protocol_1.2 (Connect timed out)
These errors continued to occur.
I tried nslookup 87.117.229.205 - it is post2.audioscrobbler.com. That address
was also pingable.
I assume these errors to be associated with my lack of control on my player.
If there is an error posting scrobble info, I would assume SC would queue
tracks and try again in the future, but also this should be a background task
that doesn't block any networking traffic. I guess that's the intention, and
I've not witnessed problems in the past.
Phil
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta
