What steps will reproduce the problem?
1. Start LMS and log into mysqueezebox,com.
2. Start squeezelite
3. Connect squeezelite to external library 79.125.18.91
4. Turn off squeezelite
5. Turn off LMS server
6. Start squeezelite with option "-s 79.125.18.91"
7. Log into mysb.com and check that squeezelite is connected to mysb.com
8. Leave squeezelite running connected to mysb.com for several days
9. Log back into mysb.com and squeezelite is no longer listed as connected
What is the expected output? What do you see instead?
Squeezelite connects to MySB.com and works with streaming services like
Wimp(Tidal) without LMS running locally on the network.
After a couple of days I can not connect to squeezelite using Squeezebox
controller.
In mysqueezebox.com: Squeezebox controller, Radio and Touch is still listed as
connected.
Squeezelite is listed as disconnected.
What version of the product are you using? On what operating system?
Squeezelite-1.8-ubuntu-lts-x86_64
On Linux - Openelec 5.0.8
Please provide any additional information below.
From log
/storage/.kodi/userdata/squeezelite/squeezelite -d all=debug -f
/storage/.kodi/userdata/squeezelite/debug.log -s 79.125.18.91 -o
iec958:CARD=NVidia,DEV=0
...
[22:09:05.387662] slimproto:848 connecting to 79.125.18.91:3483
[22:09:05.445213] slimproto:881 connected
..
[22:09:05.581704] process:494 setd
[22:09:05.581789] process:494 setd
[22:09:05.581818] process:494 strm
[22:09:05.581833] process_strm:256 strm command t
[22:09:05.581850] sendSTAT:171 STAT: STMt
[22:09:05.590922] process:494 aude
[22:09:05.590988] process_aude:395 enable spdif: 0 dac: 0
[22:09:05.591047] process:494 audg
[22:09:05.591074] process_audg:413 audg gainL: 65536 gainR: 65536 adjust: 0
[22:09:05.591094] set_volume:246 setting internal gain left: 65536 right: 65536
[22:09:05.601244] output_thread:744 disabling output
[22:09:07.341495] process:494 audg
[22:09:07.341569] process_audg:413 audg gainL: 65536 gainR: 65536 adjust: 0
[22:09:07.341592] set_volume:246 setting internal gain left: 65536 right: 65536
[22:09:31.065811] process:494 strm
[22:09:31.065893] process_strm:256 strm command t
[22:09:31.065913] sendSTAT:171 STAT: STMt
[22:10:00.272019] process:494 strm
...
[01:13:48.083354] process_strm:256 strm command t
[01:13:48.083403] sendSTAT:171 STAT: STMt
[01:14:17.087505] process:494 strm
[01:14:17.087589] process_strm:256 strm command t
[01:14:17.087615] sendSTAT:171 STAT: STMt
[01:14:53.128189] slimproto_run:573 No messages from server - connection dead
[01:14:58.233644] slimproto:868 unable to connect to server 0
[01:15:08.237283] slimproto:868 unable to connect to server 0
[01:15:18.242753] slimproto:868 unable to connect to server 0
.........
[01:34:59.829261] slimproto:868 unable to connect to server 0
[01:35:09.834733] slimproto:868 unable to connect to server 0
[01:35:19.837432] slimproto:868 unable to connect to server 0
[01:35:24.895071] slimproto:881 connected
..........
[04:09:55.073653] process:494 strm
[04:09:55.073709] process_strm:256 strm command t
[04:09:55.073723] sendSTAT:171 STAT: STMt
[04:10:24.066538] process:494 strm
[04:10:24.066618] process_strm:256 strm command t
[04:10:24.066643] sendSTAT:171 STAT: STMt
[04:10:50.045525] process:494 serv
[04:10:50.045609] process_serv:454 switch server
[04:10:50.145860] slimproto:856 switching server to 0.0.0.1:3483
[04:10:50.145958] slimproto:868 unable to connect to server 0
[04:10:55.146214] slimproto:868 unable to connect to server 0
[04:11:00.146524] slimproto:868 unable to connect to server 0
......
[08:30:21.077691] slimproto:868 unable to connect to server 0
[08:30:26.078010] slimproto:868 unable to connect to server 0
[08:30:31.078327] slimproto:868 unable to connect to server 0
Original issue reported on code.google.com by nas4fr...@gmail.com on 1 Jun 2015 at 9:39
Original issue reported on code.google.com by
nas4fr...@gmail.comon 1 Jun 2015 at 9:39