Next time the LMS goes into denial, I can just try to play it. Do I simply need the Podcasts plug-in?
Ok, cancel that. I can just add it as a favourite.
Ok, cancel that. I can just add it as a favourite.
-
Last edited by mvordeme; 2020-12-01, 17:11.piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140 -
Tidal got stuck again, today, and I tried a few more things.
- On the Receiver, the MPEG-4 podcast did not play, either. It showed the same behaviour as tracks from Tidal, i.e. re-buffering and now and then playing a few seconds.
- On squeezelite, Tidal tracks would still play, but they had some trouble taking off. The clock would start counting, but no music would play. After a few seconds, the music would follow, get stuck again, and start over. After one or two attempts and the occasional stuttering, the entire track less the first few seconds would play without any problem. It was the same for all tracks I tried.
- On squeezelite, the MPEG-4 podcast played without any problems whatsoever.
- Today, the piCorePlayer web interface was not working properly, either. The CPU temperature display for example would run into a "connection reset" error more often than not.
I just restarted the LMS (took a few retries to load the LMS page), and the pCP web interface is back. Memory consumption of the LMS was at more than 210 MB and is back to 103 MB, now. Tidal tracks are playing properly again on the Receiver and on squeezelite.piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
The same thing again today. The moment Tidal gets stuck, the pCP web interface does not load properly any more. And I noticed another thing: I configured the Transporter to power down the audio section when off. It was sitting there, clicking about once per minute. It seems that the entire server is out of connections. As soon as the LMS is restarted, everything is fine again.piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
I re-wired mains and network to the pi and, while I was at it, updated the LMS to Logitech Media Server Version: 8.0.1 - 1607087403 @ Fri Dec 4 14:26:56 CET 2020. It is still showing the same behaviour. I noticed one more thing. A few tracks before Tidal streaming breaks and the pCP interface goes down, the last seconds of tracks are sometimes skipped. The Controller is still counting down the remaining time when the next track suddenly starts playing. Somebody else has already noticed this here:As soon as the LMS is restarted, this goes away, too.piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
Might have to make a post with Tidal in the subject.piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please donate if you like the piCorePlayerComment
-
Resource Leak (Connections) in Tidal Plug-In?
Can this discussion be moved?piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
Connection Leak in Tidal Plug-In
Alright, I decided to change my mindset and try to get to the bottom of this myself. This looks very much like a connection leak.
LMS running for half a day:
LMS restarted:Code:tc@piCoreServer:~$ netstat -tnp netstat: can't scan /proc - are you root? Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 192.168.178.101:46618 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:48000 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50096 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46648 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:3483 192.168.178.201:21904 ESTABLISHED - tcp 0 0 192.168.178.101:46482 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50140 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46520 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46498 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46514 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50166 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:47276 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:47980 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50050 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50032 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50128 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:47282 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46546 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50116 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50084 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46540 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:3483 192.168.178.207:60786 ESTABLISHED - tcp 0 0 192.168.178.101:50160 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:3483 192.168.178.206:43723 ESTABLISHED - tcp 0 1852 192.168.178.101:22 192.168.178.104:50976 ESTABLISHED - tcp 0 0 192.168.178.101:50146 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:45818 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46560 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:47946 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:9000 192.168.178.205:40454 ESTABLISHED - tcp 0 0 192.168.178.101:3483 192.168.178.202:23251 ESTABLISHED - tcp 0 0 192.168.178.101:47962 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:9000 192.168.178.207:34338 ESTABLISHED - tcp 0 0 192.168.178.101:46642 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:47986 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:3483 192.168.178.205:56035 ESTABLISHED - tcp 0 0 192.168.178.101:47954 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50152 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46554 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46466 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:45830 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50188 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46436 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50176 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:9000 192.168.178.203:46808 ESTABLISHED - tcp 0 0 192.168.178.101:46610 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:48006 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46490 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:50182 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46582 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:47970 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46472 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:46574 151.101.114.142:443 CLOSE_WAIT - tcp 0 0 192.168.178.101:3483 192.168.178.204:38350 ESTABLISHED - tcp 0 0 192.168.178.101:46508 151.101.114.142:443 CLOSE_WAIT - netstat: /proc/net/tcp6: No such file or directory
Devices in the 192.168.178.20# address range are players, 192.168.178.104 is my Windows PC. And yes, I need to sudo it, next time. Is there anything else I can do to find out more?Code:tc@piCoreServer:~$ netstat -tnp netstat: can't scan /proc - are you root? Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 192.168.178.101:3483 192.168.178.207:53404 ESTABLISHED - tcp 0 0 192.168.178.101:9000 192.168.178.207:37218 ESTABLISHED - tcp 0 0 192.168.178.101:3483 192.168.178.204:38352 ESTABLISHED - tcp 0 300 192.168.178.101:22 192.168.178.104:50976 ESTABLISHED - tcp 0 0 192.168.178.101:9000 192.168.178.205:37825 ESTABLISHED - tcp 0 0 192.168.178.101:9000 192.168.178.203:46014 ESTABLISHED - tcp 0 0 192.168.178.101:3483 192.168.178.202:23262 ESTABLISHED - tcp 0 0 192.168.178.101:3483 192.168.178.206:43725 ESTABLISHED - tcp 0 0 192.168.178.101:3483 192.168.178.201:21920 ESTABLISHED - tcp 0 0 192.168.178.101:3483 192.168.178.205:52397 ESTABLISHED - netstat: /proc/net/tcp6: No such file or directory
piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
TIDAL Plug-In: One Stuck Connection per Played Track
Playing the third track after restart:
Code:tc@piCoreServer:~$ sudo netstat -tnp Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 192.168.178.101:3483 192.168.178.207:53404 ESTABLISHED 25504/perl tcp 0 0 192.168.178.101:9000 192.168.178.207:37218 ESTABLISHED 25504/perl tcp 0 0 192.168.178.101:3483 192.168.178.204:38352 ESTABLISHED 25504/perl tcp 0 49533 192.168.178.101:9000 192.168.178.201:21923 ESTABLISHED 25504/perl tcp 0 216 192.168.178.101:22 192.168.178.104:50976 ESTABLISHED 25008/sshd: tc [pri tcp 0 0 192.168.178.101:9000 192.168.178.205:37825 ESTABLISHED 25504/perl tcp 0 0 192.168.178.101:9000 192.168.178.203:46014 ESTABLISHED 25504/perl tcp 0 0 192.168.178.101:50844 151.101.114.142:443 CLOSE_WAIT 25504/perl tcp 0 0 192.168.178.101:3483 192.168.178.202:23262 ESTABLISHED 25504/perl tcp 0 0 192.168.178.101:3483 192.168.178.206:43725 ESTABLISHED 25504/perl tcp 3339072 0 192.168.178.101:50868 151.101.114.142:443 ESTABLISHED 25504/perl tcp 0 0 192.168.178.101:9000 192.168.178.203:46836 ESTABLISHED 25504/perl tcp 0 0 192.168.178.101:3483 192.168.178.201:21920 ESTABLISHED 25504/perl tcp 0 0 192.168.178.101:50850 151.101.114.142:443 CLOSE_WAIT 25504/perl tcp 0 0 192.168.178.101:3483 192.168.178.205:52397 ESTABLISHED 25504/perl netstat: /proc/net/tcp6: No such file or directory
piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
After ssh'ing into Touch, you could check on the interface statistics with ifconfig or /proc/net/netstat to see if there are more network errors/resets/retransmissions happening than expected or coinciding with the problem
edit:
Sorry mixed up with another problem and thought you were using touch.
On PCP you may be able to use netstat -ts
Look for rapid changes rather than absolute numbers.Last edited by bpa; 2020-12-09, 22:30.Comment
-
unfortunately, not:Code:tc@piCoreServer:~$ netstat -ts netstat: invalid option -- 's' BusyBox v1.30.1 (2019-06-20 23:16:54 EDT) multi-call binary. Usage: netstat [-ral] [-tuwx] [-enWp] Display networking information -r Routing table -a All sockets -l Listening sockets Else: connected sockets -t TCP sockets -u UDP sockets -w Raw sockets -x Unix sockets Else: all socket types -e Other/more information -n Don't resolve names -W Wide display -p Show PID/program name for socketspiCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
si
Code:TcpExt: SyncookiesSent SyncookiesRecv SyncookiesFailed EmbryonicRsts PruneCalled RcvPruned OfoPruned OutOfWindowIcmps LockDroppedIcmps ArpFilter TW TWRecycled TWKilled PAWSActive PAWSEstab DelayedACKs DelayedACKLocked DelayedACKLost ListenOverflows ListenDrops TCPHPHits TCPPureAcks TCPHPAcks TCPRenoRecovery TCPSackRecovery TCPSACKReneging TCPSACKReorder TCPRenoReorder TCPTSReorder TCPFullUndo TCPPartialUndo TCPDSACKUndo TCPLossUndo TCPLostRetransmit TCPRenoFailures TCPSackFailures TCPLossFailures TCPFastRetrans TCPSlowStartRetrans TCPTimeouts TCPLossProbes TCPLossProbeRecovery TCPRenoRecoveryFail TCPSackRecoveryFail TCPRcvCollapsed TCPDSACKOldSent TCPDSACKOfoSent TCPDSACKRecv TCPDSACKOfoRecv TCPAbortOnData TCPAbortOnClose TCPAbortOnMemory TCPAbortOnTimeout TCPAbortOnLinger TCPAbortFailed TCPMemoryPressures TCPMemoryPressuresChrono TCPSACKDiscard TCPDSACKIgnoredOld TCPDSACKIgnoredNoUndo TCPSpuriousRTOs TCPMD5NotFound TCPMD5Unexpected TCPMD5Failure TCPSackShifted TCPSackMerged TCPSackShiftFallback TCPBacklogDrop PFMemallocDrop TCPMinTTLDrop TCPDeferAcceptDrop IPReversePathFilter TCPTimeWaitOverflow TCPReqQFullDoCookies TCPReqQFullDrop TCPRetransFail TCPRcvCoalesce TCPOFOQueue TCPOFODrop TCPOFOMerge TCPChallengeACK TCPSYNChallenge TCPFastOpenActive TCPFastOpenActiveFail TCPFastOpenPassive TCPFastOpenPassiveFail TCPFastOpenListenOverflow TCPFastOpenCookieReqd TCPFastOpenBlackhole TCPSpuriousRtxHostQueues BusyPollRxPackets TCPAutoCorking TCPFromZeroWindowAdv TCPToZeroWindowAdv TCPWantZeroWindowAdv TCPSynRetrans TCPOrigDataSent TCPHystartTrainDetect TCPHystartTrainCwnd TCPHystartDelayDetect TCPHystartDelayCwnd TCPACKSkippedSynRecv TCPACKSkippedPAWS TCPACKSkippedSeq TCPACKSkippedFinWait2 TCPACKSkippedTimeWait TCPACKSkippedChallenge TCPWinProbe TCPKeepAlive TCPMTUPFail TCPMTUPSuccess TCPDelivered TCPDeliveredCE TCPAckCompressed TCPZeroWindowDrop TCPRcvQDrop TCPWqueueTooBig TcpExt: 0 0 8 533 128223 0 3861 9 1 0 31276 0 0 0 7 31349 19 13275 0 63 1277102 5558222 839400 774 462 0 514 82 5 504 5 541 1514 6551 253 12 116 1822 452 12960 12122 255 8 33 6 6294 6 8826 280 130 2625 24 271 0 0 2 106627300 0 16 3465 327 0 0 0 382 883 2180 0 0 0 0 0 0 0 0 0 2182968 89243 86229 6 0 0 0 0 0 0 0 0 0 55 0 7218 9819 9819 31432 4398 8637741 61 1026 26 1049 0 3 665 0 0 0 11 9 0 0 8670882 0 25224 0 39009 0 IpExt: InNoRoutes InTruncatedPkts InMcastPkts OutMcastPkts InBcastPkts OutBcastPkts InOctets OutOctets InMcastOctets OutMcastOctets InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts InECT0Pkts InCEPkts ReasmOverlaps IpExt: 0 1 2485 0 308827 8776 3788602774 10699008456 89540 0 26727858 669756 0 10080983 0 0 0 0
piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
Comment
-
Code:tc@piCoreServer:~$ cat /proc/net/netstat | cut -d' ' -f 1,35,41 TcpExt: TCPLostRetransmit TCPTimeouts TcpExt: 6863 13430 IpExt: IpExt:
piCorePlayer 8.2.0 | Logitech Media Server 8.5.1 | Tidal | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140Comment
-
OK. Normally TCP connections are reliable but when a connection has to aborted it usually means an odd network issue or perhaps one end of the connection has power off, broken,crashed.
To see if there is some odd network activity at the same time as the playback issues, you could have a shell script to output TCP Abort counters and see if they jump. If they don't then you can probably rules out network issues.
The meaning of these counters areCode:> head -n2 /proc/net/netstat | cut -d' ' -f 52,53,55 TCPAbortOnData TCPAbortOnClose TCPAbortOnTimeout 11381 5797 1379
TCPAbortOnData : connections reset due to unexpected data
TCPAbortOnClose : connections reset due to early user close
TCPAbortOnTimeout : connections aborted due to timeoutLast edited by bpa; 2020-12-10, 22:08.Comment
Comment