Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 7 FirstFirst 12345 ... LastLast
Results 21 to 30 of 67
  1. #21
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,312

    LMS web interface keeps becomingunresponsive on Debian 10

    > Any way you can think of to diagnose the lock-ups in LMS that this
    > thread is actually about? It seems to be much better since I got the
    > July 24 build, but definitely isn't working nearly as well as it was on
    > Debian 9.


    bpa asked you to run in --failsafe mode. Did you do that? You mentioned
    this happened when you eg. skipped tracks. What kind of tracks is this?
    Any kind (local, remote)?

    --

    Michael

  2. #22
    Senior Member
    Join Date
    Jan 2009
    Location
    Los Angeles & London
    Posts
    808
    Michael

    Haven’t tried it in failsafe mode yet, but that won’t tell me where the problem lies particularly, just whether or not it’s in the core product.

    I realised that I’ve been streaming a bunch of music the last week or so using Spotty, and that’s been much better. Went back to my local library tonight and it started freezing again.

    I will try with failsafe, but I think it would also be useful to know which logging options would be worth cranking up to try to identify the cause.

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

    LMS web interface keeps becomingunresponsive on Debian 10

    > Haven’t tried it in failsafe mode yet, but that won’t tell me where the
    > problem lies particularly, just whether or not it’s in the core product.


    That's what is called "narrowing down a problem", isn't it?

    > I will try with failsafe, but I think it would also be useful to know
    > which logging options would be worth cranking up to try to identify the
    > cause.


    Without having any clue at all in what part of LMS the problem is,
    there's no specific logging option. And cranking all up will produce too
    much noise.

    --

    Michael

  4. #24
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    17,835
    Quote Originally Posted by osveda View Post
    @bpa: I put output of wget in cli in the posting above.

    I tested all day on it. I first installed a complete new system (raspbian) and LMS on top. It did not change anything, same slow navigation. Then I switched the SD-card to a new rpi and tested this one. The new rpi is navigating normally, much much faster then the old rpi. I don't know why, because the old rpi is nearly the same as the new rpi:
    old rpi: rpi 3 model B
    new rpi: rpi 3 model B+
    I'm a little confused about what you are doing (i.e. no details on test) and then editing old post does not help.

    1. From original description, your problem look to be network related and/or hardware related - this is different to OP issue and a bit of a thread hijack. If problem is not Pi hardware then source of problem can include cables, connected network devices (e.g. Powerline) and possibly but unlikely PSU.
    2. You have not given any details on your network setup - wired/wireless etc. Also check network interface statistics to see if any errors, timeouts , link resets appearing on "bad" system more than "good".
    3. Difference between a Pi3 B and Pi3 B+ is 15% CPU and big change in network interface - so dismissing the two cards as similar is not right as problem looks network related.( this blog shows network difference https://www.jeffgeerling.com/blog/20...nce-comparison )
    4. You have swapped SD card - this may not be the best way as "history" may be on the card going from one system to another. Not sure if Raspbian save some config/tuning info.
    5. To do like for like comparison swapping SD card is not enough you need to swap cables and PSU and stay in same location to make sure there is no other variable.
    6. No comparison tests done playing local music to see if problem have an internet aspect.
    Last edited by bpa; 2019-08-02 at 01:30.

  5. #25
    Senior Member
    Join Date
    Jan 2009
    Location
    Los Angeles & London
    Posts
    808
    Quote Originally Posted by mherger View Post
    > Haven’t tried it in failsafe mode yet, but that won’t tell me where the
    > problem lies particularly, just whether or not it's in the core product.


    That's what is called "narrowing down a problem", isn't it?

    > I will try with failsafe, but I think it would also be useful to know
    > which logging options would be worth cranking up to try to identify the
    > cause.


    Without having any clue at all in what part of LMS the problem is,
    there's no specific logging option. And cranking all up will produce too
    much noise.
    Okay, so I tried that. Started an album from the web interface and it started playing. A minute into the first track and the playlist hadn't populated. Skipped to the next track and it skipped immediately and the playlist populated. Then, several minutes into that track, tried to skip again using the web interface and it was about 10 seconds before LMS actually started playing track 3.

    So it's definitely in the core product.

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

    LMS web interface keeps becomingunresponsive on Debian 10

    > So it's definitely in the core product.

    Ok, that's good to know. Next you could run slimerver.pl with
    "--perfwarn=0.5". That would log stuff which took longer than half a
    second to perfmon.log.

    --

    Michael

  7. #27
    Junior Member
    Join Date
    Jul 2019
    Posts
    4
    Quote Originally Posted by bpa View Post
    (...)
    1. From original description, your problem look to be network related and/or hardware related - this is different to OP issue and a bit of a thread hijack.
    You are right, sorry for that. I made a last update in my former post and will leave it with that.

  8. #28
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    17,835
    Quote Originally Posted by osveda View Post
    You are right, sorry for that. I made a last update in my former post and will leave it with that.
    OK but if you want to follow up it is better to start a new thread of your own as it is difficult to follow two different problem in the same thread.
    Also it is not always good to significantly edit old posts as some users use email to read the forum and updated posts do not show up in the email feed. Update old post maybe to correct typos or add some addtional but non essential info.
    Last edited by bpa; 2019-08-02 at 13:28.

  9. #29
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    17,835
    Quote Originally Posted by osveda View Post
    @bpa: I put output of wget in cli in the posting above.

    I tested all day on it. I first installed a complete new system (raspbian) and LMS on top. It did not change anything, same slow navigation. Then I switched the SD-card to a new rpi and tested this one. The new rpi is navigating normally, much much faster then the old rpi. I don't know why, because the old rpi is nearly the same as the new rpi:
    old rpi: rpi 3 model B
    new rpi: rpi 3 model B+

    *Update one day later:*
    new rpi worked nice for a day and now also navigating slower and slower. I removed it and the cpu felt very hot. I switched SD again to old rpi and hooked old rpi to electric socket and internet. Now LMS is working great again, navigating is quick and instant.

    *My conclusion:*
    LMS is not suitable (any more) to work on a rpi. rpi is getting too hot and I presume this is causing the system to slow down one way or another.
    Lots of users use rpi with LMS no problems and especially and RPI3 is plenty powerful for most cases. Are you doing something unusual such as transcoding, resampling, image resizing etc.

  10. #30
    Senior Member
    Join Date
    Jan 2009
    Location
    Los Angeles & London
    Posts
    808
    Quote Originally Posted by mherger View Post
    > So it's definitely in the core product.

    Ok, that's good to know. Next you could run slimerver.pl with
    "--perfwarn=0.5". That would log stuff which took longer than half a
    second to perfmon.log.
    Code:
    [19-08-02 17:08:27.2705] Logging Notify       >  0.50000s
    [19-08-02 17:08:27.2707] Logging Request      >  0.50000s
    [19-08-02 17:08:27.2708] Logging IO           >  0.50000s
    [19-08-02 17:08:27.2709] Logging Async HTTP   >  0.50000s
    [19-08-02 17:08:27.2710] Logging Scheduler    >  0.50000s
    [19-08-02 17:08:27.2712] Logging Timer        >  0.50000s
    [19-08-02 17:08:27.2713] Logging Page Build   >  0.50000s
    [19-08-02 17:08:27.2714] Logging AnyEvent CB  >  0.50000s
    [19-08-02 17:08:27.2715] Logging IR Delay     >  0.50000s
    [19-08-02 17:08:27.2716] Logging Template     >  0.50000s
    [19-08-02 17:08:27.2717] Logging DB Access    >  0.50000s
    [19-08-02 17:08:32.1099] Request      0.62725 : Plugins::Spotty::Connect::_connectEvent
    [19-08-02 17:08:32.1120] IO           0.63400 : Slim::Web::HTTP::processHTTP
    [19-08-02 17:08:33.4516] Request      1.31422 : Plugins::Spotty::Connect::_connectEvent
    [19-08-02 17:08:33.4534] IO           1.31720 : Slim::Web::HTTP::processHTTP
    [19-08-02 17:08:34.7415] Request      1.26792 : Plugins::Spotty::Connect::_connectEvent
    [19-08-02 17:08:34.7434] IO           1.27143 : Slim::Web::HTTP::processHTTP
    [19-08-02 17:09:34.4085] Page Build  30.11427 : Page: music/93ceefd8/cover_240x240_m
    [19-08-02 17:09:34.4088] IO          30.11629 : Slim::Web::HTTP::processHTTP
    [19-08-02 17:10:50.0742] Page Build  30.02197 : Page: music/21343/cover.jpg
    [19-08-02 17:10:50.0747] IO          30.02361 : Slim::Web::HTTP::processHTTP
    [19-08-02 17:11:20.3023] Page Build  30.06126 : Page: music/21344/cover.jpg
    [19-08-02 17:11:20.3027] IO          30.06318 : Slim::Web::HTTP::processHTTP

Posting Permissions

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