Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 6 of 6
  1. #1
    Junior Member
    Join Date
    Aug 2019
    Posts
    4

    LMS continuously repeating last track in playlist

    Hi

    I have been using LMS/Squeezebox with iPeng for years without any issues. In the last few months a few gremlins have popped up, the latest being that sometimes the last song in a playlist is repeating over and over, with a short gap of about a minute after the song finishes. There is no repeat option selected in iPeng when this happens and I suspect it has nothing to do with iPeng

    Logitech Media Server Version: 7.7.6 - 1452060463 @ Thu Jan 21 02:17:04 UTC 2016
    Hostname: hostname
    Server IP Address: xxxx
    Server HTTP Port Number: xxxx
    Operating system: Synology DiskStation - EN - utf8
    Platform Architecture: unknown
    Perl Version: 5.24.0 - armle-linux
    Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
    Total Players Recognized: 3 (2 X Radios, 1 X Receiver)

    As part of my investigations into earlier problems I reinstalled LMS on my server, and have updated the firmware on my radios (thought they were set to auto update but if it aint broke...and the problem is not limited to the radios). and the players are set to crossfade if that makes any difference

    Not sure if there is a setting I've missed or where I could find out why the last track restarts. I checked the last 1000 log files and they are full of:

    [19-10-25 12:04:27.8355] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 1296000 seconds
    [19-10-25 12:04:56.1345] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 1382400 seconds
    [19-10-25 12:04:59.0665] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 86400 seconds
    [19-10-25 12:05:04.5537] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 172800 seconds
    [19-10-25 12:05:54.0385] Slim::Networking::SqueezeNetwork::_error (594) Unable to login to SN: Timed out waiting for data
    [19-10-25 12:05:54.0396] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 86400 seconds
    [19-10-25 12:05:56.0314] Slim::Networking::SqueezeNetwork::_error (594) Unable to login to SN: Timed out waiting for data
    [19-10-25 12:05:56.0323] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 172800 seconds
    [19-10-25 12:05:56.1739] Slim::Networking::SqueezeNetwork::_error (594) Unable to login to SN: Timed out waiting for data
    [19-10-25 12:05:56.1748] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 259200 seconds
    [19-10-25 12:06:30.7161] Slim::Networking::SqueezeNetwork::_error (594) Unable to login to SN: Timed out waiting for data
    [19-10-25 12:06:30.7171] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 345600 seconds
    [19-10-25 12:06:33.0321] Slim::Networking::SqueezeNetwork::_error (594) Unable to login to SN: Timed out waiting for data
    [19-10-25 12:06:33.0330] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 432000 seconds
    [19-10-25 12:06:35.6420] Slim::Networking::SqueezeNetwork::_error (594) Unable to login to SN: Timed out waiting for data
    [19-10-25 12:06:35.6430] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 518400 seconds
    [19-10-25 12:06:38.9074] Slim::Networking::SqueezeNetwork::_error (594) Unable to login to SN: 503 Service Temporarily Unavailable
    [19-10-25 12:06:38.9083] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: 503 Service Temporarily Unavailable, retrying in 604800 seconds
    [19-10-25 12:06:40.9164] Slim::Networking::SqueezeNetwork::_error (594) Unable to login to SN: 503 Service Temporarily Unavailable
    [19-10-25 12:06:40.9177] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: 503 Service Temporarily Unavailable, retrying in 691200 seconds
    [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.

  2. #2
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,324

    LMS continuously repeating lasttrack in playlist

    > [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

  3. #3
    Junior Member
    Join Date
    Aug 2019
    Posts
    4
    Thanks Michael, that appears to have done the trick

    I can also confirm that neither of the available repeat options in iPeng were selected

    I stopped LMS on the server for 25 minutes. When I restarted these were the first logs:

    [19-10-25 16:41:47.5061] main::init (353) Starting Logitech Media Server (v7.7.6, 1452060463, Thu Jan 21 02:17:04 UTC 2016) perl 5.024000
    [19-10-25 16:41:52.8984] Slim::Utils::PluginManager::load (235) Couldn't load BBCiPlayerExtra. Error: Plugin is incompatible with this version of Logitech Media Server. Please update.
    [19-10-25 16:42:52.4094] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 86400 seconds

    I can see all the players on iPeng and on the Web UI and it still seems a strange error to say 'timed out, Ill try again in 24 hours'? The state of my logs before suggests that this is an error that keeps happening and maybe the condition cascades, but I havent the foggiest what is timing out or why. While my server has had utilisation issues from time to time it was under no load at all for the duration of this testing, so I dont think that is part of the equation now.

    Ill start keeping an eye on the server logs to see if this starts recurring again but any idea what to check if it does? And what sets the time delay? I'd expect DHL to retry in 24 hours if unsuccessful, but not a network connection attempt?

  4. #4
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,324
    Quote Originally Posted by Mellon View Post
    [19-10-25 16:41:47.5061] main::init (353) Starting Logitech Media Server (v7.7.6, 1452060463, Thu Jan 21 02:17:04 UTC 2016) perl 5.024000
    [19-10-25 16:41:52.8984] Slim::Utils::PluginManager::load (235) Couldn't load BBCiPlayerExtra. Error: Plugin is incompatible with this version of Logitech Media Server. Please update.
    [19-10-25 16:42:52.4094] Slim::Networking::SqueezeNetwork::Players::_player s_error (334) Unable to get players from SN: Timed out waiting for data, retrying in 86400 seconds

    I can see all the players on iPeng and on the Web UI and it still seems a strange error to say 'timed out, Ill try again in 24 hours'? The state of my logs before suggests that this is an error that keeps happening and maybe the condition cascades, but I havent the foggiest what is timing out or why. While my server has had utilisation issues from time to time it was under no load at all for the duration of this testing, so I dont think that is part of the equation now.
    LMS tries to log in to mysb.com to get latest information about apps, players etc. When that fails it usually backs off by doubling the wait until the next re-try. But I think anything beyond a day or two is a bit excessive. In particular when it seems to wait a day after the first failure?...
    Michael

    http://www.herger.net/slim-plugins - Spotty, MusicArtistInfo

  5. #5
    Junior Member
    Join Date
    Aug 2019
    Posts
    4
    Quote Originally Posted by mherger View Post
    LMS tries to log in to mysb.com to get latest information about apps, players etc. When that fails it usually backs off by doubling the wait until the next re-try. But I think anything beyond a day or two is a bit excessive. In particular when it seems to wait a day after the first failure?...
    I have mysqueezebox.com Integration currently set to Disabled

    I cant remember exactly why, but at some point in the past it was doing something funky , and didnt appear to be providing any benefit, so I disabled it.

    But under Advanced>Logging it defines '(network.squeezenetwork) - mysqueezebox.com Logging' so while I would expect it not to be the case (as I have it disabled), that does appear to be exactly what is erroring. I guess the question is, why, if it is disabled?

    Just curious about that now, but many thanks for your assistance in sorting the problem Michael

  6. #6
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,324

    LMS continuously repeating lasttrack in playlist

    > But under Advanced>Logging it defines '(network.squeezenetwork) -
    > mysqueezebox.com Logging' so while I would expect it not to be the case
    > (as I have it disabled), that does appear to be exactly what is
    > erroring. I guess the question is, why, if it is disabled?


    Disabling integration in the settings would still use mysb.com to eg.
    resize online images etc. And technically the mysb.com integration code
    is still there, and with that code comes the logging category, even if
    it wouldn't log much.

    --

    Michael

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •