Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 7 of 7
  1. #1
    Junior Member
    Join Date
    Dec 2020
    Posts
    6

    Squeezelite: slimproto_run error reading from socket: closed

    Hi,

    First post here!

    I'm just getting started with LMS, and have managed to get most things up and running. My question is about Squeezelite - when I run it with debug options,

    Code:
    ./squeezelite -d all=debug -n server_player
    it seems to constantly loop with the following:

    Code:
    [11:47:09.228303] slimproto:926 connected
    [11:47:09.228338] slimproto:937 local player
    [11:47:09.228349] sendHELO:142 mac: 70:85:c2:31:39:e9
    [11:47:09.228358] sendHELO:144 cap: CanHTTPS=1,Model=squeezelite,AccuratePlayPoints=1,HasDigitalOut=1,HasPolarityInversion=1,Firmware=v1.9.8-1287,ModelName=SqueezeLite,MaxSampleRate=44100,dsf,dff,alc,aac,ogg,ops,ogf,flc,aif,pcm,mp3,loc
    [11:47:09.641476] process:521 setd
    [11:47:09.641499] sendSETDName:248 set playername: server_player
    [11:47:09.641565] process:521 setd
    [11:47:09.641581] process:521 aude
    [11:47:09.641588] process_aude:415 enable spdif: 1 dac: 1
    [11:47:09.641653] process:521 audg
    [11:47:09.641675] process_audg:433 audg gainL: 0 gainR: 0 adjust: 1
    [11:47:09.743553] slimproto_run:572 error reading from socket: closed
    a couple of times per second. This is when nothing is playing, and LMS is running. It seems to successfully play music that is streamed to it from LMS, but I'm wondering if these constant disconnects are completely normal, or whether something is going wrong.

    Google searches for this error seem to show that it appears in other logs.

    For reference, I'm using the binary distribution squeezelite-pulse-1.9.8.1287-x86_64, and LMS in Docker (lmscommunity/logitechmediaserver:8.1.0-dev) running on the same host.

  2. #2
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    6,938
    Quote Originally Posted by hbq269 View Post
    Hi,

    First post here!

    I'm just getting started with LMS, and have managed to get most things up and running. My question is about Squeezelite - when I run it with debug options,

    Code:
    ./squeezelite -d all=debug -n server_player
    it seems to constantly loop with the following:

    Code:
    [11:47:09.228303] slimproto:926 connected
    [11:47:09.228338] slimproto:937 local player
    [11:47:09.228349] sendHELO:142 mac: 70:85:c2:31:39:e9
    [11:47:09.228358] sendHELO:144 cap: CanHTTPS=1,Model=squeezelite,AccuratePlayPoints=1,HasDigitalOut=1,HasPolarityInversion=1,Firmware=v1.9.8-1287,ModelName=SqueezeLite,MaxSampleRate=44100,dsf,dff,alc,aac,ogg,ops,ogf,flc,aif,pcm,mp3,loc
    [11:47:09.641476] process:521 setd
    [11:47:09.641499] sendSETDName:248 set playername: server_player
    [11:47:09.641565] process:521 setd
    [11:47:09.641581] process:521 aude
    [11:47:09.641588] process_aude:415 enable spdif: 1 dac: 1
    [11:47:09.641653] process:521 audg
    [11:47:09.641675] process_audg:433 audg gainL: 0 gainR: 0 adjust: 1
    [11:47:09.743553] slimproto_run:572 error reading from socket: closed
    a couple of times per second. This is when nothing is playing, and LMS is running. It seems to successfully play music that is streamed to it from LMS, but I'm wondering if these constant disconnects are completely normal, or whether something is going wrong.

    Google searches for this error seem to show that it appears in other logs.

    For reference, I'm using the binary distribution squeezelite-pulse-1.9.8.1287-x86_64, and LMS in Docker (lmscommunity/logitechmediaserver:8.1.0-dev) running on the same host.
    It should definitively not happen. There is a problem with your network and connection breaks all the time. SB devices are supposed to keep an open socket with LMS all the time
    LMS 8.1.x on Odroid-C4 - SqueezeAMP!, 5xRadio, 5xBoom, 2xDuet, 1xTouch, 1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

  3. #3
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    20,304
    Since you run Docker, it maybe a Docker setup issue. I suggest posting on the Docker thread ( with a link to this thread) and see if another Docker users has seen it.

    https://forums.slimdevices.com/showt...tainer-for-LMS

    Provide details of the OS / Platform on which LMS/Docker is running and details on the squeezelite player OS & platform.

  4. #4
    Junior Member
    Join Date
    Dec 2020
    Posts
    6
    Quote Originally Posted by bpa View Post
    Since you run Docker, it maybe a Docker setup issue. I suggest posting on the Docker thread ( with a link to this thread) and see if another Docker users has seen it.

    https://forums.slimdevices.com/showt...tainer-for-LMS

    Provide details of the OS / Platform on which LMS/Docker is running and details on the squeezelite player OS & platform.
    Hi,

    Thanks - yes, when I read that this was not normal, the first thing I thought of was that it might be a docker issue. However, I've just installed it from the deb on bare metal, and the same thing happens. It happens with Squeezelite running on the same host as LMS, as well as when Squeezelite is run on a MacBook Pro connecting over wifi.

    Is it at all possible that this is happening for everyone with the latest versions of LMS, and nobody notices because they don't use

    Code:
    -d all=debug
    ?

    I'm pretty sure I haven't done anything weird, so unless the networking stack on my server is really messed up, I can't think how my setup would differ from many others.

  5. #5
    Senior Member
    Join Date
    May 2008
    Location
    Canada
    Posts
    6,938
    Quote Originally Posted by hbq269 View Post
    Hi,

    Thanks - yes, when I read that this was not normal, the first thing I thought of was that it might be a docker issue. However, I've just installed it from the deb on bare metal, and the same thing happens. It happens with Squeezelite running on the same host as LMS, as well as when Squeezelite is run on a MacBook Pro connecting over wifi.

    Is it at all possible that this is happening for everyone with the latest versions of LMS, and nobody notices because they don't use

    Code:
    -d all=debug
    ?

    I'm pretty sure I haven't done anything weird, so unless the networking stack on my server is really messed up, I can't think how my setup would differ from many others.
    Maybe b/c slimproto by default runs with loglevel = WARN and this is an INFO level log. On my own squeezelite fork for the bridges I've moved that to WARN but at least in that context, nobody reported that to me so far.
    LMS 8.1.x on Odroid-C4 - SqueezeAMP!, 5xRadio, 5xBoom, 2xDuet, 1xTouch, 1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

  6. #6
    Junior Member
    Join Date
    Dec 2020
    Posts
    6
    Quote Originally Posted by philippe_44 View Post
    It should definitively not happen. There is a problem with your network and connection breaks all the time. SB devices are supposed to keep an open socket with LMS all the time
    I seem to have resolved it. I think the problem might have been that there were multiple squeezelite processes running on the same server. Could that have caused this? The other one seemed to have survived in the background for a long time, and I only discovered it by accident. Once I killed it, things seemed to work a lot better, both in docker and on bare metal. The only thing this doesn't explain is the fact that squeezelite running on my laptop also gave the same errors. Perhaps the server was just generally confused by having two squeezelites on the same host.

  7. #7
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    20,304
    Quote Originally Posted by hbq269 View Post
    Perhaps the server was just generally confused by having two squeezelites on the same host.
    LMS identifies squeezelite players by their MAC address - so to have multiple squeezlite in same on same host they must have different MAC addresses. Users must use the squeezelite command option to fake a MAC address to handle this setup.

    If you have two squeezelite processes with same MAC address - LMS will think it is just one player so probably only one TCP connection at a time and so weird stuff will 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
  •