Home of the Squeezebox™ & Transporter® network music players.
Page 7 of 8 FirstFirst ... 5678 LastLast
Results 61 to 70 of 78
  1. #61
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    20,749
    Quote Originally Posted by AndyTwizzle View Post
    Here's my LMS 8.1 settings - looks like IO::Socket::SSL is 2.044:
    ..
    And openssl shows as version 1.1.0:
    ..

    How's that all look - and what's next steps for error diagnosis?
    OpenSSL 1.1.0l is OK although 2 years old.
    IO::Socket::SSL is older 2.044 as it is from Jan 2017 but I'm assuming that since you are using Docker and a container - other users are using same version without problems.

    Without having to go through the other thread - can you confirm you used the "official" LMS container to get LMS going.

  2. #62
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    20,749
    Quote Originally Posted by mherger View Post
    > Here's my LMS 8.1 settings - looks like IO::Socket::SSL is 2.044:

    It's not an SSL issue. As I said your instance did successfully sign in
    (as do many others running the same image). I believe it's only some
    timing issue. Give it some time before checking the web UI.
    The OP (DMayer) of this thread has similar error message and it was hard to pin down except 8.1 - is the same issue - timing ?

  3. #63
    Senior Member
    Join Date
    Jan 2012
    Posts
    117
    Quote Originally Posted by bpa View Post
    OpenSSL 1.1.0l is OK although 2 years old.
    IO::Socket::SSL is older 2.044 as it is from Jan 2017 but I'm assuming that since you are using Docker and a container - other users are using same version without problems.

    Without having to go through the other thread - can you confirm you used the "official" LMS container to get LMS going.
    I used the lmscommunity/logitechmediaserver:latest repository, if that's what you mean?
    Name:  2021-06-10 LMS 8.1 Docker repository.JPG
