Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 2 12 LastLast
Results 1 to 10 of 17
  1. #1
    Senior Member Diana's Avatar
    Join Date
    Sep 2006
    Location
    UK
    Posts
    328

    Official Spotify plugin / Spotify Protocol Handler suddenly no longer working

    I was using the Spotify app this morning (it normally works flawlessly), and found it was failing to connect to my playlists. I went to the LMS Web Interface, and this was extremely sluggish, failing to load pages properly. After a lot of fruitless investigation, I decided to upgrade LMS to the newly released 7.9.0. This installed OK; and I cleared and rescanned the library. But the problems persisted.

    After restarting the Linux box (Debian Wheezy) that LMS runs on, the web interface was responsive as normal. But as soon as I try to open the Spotify app, the web gui became very unresponsive.

    After another reboot, the Spotify app opened after a long delay, but when I tried to open my playlists the web gui again became totally unresponsive.

    This is the section of the server log after the last restart:

    [17-07-05 10:45:59.6150] main::init (388) Starting Logitech Media Server (v7.9.0, 1488878280, Wed Mar 8 14:27:16 UTC 2017) perl 5.014002 - i486-linux-gnu-thread-multi-64int
    [17-07-05 10:51:41.3675] Slim::Formats::XML::gotErrorViaHTTP (310) Error: getting http://www.mysqueezebox.com/api/spotify/v1/opml
    Timed out waiting for data
    [17-07-05 10:51:41.3724] Slim::Web::Template::SkinManager::_fillTemplate (337) Error: file error - recursion into '/usr/share/squeezeboxserver/HTML/Default/xmlbrowser.html'
    [17-07-05 10:51:41.4137] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::Async::_async_error failed:
    [17-07-05 11:15:20.1023] Slim::Formats::XML::gotViaHTTP (238) XML/JSON parse error: unexpected end of string while parsing JSON string, at character offset 41377 (before "(end of string)") at /usr/share/perl5/Slim/Formats/XML.pm line 324.
    [17-07-05 11:15:20.1065] Slim::Web::Template::SkinManager::_fillTemplate (337) Error: file error - recursion into '/usr/share/squeezeboxserver/HTML/Default/xmlbrowser.html'
    [17-07-05 11:16:45.5083] Slim::Plugin::MusicMagic::Plugin::_musicipError (528) MusicIP: http error, no response.


    Further investigation revealed that the Spotify Protocol Handler (SPH) was reporting I was not logged in to Spotify. I uninstalled and reinstalled the Official Spotify App. I rebooted the server, and the LMS GUI behaved as normal. I logged back in to Spotify in the SPH settings.

    I was able to use my music library, including MusicIP mixes, entirely normally, from both the web interface and my Squeezebox Classics. But if I selected the Spotify App on the web interface or on any device, I was unable to use Spotify; and the LMS web gui became very unresponsive. SPH was again reporting that I was not logged in to Spotify. I was able to log in again, and after a reboot I was still logged in. I appear to stay logged in as long as I don't use the Spotify app!

    When I looked at the server log again, I saw further errors:

    [17-07-05 16:47:43.8936] main::init (388) Starting Logitech Media Server (v7.9.0, 1488878280, Wed Mar 8 14:27:16 UTC 2017) perl 5.014002 - i486-linux-gnu-thread-multi-64int
    [17-07-05 16:52:26.1923] Slim::Plugin::MusicMagic::Plugin::_musicipError (528) MusicIP: http error, no response.
    [17-07-05 16:54:16.7705] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling Slim::Web::HTTP:rocessHTTP: illegal file descriptor or filehandle (either no attached file descriptor or illegal value): at /usr/share/perl5/Slim/Networking/IO/Select.pm line 134.
    ; fh=Slim::Web::HTTP::ClientConn=GLOB(0xc77deb0)
    [17-07-05 16:57:16.5733] Slim::Web::Template::SkinManager::_fillTemplate (337) Error: file error - recursion into '/usr/share/squeezeboxserver/HTML/Default/xmlbrowser.html'
    [17-07-05 16:57:16.5829] Slim::Web::Template::SkinManager::_fillTemplate (337) Error: file error - recursion into '/usr/share/squeezeboxserver/HTML/Default/xmlbrowser.html'
    [17-07-05 16:57:16.5842] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::Async::HTTP::_http_read_timeout failed: illegal file descriptor or filehandle (either no attached file descriptor or illegal value): at /usr/share/perl5/Slim/Networking/IO/Select.pm line 134.
    [17-07-05 16:57:21.6137] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling Slim::Networking::Async::HTTP::_http_read_body: illegal file descriptor or filehandle (either no attached file descriptor or illegal value): at /usr/share/perl5/Slim/Networking/IO/Select.pm line 134.
    ; fh=Slim::Networking::Async::Socket::HTTP=GLOB(0xde 94d6c)



    I'm out of my depth here, and I'd be grateful for any advice or suggestions about getting Spotify working again.

    Thanks in advance.

  2. #2
    Senior Member
    Join Date
    Apr 2013
    Posts
    159
    The SPH is still working fine for me here in Los Angeles.

  3. #3
    Senior Member Diana's Avatar
    Join Date
    Sep 2006
    Location
    UK
    Posts
    328
    Quote Originally Posted by usc95 View Post
    The SPH is still working fine for me here in Los Angeles.
    Good. And that suggests my issue isn't a result of Spotify changing their API. But that still leaves me floundering for ideas about how to restore my set up to its usual full working order.
    I'd be really grateful for suggestions about how to approach fixing it.

  4. #4
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,681

    Official Spotify plugin / Spotify Protocol Handler suddenly no longer working

    Forget about the current solutions and switch over to Spotty.

    http://forums.slimdevices.com/showthread.php?t=107418

    The subject is outdated. You don't need to be brave to use it any more
    Michael

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

  5. #5
    Senior Member Diana's Avatar
    Join Date
    Sep 2006
    Location
    UK
    Posts
    328
    Quote Originally Posted by mherger View Post
    Forget about the current solutions and switch over to Spotty.
    Thanks, Michael. I've followed the instructions, and installed Spotty (and removed the old plugins as per instructions). I had to add my Spotify login details manually, as I couldn't get the automated process to work.
    When I selected the Spotty app in the LMS webUI, the web page took ages to load (which is what has been happening all day). But it did open the menu eventually.

    However, when I selected one of the menu items (e.g. 'What's New' or 'Playlists'), the web page waited interminably for the the server to respond, but the page did not load.

    The server log shows this:

    [17-07-05 20:56:57.6850] main::init (388) Starting Logitech Media Server (v7.9.0, 1488878280, Wed Mar 8 14:27:16 UTC 2017) perl 5.014002 - i486-linux-gnu-thread-multi-64int
    [17-07-05 20:57:04.4099] Plugins::Spotty::Plugin::initPlugin (99) Please update to Logitech Media Server 7.9.1 if you want to use seeking in Spotify tracks.
    [17-07-05 21:06:04.3388] Plugins::Spotty::API::__ANON__ (1003) error: Timed out waiting for data
    [17-07-05 21:06:04.3872] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::Async::_async_error failed:
    [17-07-05 21:06:04.3882] Plugins::Spotty::API::__ANON__ (1003) error: Timed out waiting for data
    [17-07-05 21:06:04.3886] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::Async::_async_error failed: Can't call method "code" on an undefined value at /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/API.pm line 1005.
    [17-07-05 21:06:04.3894] Plugins::Spotty::API::__ANON__ (1003) error: Timed out waiting for data
    [17-07-05 21:06:04.3898] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::Async::_async_error failed: Can't call method "code" on an undefined value at /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/API.pm line 1005.
    [17-07-05 21:07:39.9353] Slim::Plugin::MusicMagic::Plugin::_musicipError (528) MusicIP: http error, no response.
    [17-07-05 21:09:15.5379] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling Slim::Networking::Async::HTTP::_http_read_body: illegal file descriptor or filehandle (either no attached file descriptor or illegal value): at /usr/share/perl5/Slim/Networking/IO/Select.pm line 134.
    ; fh=Slim::Networking::Async::Socket::HTTPS=GLOB(0xc e2aa54)


    Do you have any ideas?


    [UPDATE] Mmm... Despite the webUI not working, Spotty plays beautifully on my Squeezebox Classics, either using the remote control or using iPeng. I've absolutely no idea why the webUI is struggling so badly.
    Last edited by Diana; 2017-07-05 at 14:12.

  6. #6
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,681
    Could you please try the latest 7.9.1 nightly build? There have been some changes in how SSL connections (and in particular connection failures) are being handled. Might be worth a try.
    Michael

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

  7. #7
    Senior Member Diana's Avatar
    Join Date
    Sep 2006
    Location
    UK
    Posts
    328
    Quote Originally Posted by mherger View Post
    Could you please try the latest 7.9.1 nightly build? There have been some changes in how SSL connections (and in particular connection failures) are being handled. Might be worth a try.
    Thanks for the suggestion, Michael. I've just installed 7.9.1, but when I try to open Spotty>Playlists the webUI waits and waits for the server but doesn't load. The log again says

    [17-07-06 06:15:27.5797] main::init (387) Starting Logitech Media Server (v7.9.1, 1498799744, Sat Jul 1 04:29:28 UTC 2017) perl 5.014002 - i486-linux-gnu-thread-multi-64int
    [17-07-06 06:17:34.9033] Plugins::Spotty::API::__ANON__ (1003) error: Timed out waiting for data
    [17-07-06 06:17:34.9369] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::Async::_async_error failed:
    [17-07-06 06:17:34.9379] Plugins::Spotty::API::__ANON__ (1003) error: Timed out waiting for data
    [17-07-06 06:17:34.9383] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::Async::_async_error failed: Can't call method "code" on an undefined value at /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/API.pm line 1005.
    [17-07-06 06:17:34.9393] Plugins::Spotty::API::__ANON__ (1003) error: Timed out waiting for data
    [17-07-06 06:17:34.9399] Slim::Utils::Timers::__ANON__ (273) Error: Timer Slim::Networking::Async::_async_error failed: Can't call method "code" on an undefined value at /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/API.pm line 1005.
    [17-07-06 06:18:00.0561] Slim::Plugin::MusicMagic::Plugin::_musicipError (528) MusicIP: http error, no response.

  8. #8
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,681

    Official Spotify plugin / SpotifyProtocol Handler suddenly no longer working

    > Thanks for the suggestion, Michael. I've just installed 7.9.1, but when
    > I try to open Spotty>Playlists the webUI waits and waits for the server
    > but doesn't load. The log again says


    Is it limited to the web UI and Playlists again? Would other menus work?

    Do you have a large number of playlists? It's odd that you'd experience
    the same issues with two totally independent implementations. Please
    enable debug logging for plugin.spotty (Settings/Advanced/Logging),
    re-try, then upload the server.log file again. Thanks!

    > [17-07-06 06:17:34.9383] Slim::Utils::Timers::__ANON__ (273) Error:
    > Timer Slim::Networking::Async::_async_error failed: Can't call method
    > "code" on an undefined value at
    > /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/API.pm
    > line 1005.


    This issue should be fixed in Spotty 1.0.0 - available for download now.

    --

    Michael

  9. #9
    Senior Member Diana's Avatar
    Join Date
    Sep 2006
    Location
    UK
    Posts
    328
    Quote Originally Posted by mherger View Post
    Is it limited to the web UI and Playlists again? Would other menus work?
    Yes the problems are just with the Web UI (whether accessed from the Linux box the server runs on, or from a Mac over the LAN). But not everything is affected:
    - When I open the LMS Web UI, the data transfers slowly from the server, but the Home page eventually opens
    - All sections of "My Music" run normally, with no undue latency for page loads.
    - "Radios" links with larger numbers of items are very slow to load (e.g. Music>Folk>Stations(26+) )
    - navigation round the Web UI seems to get less and less responsive as I use it. This is only rectified by a server restart.
    - All submenus of Spotty, not just Playlists, are very unresponsive. (e.g. "What's New" waited interminably, and did not load.)

    Quote Originally Posted by mherger View Post
    Do you have a large number of playlists?
    Yes, but see above - the problem is not limited to 'Playlists'

    Quote Originally Posted by mherger View Post
    Please enable debug logging for plugin.spotty (Settings/Advanced/Logging), re-try, then upload the server.log file again.
    I've done this, but it generates an enormous log file. (And the file includes Spotify tokens.) I've edited out what I think is a typical section, but it's still a very large text file. Is there some way of passing it to you without cluttering up the forum pages with hundreds of lines of log?

    Thanks, as always, for all your help with this. (And I have to say that your Spotty plugin, which I'm using just fine on my SB Classics via remotes or iPeng, is utterly brilliant, with great stability and sound quality. Thanks ever so much for building it!)

  10. #10
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    19,681

    Official Spotify plugin / SpotifyProtocol Handler suddenly no longer working

    >> Do you have a large number of playlists?
    > Yes, but see above - the problem is not limited to 'Playlists'


    From your description I actually believe this has nothing to do with
    Spotify or Spotty at all, but is a larger issue with the web UI. Would
    you have different browsers to test with? Would you see the same issue
    on various browsers or from various clients in your network?

    > I've done this, but it generates an enormous log file. (And the file
    > includes Spotify tokens.) I've edited out what I think is a typical


    There should be no usable tokens in the log file imho. Otherwise I'll
    have to fix this.

    > section, but it's still a very large text file. Is there some way of
    > passing it to you without cluttering up the forum pages with hundreds of
    > lines of log?


    https://www.dropbox.com/request/T3RctyzGgNg0oFDubq6a

    --

    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
  •