Home of the Squeezebox™ & Transporter® network music players.
Page 63 of 73 FirstFirst ... 13536162636465 ... LastLast
Results 621 to 630 of 722
  1. #621
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,749

    [Announce] Spotty 2.8.x - SpotifyConnect for your Squeezebox

    > There has been a problem running the Spotty helper application.
    > Most likely your operating system and/or platform is not supported.
    > Please report the following details to me:


    What happens if you run

    /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64

    from the command line?

    --

    Michael

  2. #622
    Junior Member
    Join Date
    Sep 2009
    Posts
    9
    Quote Originally Posted by mherger View Post
    > There has been a problem running the Spotty helper application.
    > Most likely your operating system and/or platform is not supported.
    > Please report the following details to me:


    What happens if you run

    /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64

    from the command line?
    I get told to specify the device name and the list of options is listed.

  3. #623
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,749

    [Announce] Spotty 2.8.x - SpotifyConnect for your Squeezebox

    >> What happens if you run
    >>
    >> /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
    >>
    >> from the command line?

    >
    > I get told to specify the device name and the list of options is listed.


    Which means it is there and does work. Hmm... No idea what happens
    there. It's the exact path that in the log is mentioned as not working.

    What if you run

    ..../spotty-x86_64 -n test --check

    ?

    --

    Michael

  4. #624
    Junior Member
    Join Date
    Sep 2009
    Posts
    9
    Quote Originally Posted by mherger View Post
    >> What happens if you run
    >>
    >> /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
    >>
    >> from the command line?

    >
    > I get told to specify the device name and the list of options is listed.

    What if you run

    ..../spotty-x86_64 -n test --check
    ok spotty v0.20.0
    {"debug":false,"lms-auth":true,"ogg-direct":true,"version":"0.20.0","volume-normalisation":true}
    [

  5. #625
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,749

    [Announce] Spotty 2.8.x - SpotifyConnect for your Squeezebox

    >> ..../spotty-x86_64 -n test --check
    >>

    > ok spotty v0.20.0
    > {"debug":false,"lms-auth":true,"ogg-direct":true,"version":"0.20.0","volume-normalisation":true}


    That's perfect. I don't really know why Spotty wouldn't work then...

    --

    Michael

  6. #626
    Junior Member
    Join Date
    Oct 2019
    Posts
    4

    Unable to enter spotify credentials

    Hello

    I have no chance with using Spotty since last Summer. After numerous restarts I have succeed to install the plugin. However, now the LMS crashes when I try to enter the spotify credentials at the parameters page, I see the following in the server.log:

    [19-10-25 18:14:18.1582] Plugins::Spotty::Settings::Auth::handler (75) Authorization failed : called `Result::unwrap()` on an `Err` value: Os { code: 110, kind: TimedOut, message: "Operation timed out" } : thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 110, kind: TimedOut, message: "Operation timed out" }', src/libcore/result.rs:997:5
    note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

    When trying from the command line ./spotty-x86_64 -n test --check I get

    ok spotty v0.20.0
    {"debug":false,"lms-auth":true,"ogg-direct":true,"version":"0.20.0","volume-normalisation":true}

    An educated opinion about what is going on?

    Regards,
    Anatoli
    Last edited by ai1; 2019-10-25 at 09:28.

  7. #627
    Senior Member sle118's Avatar
    Join Date
    Dec 2009
    Location
    Quebec City, Canada
    Posts
    524

    socketwrapper dies from watchdog, tracks doesn't play fully

    I've been banging my head against the wall on an issue which prevents me from enjoying Spotty. First I thought something was wrong with my SqueezeAmp and started looking in the logs to see if I could get some insights. Eventually, I realized something was wrong on the server side.

    Fast forward: I ended up running the squeezebox server from the command line to get the output from the socket wrapper, as it seemed that it was somehow terminating abruptly. What seems to happen is:
    • Socket wrapper opens up spotty
    • socket wrapper transfers several data chunks, so far so good
    • After some time, the socket wrapper stalls and watchdog kills the process


    Here is the extracted socket wrapper log:
    Code:
    SW: 2019-10-25 12:21:35.282 Socketwrapper 1.11beta
    SW: 2019-10-25 12:21:35.283 -i 0 -o 51681 -c "C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\Spotty\Bin\MSWin32-x86-multi-thread\spotty.exe" -n Squeezebox -c "C:\ProgramData\Squeezebox\Cache\spotty\8ba0b816" --verbose --single-track "spotify://track:6lhDKRxI7fjL1Jao6erY1n" --bitrate 320 --disable-discovery --disable-audio-cache --pass-through
    SW: 2019-10-25 12:21:35.294 Init complete.
    SW: 2019-10-25 12:21:35.295 # =input== =output= ==type== ===details===
    SW: 2019-10-25 12:21:35.295 0 00000008 00000114  PROCESS "C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\Spotty\Bin\MSWin32-x86-multi-thread\spotty.exe" -n Squeezebox -c "C:\ProgramData\Squeezebox\Cache\spotty\8ba0b816" --verbose --single-track "spotify://track:6lhDKRxI7fjL1Jao6erY1n" --bitrate 320 --disable-discovery --disable-audio-cache --pass-through 
    SW: 2019-10-25 12:21:35.295 1 00000110 00000120  THREAD  Output Socket
    SW: 2019-10-25 12:21:35.296 MoveDataThreadProc for step 1 started.
    SW: 2019-10-25 12:21:35.297 MoveDataThreadProc for step 1 about to call ReadFile.
    SW: 2019-10-25 12:21:36.142 MoveDataThreadProc for step 1 got 7986 bytes, about to write data.
    SW: 2019-10-25 12:21:36.299 MoveDataThreadProc for step 1 about to call ReadFile.
    SW: 2019-10-25 12:21:36.299 MoveDataThreadProc for step 1 got 8192 bytes, about to write data.
    [... repeat 2 lines above, many times ... ]
    SW: 2019-10-25 12:21:41.286 MoveDataThreadProc for step 1 about to call ReadFile.
    SW: 2019-10-25 12:21:41.286 MoveDataThreadProc for step 1 got 8192 bytes, about to write data.
    SW: 2019-10-25 12:21:41.286 MoveDataThreadProc for step 1 about to call ReadFile.
    SW: 2019-10-25 12:21:41.286 MoveDataThreadProc for step 1 got 8192 bytes, about to write data.
    SW: 2019-10-25 12:21:55.305 Watchdog expired - Thread for step 1 stalled.
    SW: 2019-10-25 12:21:55.305 Tidying up
    SW: 2019-10-25 12:21:55.307 Watchdog expired
    SW: 2019-10-25 12:21:55.307 Waiting for process step 0 to terminate
    SW: 2019-10-25 12:21:57.308 Tidying up - process for step 0 hasn't died or wait failed. wr=258 :0
    SW: 2019-10-25 12:21:59.323 Tidying up - Thread for step 1 hasn't died.
    SW: 2019-10-25 12:21:59.323 Thread for step 1 streamed    603 blocks totalling 0046DE64 (4644452) bytes
    SW: 2019-10-25 12:21:59.323 Exitcode for Thread 1 Code=259
    SW: 2019-10-25 12:21:59.338 Socketwrapper has terminated.
    This results in a cascading effect which causes Slim::Player::Source::_readNextChunk to detect the end of the stream and report "end of file or error on socket", with a position that represents the number of bytes read. At this point, the streaming controller changes to a new streaming state : STREAMOUT. The player will keep going until its internal buffer is empty, and the next track will start.

    Unfortunately, and with a variety of players (duet, boom, etc), this most of the time result in a song that gets cut out.

    Is there any way to get some logging out of spotty or its underlying librespot? This might help me unearth the actual root cause, as for now I'm in the dark.



    *** EDIT: Additional test done ***
    I tried running the following command
    Code:
    "C:\ProgramData\Squeezebox\Cache\InstalledPlugins\Plugins\Spotty\Bin\MSWin32-x86-multi-thread\spotty.exe" -n Squeezebox -c "C:\ProgramData\Squeezebox\Cache\spotty\8ba0b816" --verbose --single-track "spotify://track:6lhDKRxI7fjL1Jao6erY1n" --bitrate 320 --disable-discovery --disable-audio-cache --pass-through >test2.ogg
    The resulting file was 7 367 002 bytes, which seems to indicate that spotty itself can get the full content? If this is the case, then I am wondering what could be causing the socket wrapper to trigger watchdog?

    ** EDIT #2: More comprehension on the issue? **
    I dug into the socket wrapper code and now I wonder. The wrapper actually stops at "MoveDataThreadProc for step 1 got 8192 bytes, about to write data.", which seems to indicate that it got data from spotty and that it was waiting for the "receiver end" to read the data. What sits between the wrapper and the player? Why is it not accepting the data from the wrapper (and thus, from spotty.exe) ?
    Last edited by sle118; 2019-10-25 at 11:16. Reason: Additional test
    LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
    6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!

  8. #628
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,749

    [Announce] Spotty 2.8.x - SpotifyConnect for your Squeezebox

    > I have no chance with using Spotty since last Summer. After numerous
    > restarts I have succeed to install the plugin. However, now the LMS
    > crashes when I try to enter the spotify credentials at the parameters
    > page, I see the following in the server.log:


    What OS are you using? What hardware? Network configuration?

    >
    > [19-10-25 18:14:18.1582] Plugins::Spotty::Settings::Auth::handler (75)
    > Authorization failed : called `Result::unwrap()` on an `Err` value: Os {
    > code: 110, kind: TimedOut, message: "Operation timed out" } : thread
    > 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os {
    > code: 110, kind: TimedOut, message: "Operation timed out" }',
    > src/libcore/result.rs:997:5
    > note: Run with `RUST_BACKTRACE=1` environment variable to display a
    > backtrace.


    Might be a firewall or something blocking outgoing connections?

    --

    Michael

  9. #629
    Junior Member
    Join Date
    Oct 2019
    Posts
    4
    Quote Originally Posted by mherger View Post
    > I have no chance with using Spotty since last Summer. After numerous...

    What OS are you using? What hardware? Network configuration?

    >
    > [19-10-25 18:14:18.1582] Plugins::Spotty::Settings::Auth::handler (75)
    > Authorization failed : called `Result::unwrap()` on an `Err` value: Os {
    > code: 110, kind: TimedOut, message: "Operation timed out" } : thread
    > 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os {
    > code: 110, kind: TimedOut, message: "Operation timed out" }',
    > src/libcore/result.rs:997:5
    > note: Run with `RUST_BACKTRACE=1` environment variable to display a
    > backtrace.


    Might be a firewall or something blocking outgoing connections?

    --

    Michael
    Thank you very much for reacting so fast. Below is the information about the LMS on my Qnap NAS TS-251+. Sorry, do not understand what information about network configuration is needed. The NAS is behind the Orange Livebox modem/router, TCP ports 443 and 80 are forwarded to NAS at192.168.1.10. The following UPnP rules were configured automatically:
    Web Admin 192.168.1.10 8080 8080 TCP
    Secure Web Server 192.168.1.10 8081 8081 TCP
    libminiupnpc 192.168.1.10 51163 51163TCP
    ------------------------------
    Logitech Media Server Version : 7.9.2 - 1571644358 @ Mon Oct 21 10:21:50 CEST 2019
    Adresse IP du serveur : 192.168.1.10
    Port HTTP du serveur : 9001
    Système d'exploitation : QLMS 2.X (QNAP TurboStation) - FR - utf8
    Architecture de la plate-forme : x86_64-linux
    Version de Perl : 5.28.2 - x86_64-linux-thread-multi
    Audio::Scan : 1.02
    IO::Socket::SSL : 2.060
    Version de la base de données : DBD::SQLite 1.58 (sqlite 3.22.0)
    Platines identifiées : 2

  10. #630
    Senior Member pablolie's Avatar
    Join Date
    Feb 2006
    Location
    bay area, california.
    Posts
    1,203

    Spotty on Ubuntu 18.04?

    I am drawing blanks trying to get the Spotty plugin to start in Ubuntu 18.04. I pick it in the plug-in settings, restart the LMS, and yet it never comes up as an active plugin.

    The log file is weird and tells me nothing

    [19-10-25 14:27:36.2570] main::init (387) Starting Logitech Media Server (v7.9.1, 1522157629, Fri Mar 30 12:25:29 CEST 2018) perl 5.026001 - x86_64-linux-gnu-thread-multi
    [19-10-25 14:28:54.5465] Slim::Plugin::Extensions::Settings::handler (35) attempt to set params with band random number - ignoring
    [19-10-25 14:30:02.0488] main::init (387) Starting Logitech Media Server (v7.9.1, 1522157629, Fri Mar 30 12:25:29 CEST 2018) perl 5.026001 - x86_64-linux-gnu-thread-multi
    [19-10-25 14:31:03.3856] Slim::Plugin::Extensions::Settings::handler (35) attempt to set params with band random number - ignoring
    Last edited by pablolie; 2019-10-25 at 14:35.
    ...pablo
    Server: Win10 and LMS 8.2.0
    System: SB Touch -optical-> Benchmark DAC2HGC -AnalysisPlus Oval Copper XLR-> NAD M22 Power Amp -AnalysisPlus Black Mesh Oval-> KEF Reference 1
    Other Rooms: 2x SB Boom; 1x SB Radio; 1x SB Touch-> NAD D7050 -> KEF LS50 + Velodyne Minivee Sub
    Computer audio: workstation -USB-> audioengine D1 -> Grado RS1/Shure 1540

Posting Permissions

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