mvordeme wrote:
> 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:
> >
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
--------------------
> >
>
>
This is probably not a helpful or relevant observation, but I shall make
it anyway. I don't use Tidal, so I can't vouch for or validate the OP's
experience.
The netstat listing is very reminiscent of the pattern that I used to
see when LMS would first start up and then 'freeze' for a few minutes.
In that case the 'CLOSE_WAIT's would all relate to the various players
that attempted to connect to LMS, gave up after a timeout, and tried
again. But, for reasons I have never determined, LMS would remain
stubbornly stuck. After a few minutes LMS would become responsive again,
all the 'CLOSE_WAIT's would disappear, and life would continue as
normal.
Is there something similar going on here ? Is LMS simply hanging about
waiting for something to happen on a connection to a remote server, and
not noticing that the remote server has hung up ?
I notice that these are https connections. Is it too fanciful to think
that a 'Reliable plugin for resilient HTTP connections' might help ?
https://forums.slimdevices.com/showthread.php?112931-ANNOUNCE-Reliable-plugin-for-resilient-HTTP-connections&p=988552&viewfull=1#post988552
------------------------------------------------------------------------
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=113321
_______________________________________________
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
