Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 4 of 4
  1. #1
    Senior Member dolodobendan's Avatar
    Join Date
    Dec 2017
    Location
    Braunschweig, Germany
    Posts
    915

    Claim: "retrying in 86400 seconds" but trying it 30s later instead

    So this morning there was this pretty big DSL blackout in Germany caused by a storm. I noticed that in the log LMS announced it would retry connecting to MSB in 86400 seconds. That's 24h hours. But instead, LMS retried it 30s later. There seems to be something wrong with the numbers in that particular error:

    Code:
    [20-02-12 03:56:54.0129] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 86400 seconds
    [20-02-12 03:57:24.0722] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    [20-02-12 03:57:24.0732] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 172800 seconds
    [20-02-12 03:58:14.0074] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    [20-02-12 03:58:14.0084] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 259200 seconds
    [20-02-12 03:59:00.0108] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    [20-02-12 03:59:00.0117] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 345600 seconds
    [20-02-12 04:01:33.0075] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    [20-02-12 04:01:33.0087] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 432000 seconds
    [20-02-12 04:03:11.0127] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    [20-02-12 04:03:11.0136] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 518400 seconds
    [20-02-12 04:04:56.0122] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    [20-02-12 04:04:56.0131] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 604800 seconds
    [20-02-12 04:09:56.0122] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    [20-02-12 04:09:56.0131] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 691200 seconds
    [20-02-12 05:17:52.1491] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    [20-02-12 05:17:52.1500] Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get players from SN: Couldn't resolve IP address for: www.mysqueezebox.com, retrying in 777600 seconds
    [20-02-12 05:23:13.0103] Slim::Networking::SqueezeNetwork::_error (480) Unable to login to SN: Couldn't resolve IP address for: www.mysqueezebox.com
    QLMS 8.0.0@2.10.05 x64 (digimaster) with perl 5.28 dedicated to me. :D / QNAP 469L QTS 4.3.4

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

    Claim: "retrying in 86400 seconds"but trying it 30s later instead

    > So this morning there was this pretty big DSL blackout in Germany caused
    > by a storm. I noticed that in the log LMS announced it would retry
    > connecting to MSB in 86400 seconds. That's 24h hours. But instead, LMS
    > retried it 30s later. There seems to be something wrong with the numbers
    > in that particular error:


    There must be a bug around the mysb.com sign-in I still haven't found. I
    see from mysb log files that sometimes an instance would hammer the
    service with thousands of login requests in a very short time (millions
    within a day!). The LMS side back-off strategy in this case probably
    would fail, as more requests might have been triggered before the first
    error comes back.

    But going to weeks in between re-tries seems wrong, too...

    --

    Michael

  3. #3
    Senior Member dolodobendan's Avatar
    Join Date
    Dec 2017
    Location
    Braunschweig, Germany
    Posts
    915
    Quote Originally Posted by mherger View Post
    > So this morning there was this pretty big DSL blackout in Germany caused
    > by a storm. I noticed that in the log LMS announced it would retry
    > connecting to MSB in 86400 seconds. That's 24h hours. But instead, LMS
    > retried it 30s later. There seems to be something wrong with the numbers
    > in that particular error:


    There must be a bug around the mysb.com sign-in I still haven't found. I
    see from mysb log files that sometimes an instance would hammer the
    service with thousands of login requests in a very short time (millions
    within a day!). The LMS side back-off strategy in this case probably
    would fail, as more requests might have been triggered before the first
    error comes back.

    But going to weeks in between re-tries seems wrong, too...

    --

    Michael
    My LMS really was offline for several hours, not blocked by MSB. I do wonder why the claimed retry interval would be increased by a constant every retry while the actual interval doesn't seem to follow some easy to spot logic ([s]: 30, 50, 46, 153, 98, 105, 300, 4076(!), 321). The log shows two instances of time where it's hh:mm:ss.1xxx. That's where the 4076s spike is. Could be coincidental, of course. Then again, you'd need milliseconds to achieve your millions of login requests a day.
    QLMS 8.0.0@2.10.05 x64 (digimaster) with perl 5.28 dedicated to me. :D / QNAP 469L QTS 4.3.4

  4. #4
    Senior Member dolodobendan's Avatar
    Join Date
    Dec 2017
    Location
    Braunschweig, Germany
    Posts
    915
    What I want to say is: Maybe somewhere that xxxx is used and not ss (in hh:mm:ss.xxxx).
    QLMS 8.0.0@2.10.05 x64 (digimaster) with perl 5.28 dedicated to me. :D / QNAP 469L QTS 4.3.4

Posting Permissions

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