Views: 55
Size:  17.3 KB
    • Synology D218+ running LMS 8.1.1 in Docker container
    • 1 x Squeezebox Touch, 2 x Squeezebox Radios, 1 x Squeezebox Receiver, Squeeze Player & Squeeze Ctrl apps on Galaxy Tab S5e & Galaxy A40
    • Raspberry Pi 4B 8GB (with 7" Touchscreen in case & Flirc USB IR dongle) & Pi 4B 8GB in Flirc case, both running piCorePlayer 8.0.0 & LMS 8.1.1, connecting over Wi-fi to DS218+, or LMS library copy on 2TB USB hard drive plugged into Pi when no Wi-fi available
    • LMS library of ALAC, ACC/M4A and MP3 files

  4. #64
    Senior Member
    Join Date
    Jan 2012
    Posts
    117
    Quote Originally Posted by mherger View Post
    > Here's my LMS 8.1 settings - looks like IO::Socket::SSL is 2.044:

    It's not an SSL issue. As I said your instance did successfully sign in
    (as do many others running the same image). I believe it's only some
    timing issue. Give it some time before checking the web UI.
    First and foremost, thanks for all the valuable assistance so far on this problem, it's much appreciated.

    I'm afraid I don't understand what you mean by a timing issue. I installed LMS 8.1 in Docker on 24 May, and in order to test out its stability, left it running and used it repeatedly for over a week. In all that time the Radio shortcuts did not appear. Once I started checking the logs, the error messages only appear when I cleared my mysqueezebox credentials, saved, then added them back in and saved - so I'm not really sure how long I should wait, and whether I should repeatedly attempt to clear my credentials and add them back in.

    In the last week I've been using 7.9 again, but now I'm going to keep using the Docker 8.1 version to see if it does eventually log me in at the LMS end - what actions would you recommend that would give me the best chance of getting over this timing issue, and how long should I wait?

    Here's the most recent logs, again showing the errors - note the presence of a new error this time in bold (Utils::Timers::__ANON__ (272)), does this provide any further clues?:

    [21-06-10 18:42:01.3140] main::init (388) Starting Logitech Media Server (v8.1.1, 1610364019, Fri Jan 29 08:24:15 CET 2021) perl 5.024001 - x86_64-linux-gnu-thread-multi
    [21-06-10 18:43:48.9461] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Timed out waiting for data
    [21-06-10 18:43:48.9469] Slim::Networking::SqueezeNetwork::_init_error (156) Unable to login to mysqueezebox.com, sync is disabled: Timed out waiting for data (https://www.mysqueezebox.com)
    [21-06-10 18:43:48.9477] Slim::Networking::SqueezeNetwork::_init_error (172) mysqueezebox.com sync init failed: Timed out waiting for data, will retry in 300 (https://www.mysqueezebox.com)
    [21-06-10 18:44:20.2875] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Invalid mysqueezebox.com username or password.
    [21-06-10 18:45:20.7756] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Timed out waiting for data
    [21-06-10 18:45:20.7760] Slim::Networking::SqueezeNetwork::_init_error (156) Unable to login to mysqueezebox.com, sync is disabled: Timed out waiting for data (https://www.mysqueezebox.com)
    [21-06-10 18:45:20.7765] Slim::Networking::SqueezeNetwork::_init_error (172) mysqueezebox.com sync init failed: Timed out waiting for data, will retry in 600 (https://www.mysqueezebox.com)
    [21-06-10 18:48:58.0363] Slim::Utils::Timers::__ANON__ (272) Error: Timer Slim::Networking::SqueezeNetwork::__ANON__ failed:


    Thanks again

    Andy
    Last edited by AndyTwizzle; 2021-06-10 at 12:44.
    • Synology D218+ running LMS 8.1.1 in Docker container
    • 1 x Squeezebox Touch, 2 x Squeezebox Radios, 1 x Squeezebox Receiver, Squeeze Player & Squeeze Ctrl apps on Galaxy Tab S5e & Galaxy A40
    • Raspberry Pi 4B 8GB (with 7" Touchscreen in case & Flirc USB IR dongle) & Pi 4B 8GB in Flirc case, both running piCorePlayer 8.0.0 & LMS 8.1.1, connecting over Wi-fi to DS218+, or LMS library copy on 2TB USB hard drive plugged into Pi when no Wi-fi available
    • LMS library of ALAC, ACC/M4A and MP3 files

  5. #65
    Senior Member
    Join Date
    Jan 2012
    Posts
    117
    Quote Originally Posted by Paul Webster View Post
    Should work fine in 8.1 and with that Docker image - if not there would be a lot more complaints.

    Set loggin (Settings/Advanced/Logging/network.squeezenetwork) to Debug (click apply)
    and then check the logs to see what is going on.

    I just put in a bad password and then the good one to see what the logs show ... so compare yours with:
    Thanks Paul.

    Just did this, then a combination of clearing and saving blank credentials, logging in with wrong passwords, wrong user names, then finally the correct details. Quite a bit to digest in the debug logs - grateful if you can cast your eye over this for your opinion on what may be going on (I did a find/replace on my actual email address, replacing it with myemail@myprovider.com):
    Code:
    [21-06-10 20:29:24.6540] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 20:29:24.6822] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 20:29:24.6833] Slim::Networking::SqueezeNetwork::Players::shutdown (75) SqueezeNetwork player list shutdown
    [21-06-10 20:29:24.7784] Slim::Networking::SqueezeNetwork::PrefSync::_init_done (57) Got list of SN prefs to sync: 55 prefs
    [21-06-10 20:29:28.0015] Slim::Networking::SqueezeNetwork::PrefSync::syncDownGlobal (200) Requesting global sync down from SN: { since => "1623354417" }
    [21-06-10 20:29:28.0020] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:29:28.0023] Slim::Networking::SqueezeNetwork::login (267) A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 20:29:28.0026] Slim::Networking::SqueezeNetwork::PrefSync::_syncDown_error (370) Global Sync Down failed: A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 20:29:47.9949] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 20:29:47.9954] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:29:47.9957] Slim::Networking::SqueezeNetwork::login (248) We've failed to log in a few moments ago, or are still waiting for a response. Let's not try again just yet, we don't want to hammer mysqueezebox.com.
    [21-06-10 20:29:48.0235] Slim::Networking::SqueezeNetwork::PrefSync::_init_error (126) Unable to get list of prefs to sync with mysqueezebox.com, sync is disabled: An unexpected error occurred while validating your mysqueezebox.com account. Please make sure network connectivity is working fine.
    [21-06-10 20:29:48.0243] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 20:29:48.1141] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Invalid mysqueezebox.com username or password.
    [21-06-10 20:29:54.0024] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:29:54.0031] Slim::Networking::SqueezeNetwork::login (267) A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 20:29:59.2547] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 20:29:59.2553] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:29:59.2558] Slim::Networking::SqueezeNetwork::login (248) We've failed to log in a few moments ago, or are still waiting for a response. Let's not try again just yet, we don't want to hammer mysqueezebox.com.
    [21-06-10 20:29:59.2563] Slim::Networking::SqueezeNetwork::PrefSync::_init_error (126) Unable to get list of prefs to sync with mysqueezebox.com, sync is disabled: An unexpected error occurred while validating your mysqueezebox.com account. Please make sure network connectivity is working fine.
    [21-06-10 20:29:59.2573] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 20:30:18.0043] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:30:18.0046] Slim::Networking::SqueezeNetwork::login (248) We've failed to log in a few moments ago, or are still waiting for a response. Let's not try again just yet, we don't want to hammer mysqueezebox.com.
    [21-06-10 20:30:18.5001] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Invalid mysqueezebox.com username or password.
    [21-06-10 20:30:24.2261] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 20:30:24.2269] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:30:24.2274] Slim::Networking::SqueezeNetwork::login (267) A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 20:30:24.2279] Slim::Networking::SqueezeNetwork::PrefSync::_init_error (126) Unable to get list of prefs to sync with mysqueezebox.com, sync is disabled: A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 20:30:24.2289] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 20:30:24.3663] Slim::Utils::Prefs::__ANON__ (592) SN session has changed, removing cookies
    [21-06-10 20:30:24.3674] Slim::Networking::SqueezeNetwork::_login_done (416) Logged into SN OK
    [21-06-10 20:30:24.3682] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 20:30:24.3685] Slim::Networking::SqueezeNetwork::Players::shutdown (75) SqueezeNetwork player list shutdown
    [21-06-10 20:30:24.3702] Slim::Networking::SqueezeNetwork::init (39) SqueezeNetwork Init
    [21-06-10 20:30:24.3724] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 20:30:29.8584] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 20:30:29.8591] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:30:29.8599] Slim::Networking::SqueezeNetwork::login (248) We've failed to log in a few moments ago, or are still waiting for a response. Let's not try again just yet, we don't want to hammer mysqueezebox.com.
    [21-06-10 20:30:29.8604] Slim::Networking::SqueezeNetwork::PrefSync::_init_error (126) Unable to get list of prefs to sync with mysqueezebox.com, sync is disabled: An unexpected error occurred while validating your mysqueezebox.com account. Please make sure network connectivity is working fine.
    [21-06-10 20:30:48.0010] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:30:48.0015] Slim::Networking::SqueezeNetwork::login (248) We've failed to log in a few moments ago, or are still waiting for a response. Let's not try again just yet, we don't want to hammer mysqueezebox.com.
    [21-06-10 20:30:54.0025] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:30:54.0032] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 20:30:54.4312] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Timed out waiting for data
    [21-06-10 20:30:54.4318] Slim::Networking::SqueezeNetwork::_init_error (156) Unable to login to mysqueezebox.com, sync is disabled: Timed out waiting for data (https://www.mysqueezebox.com)
    [21-06-10 20:30:54.4329] Slim::Networking::SqueezeNetwork::_init_error (172) mysqueezebox.com sync init failed: Timed out waiting for data, will retry in 300 (https://www.mysqueezebox.com)
    [21-06-10 20:30:59.0035] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:30:59.0039] Slim::Networking::SqueezeNetwork::login (248) We've failed to log in a few moments ago, or are still waiting for a response. Let's not try again just yet, we don't want to hammer mysqueezebox.com.
    [21-06-10 20:31:24.0660] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Timed out waiting for data
    • Synology D218+ running LMS 8.1.1 in Docker container
    • 1 x Squeezebox Touch, 2 x Squeezebox Radios, 1 x Squeezebox Receiver, Squeeze Player & Squeeze Ctrl apps on Galaxy Tab S5e & Galaxy A40
    • Raspberry Pi 4B 8GB (with 7" Touchscreen in case & Flirc USB IR dongle) & Pi 4B 8GB in Flirc case, both running piCorePlayer 8.0.0 & LMS 8.1.1, connecting over Wi-fi to DS218+, or LMS library copy on 2TB USB hard drive plugged into Pi when no Wi-fi available
    • LMS library of ALAC, ACC/M4A and MP3 files

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

    Cant connect to mysqueezebox.com"unexpect error - check your networking"

    > [21-06-10 20:29:48.0243] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as myemail (AT) myprovider (DOT) com
    > [21-06-10 20:29:48.1141] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Invalid mysqueezebox.com username or password.


    This means the credentials you're using are wrong. Are you using any
    special characters in the password?

    > - LMS 7.9.1-168 running on Synology D218+ connected to Wi-Fi router
    > via LAN cable


    But was the above using this LMS or the dockerized version?

  7. #67
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    4,521
    Quote Originally Posted by mherger View Post
    > [21-06-10 20:29:48.0243] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as myemail (AT) myprovider (DOT) com
    > [21-06-10 20:29:48.1141] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Invalid mysqueezebox.com username or password.


    This means the credentials you're using are wrong. Are you using any
    special characters in the password?
    I think that was deliberate to show what happens in different circumstances.
    The fact that it failed differently when the credentials were wrong implies that it really is managing to reach mysqueezebox.
    Indeed at one point there is:
    Code:
    [21-06-10 20:30:24.3674] Slim::Networking::SqueezeNetwork::_login_done (416) Logged into SN OK
    So it looks like it can work ... but just after that it shows more failures.
    All very strange.
    Paul Webster
    http://dabdig.blogspot.com
    Author of "Now Playing" plugins covering Radio France (FIP etc), PlanetRadio (Bauer - Kiss, Absolute, Scala, JazzFM etc), KCRW, Supla Finland, ABC Australia, CBC/Radio-Canada and RTE Ireland

  8. #68
    Senior Member
    Join Date
    Jan 2012
    Posts
    117
    Quote Originally Posted by mherger View Post
    > [21-06-10 20:29:48.0243] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as myemail (AT) myprovider (DOT) com
    > [21-06-10 20:29:48.1141] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Invalid mysqueezebox.com username or password.


    This means the credentials you're using are wrong. Are you using any
    special characters in the password?
    As was explained above the long paste of code - and as Paul suggested - I attempted various types of credentials including incorrect passwords and user names to see what the debug log recorded. Only the final errors in that block of code related to the correct credentials being entered

    Quote Originally Posted by mherger View Post

    > - LMS 7.9.1-168 running on Synology D218+ connected to Wi-Fi router
    > via LAN cable


    But was the above using this LMS or the dockerized version?
    My signature describes my typical setup of 7.9 in Package Centre which can log into mysqueezebox with no problems at all.

    All the logs I have been posting and the issue of not being to login to mysqueezebox relate to the 8.1 Docker installation on my Synology, which I have setup and tested as something I will eventually migrate to at the point I either choose to upgrade Perl on the Synology, or move up to DSM7. Trying to iron all the problems out now, so it's a smooth transition once it's time to move.

    Incidentally, there are no further entries in the log showing further attempts by LMS to login into mysqueezebox.com since 20:31 GMT, so I think LMS only makes one attempt to retry the login. This is why I'm wondering what the point of waiting to see if it updates is - not so sure it is a timing issue:
    Code:
    [21-06-10 20:30:54.0032] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 20:30:54.4312] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Timed out waiting for data
    [21-06-10 20:30:54.4318] Slim::Networking::SqueezeNetwork::_init_error (156) Unable to login to mysqueezebox.com, sync is disabled: Timed out waiting for data (https://www.mysqueezebox.com)
    [21-06-10 20:30:54.4329] Slim::Networking::SqueezeNetwork::_init_error (172) mysqueezebox.com sync init failed: Timed out waiting for data, will retry in 300 (https://www.mysqueezebox.com)
    [21-06-10 20:30:59.0035] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 20:30:59.0039] Slim::Networking::SqueezeNetwork::login (248) We've failed to log in a few moments ago, or are still waiting for a response. Let's not try again just yet, we don't want to hammer mysqueezebox.com.
    [21-06-10 20:31:24.0660] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Timed out waiting for data
    Cheers

    Andy
    • Synology D218+ running LMS 8.1.1 in Docker container
    • 1 x Squeezebox Touch, 2 x Squeezebox Radios, 1 x Squeezebox Receiver, Squeeze Player & Squeeze Ctrl apps on Galaxy Tab S5e & Galaxy A40
    • Raspberry Pi 4B 8GB (with 7" Touchscreen in case & Flirc USB IR dongle) & Pi 4B 8GB in Flirc case, both running piCorePlayer 8.0.0 & LMS 8.1.1, connecting over Wi-fi to DS218+, or LMS library copy on 2TB USB hard drive plugged into Pi when no Wi-fi available
    • LMS library of ALAC, ACC/M4A and MP3 files

  9. #69
    Senior Member
    Join Date
    Jan 2012
    Posts
    117
    Quote Originally Posted by Paul Webster View Post
    I think that was deliberate to show what happens in different circumstances.
    The fact that it failed differently when the credentials were wrong implies that it really is managing to reach mysqueezebox.
    Indeed at one point there is:
    Code:
    [21-06-10 20:30:24.3674] Slim::Networking::SqueezeNetwork::_login_done (416) Logged into SN OK
    Yes, Paul is correct. As explained above my long copy and paste of code, I deliberately entered wrong credentials to see what debug logs were recorded. I don't doubt that it's reaching mysqueezebox.com - but I'm hoping I can find a solution to why LMS logs show I'm not logged in and doesn't show my Radio apps/shortcuts
    Quote Originally Posted by Paul Webster View Post
    So it looks like it can work ... but just after that it shows more failures.
    All very strange.
    Yes, it has me baffled, but I'd welcome suggestions from any users - particularly those using either 8.1, Docker or Synology environments. I'm interested by the multiple references to sync being disabled on the login attempts with the correct credentials - what could this mean?
    Code:
    [21-06-10 20:30:54.4318] Slim::Networking::SqueezeNetwork::_init_error (156) Unable to login to mysqueezebox.com, sync is disabled: Timed out waiting for data (https://www.mysqueezebox.com)
    [21-06-10 20:30:54.4329] Slim::Networking::SqueezeNetwork::_init_error (172) mysqueezebox.com sync init failed: Timed out waiting for data, will retry in 300 (https://www.mysqueezebox.com)
    Thanks

    Andy
    • Synology D218+ running LMS 8.1.1 in Docker container
    • 1 x Squeezebox Touch, 2 x Squeezebox Radios, 1 x Squeezebox Receiver, Squeeze Player & Squeeze Ctrl apps on Galaxy Tab S5e & Galaxy A40
    • Raspberry Pi 4B 8GB (with 7" Touchscreen in case & Flirc USB IR dongle) & Pi 4B 8GB in Flirc case, both running piCorePlayer 8.0.0 & LMS 8.1.1, connecting over Wi-fi to DS218+, or LMS library copy on 2TB USB hard drive plugged into Pi when no Wi-fi available
    • LMS library of ALAC, ACC/M4A and MP3 files

  10. #70
    Senior Member
    Join Date
    Jan 2012
    Posts
    117
    I just went to the mysqueezebox login screen in LMS 8.1, made no changes and simply clicked 'Apply', and as usual still no Radio apps. The log shows:
    Code:
    [21-06-10 21:51:26.1684] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 21:51:30.7161] Slim::Networking::SqueezeNetwork::PrefSync::_init_done (57) Got list of SN prefs to sync: 55 prefs
    [21-06-10 21:51:30.7431] Slim::Networking::SqueezeNetwork::PrefSync::syncDownGlobal (200) Requesting global sync down from SN: { since => "1623357364" }
    [21-06-10 21:51:30.8930] Slim::Networking::SqueezeNetwork::PrefSync::_syncDown_done (223) Sync down data from SN: { prefs => {}, timestamp => "1623361890" }
    Then I've cleared credentials and clicked apply. Log then shows:
    Code:
    [21-06-10 21:55:08.2569] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 21:55:08.2675] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 21:55:08.2688] Slim::Networking::SqueezeNetwork::Players::shutdown (75) SqueezeNetwork player list shutdown
    [21-06-10 21:55:08.3738] Slim::Networking::SqueezeNetwork::PrefSync::_init_done (57) Got list of SN prefs to sync: 55 prefs
    [21-06-10 21:55:12.0027] Slim::Networking::SqueezeNetwork::PrefSync::syncDownGlobal (200) Requesting global sync down from SN: { since => "1623361890" }
    [21-06-10 21:55:12.0031] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 21:55:12.0034] Slim::Networking::SqueezeNetwork::login (267) A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 21:55:12.0037] Slim::Networking::SqueezeNetwork::PrefSync::_syncDown_error (370) Global Sync Down failed: A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 21:55:38.0020] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 21:55:38.0032] Slim::Networking::SqueezeNetwork::login (248) We've failed to log in a few moments ago, or are still waiting for a response. Let's not try again just yet, we don't want to hammer mysqueezebox.com.
    Finally, I've re-entered correct credentials and this is the log:
    Code:
    [21-06-10 21:57:09.4177] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 21:57:09.4182] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 21:57:09.4191] Slim::Networking::SqueezeNetwork::login (267) A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 21:57:09.4198] Slim::Networking::SqueezeNetwork::PrefSync::_init_error (126) Unable to get list of prefs to sync with mysqueezebox.com, sync is disabled: A mysqueezebox.com account is required for this service. Please access Logitech Media Server Settings -> mysqueezebox.com with a web browser to configure.
    [21-06-10 21:57:09.4207] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 21:57:09.5320] Slim::Utils::Prefs::__ANON__ (592) SN session has changed, removing cookies
    [21-06-10 21:57:09.5325] Slim::Networking::SqueezeNetwork::_login_done (416) Logged into SN OK
    [21-06-10 21:57:09.5333] Slim::Networking::SqueezeNetwork::PrefSync::shutdown (151) SqueezeNetwork pref sync shutdown
    [21-06-10 21:57:09.5342] Slim::Networking::SqueezeNetwork::Players::shutdown (75) SqueezeNetwork player list shutdown
    [21-06-10 21:57:09.5351] Slim::Networking::SqueezeNetwork::init (39) SqueezeNetwork Init
    [21-06-10 21:57:09.5374] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 21:57:39.0052] Slim::Networking::SqueezeNetwork::_createHTTPRequest (369) Logging in to SqueezeNetwork to obtain session ID
    [21-06-10 21:57:39.0058] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 21:57:39.1628] Slim::Utils::Prefs::__ANON__ (592) SN session has changed, removing cookies
    [21-06-10 21:57:39.1637] Slim::Networking::SqueezeNetwork::_login_done (416) Logged into SN OK
    [21-06-10 21:57:39.1646] Slim::Networking::SqueezeNetwork::__ANON__ (378) Got SqueezeNetwork session ID
    [21-06-10 21:57:39.6007] Slim::Networking::SqueezeNetwork::_error (431) Unable to login to SN: Timed out waiting for data
    [21-06-10 21:57:39.6017] Slim::Networking::SqueezeNetwork::_init_error (156) Unable to login to mysqueezebox.com, sync is disabled: Timed out waiting for data (https://www.mysqueezebox.com)
    [21-06-10 21:57:39.6025] Slim::Networking::SqueezeNetwork::_init_error (172) mysqueezebox.com sync init failed: Timed out waiting for data, will retry in 300 (https://www.mysqueezebox.com)
    [21-06-10 22:02:49.0019] Slim::Networking::SqueezeNetwork::init (39) SqueezeNetwork Init
    [21-06-10 22:02:49.0028] Slim::Networking::SqueezeNetwork::login (271) Logging in to www.mysqueezebox.com as  myemail@myprovider.com
    [21-06-10 22:02:49.1719] Slim::Utils::Prefs::__ANON__ (592) SN session has changed, removing cookies
    [21-06-10 22:02:49.1723] Slim::Networking::SqueezeNetwork::_login_done (416) Logged into SN OK
    [21-06-10 22:02:49.1726] Slim::Networking::SqueezeNetwork::_init_done (80) Got SqueezeNetwork server time: 1623362569, diff: 0
    [21-06-10 22:02:49.2603] Slim::Networking::SqueezeNetwork::PrefSync::_init_done (57) Got list of SN prefs to sync: 55 prefs
    [21-06-10 22:02:52.1550] Slim::Networking::SqueezeNetwork::Players::_players_done (111) Got list of SN players: (
    But still only this one Radio app/shortcut, when 7.9 has multiple:
    Name:  2021-06-10 LMS 8.1 Home - Radio menu 2.JPG
Views: 52
Size:  14.4 KB

    Does this give any more clues?

    Thanks

    Andy
    • Synology D218+ running LMS 8.1.1 in Docker container
    • 1 x Squeezebox Touch, 2 x Squeezebox Radios, 1 x Squeezebox Receiver, Squeeze Player & Squeeze Ctrl apps on Galaxy Tab S5e & Galaxy A40
    • Raspberry Pi 4B 8GB (with 7" Touchscreen in case & Flirc USB IR dongle) & Pi 4B 8GB in Flirc case, both running piCorePlayer 8.0.0 & LMS 8.1.1, connecting over Wi-fi to DS218+, or LMS library copy on 2TB USB hard drive plugged into Pi when no Wi-fi available
    • LMS library of ALAC, ACC/M4A and MP3 files

Posting Permissions

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