> [19-10-25 12:06:43.6337] Slim::Networking::SqueezeNetwork::_error (594)
> Unable to login to SN: 503 Service Temporarily Unavailable
>
> Responses can be a bit laggy on the server as it is often working hard
> on CCTV tasks (which is what I expect the above logs reflect - although
> the retry time seems a bit bizzare, 'retrying in 8 days??), but I was
> using LMS fine during this time, albeit with the repeating last track.
There's definitely something wrong with your LMS. That last response
most likely means the load-balancer banned your login attempts because
your LMS tried too many times in a too short interval.
I'd suggest you shut down LMS for 10-15 minutes to let the rate limiter
cool down. Then you fire it back up.
If the problem persists you might want to give more information about
what kind of track you're playing. And whether you're sure you haven't
hit the "repeat track" button ;-)
--
Michael
> Unable to login to SN: 503 Service Temporarily Unavailable
>
> Responses can be a bit laggy on the server as it is often working hard
> on CCTV tasks (which is what I expect the above logs reflect - although
> the retry time seems a bit bizzare, 'retrying in 8 days??), but I was
> using LMS fine during this time, albeit with the repeating last track.
There's definitely something wrong with your LMS. That last response
most likely means the load-balancer banned your login attempts because
your LMS tried too many times in a too short interval.
I'd suggest you shut down LMS for 10-15 minutes to let the rate limiter
cool down. Then you fire it back up.
If the problem persists you might want to give more information about
what kind of track you're playing. And whether you're sure you haven't
hit the "repeat track" button ;-)
--
Michael