Home of the Squeezebox™ & Transporter® network music players.
Page 5 of 5 FirstFirst ... 345
Results 41 to 43 of 43
  1. #41
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    15,478
    Quote Originally Posted by Eisbaer2 View Post
    How can I determine that?
    After the next freezing I plan to connect my SBR to a LAN cable for several days and see if the problem still occurs. I only don't have LAN at the usual location of the SBR.

    By the way: you mentioned to uninstall applets. I think no applets are installed.
    The more I look at the log - the more it looks like everything is "normal" (i.e. I have seen similar logged messages on my SBR after connecting/disconnecting LMS / mysqeueezebox.com ) - just there is some sort of network disruption which needs to be characterised before it can be fixed.

    The usual way to get jmore info is to enable better logging through SBR Menu Settings/Advanced/Logging

    If squeezebox.server is set to DEBUG - the status of LMS / mysqueezebox.com connection is shown at intervals and if it changes messages are logged.

    To see the state of the network connections you could enable net.socket to DEBUG but this generates lots of messages but it should "pinpoint" any Wifi disconnection issue.

    I'd advise try setting squeezebox.server to DEBUG first.

    I

  2. #42
    Junior Member
    Join Date
    Dec 2017
    Posts
    21
    Quote Originally Posted by bpa View Post
    The more I look at the log - the more it looks like everything is "normal" (i.e. I have seen similar logged messages on my SBR after connecting/disconnecting LMS / mysqeueezebox.com ) - just there is some sort of network disruption which needs to be characterised before it can be fixed.

    The usual way to get jmore info is to enable better logging through SBR Menu Settings/Advanced/Logging

    If squeezebox.server is set to DEBUG - the status of LMS / mysqueezebox.com connection is shown at intervals and if it changes messages are logged.

    To see the state of the network connections you could enable net.socket to DEBUG but this generates lots of messages but it should "pinpoint" any Wifi disconnection issue.

    I'd advise try setting squeezebox.server to DEBUG first.

    I
    Short update: As suggested I enabled the DEBUG mode for net.socket and squeezebox.server. Until now I've had no more freezes for about 4 days. Great!
    I only have a new phenomenon: often the wrong web radio logo is shown. That can be solved by pressing FR or FF several times. Doesn't bother me much.
    Last edited by Eisbaer2; Today at 01:12.

  3. #43
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    15,478
    Quote Originally Posted by Eisbaer2 View Post
    Short update: As suggested I enabled the DEBUG mode for net.socket and squeezebox.server. Until now I've had no more freezes for about 4 days. Great!
    I only have a new phenomenon: often the wrong web radio logo is shown. That can be solved by pressing FR or FF several times. Doesn't bother me much.
    Enabling logging should not fix a problem - it has just changed the symptoms.

    The image issues sounds like the network request/response for new image is getting "lost" in your network connection and the FF/FR is just a manual way of repeating the requests. IIRC mysqueezebox.com does the image resizing - long delays can happen.

Tags for this Thread

Posting Permissions

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