Could you try once more with
when the problem is occurring?
What I am looking for is the other end of the single active connection, which is not included in the listing with all the CLOSE_WAIT connections that you sent:
My guess is that lsof is not listing all network connections without sudo.
What I am looking for is something like this:
You can see kplex server listening for new connections and then one established connection from application nc.
As far as I understand this kplex is not handling connections that are closed by a client properly but keeps the file descriptor open with the connection in CLOSE_WAIT state - when there is no data being processed. From what you are saying it closes the connections properly if there is data flowing.
What i don't understand is that in your listings signalk-server does not have any open connections: it is only listening for new http connections on port 3000.
Ooops, I meant
https://sailoog.gitbooks.io/openplotter-..._work.html
and the picture in
http://forum.openmarine.net/showthread.p...41#pid6541
Code:
sudo lsof -i | grep 30330
when the problem is occurring?
What I am looking for is the other end of the single active connection, which is not included in the listing with all the CLOSE_WAIT connections that you sent:
Code:
kplex 3363 pi 11u IPv4 434938 0t0 TCP 10.10.10.1:30330->10.10.10.1:55516 (ESTABLISHED)
My guess is that lsof is not listing all network connections without sudo.
What I am looking for is something like this:
Code:
lsof -i | grep 30330
kplex 8862 tjk 6u IPv6 0x1b4146e9b77ce467 0t0 TCP *:30330 (LISTEN)
kplex 8862 tjk 7u IPv6 0x1b4146e9af129447 0t0 TCP localhost:30330->localhost:56510 (ESTABLISHED)
nc 8863 tjk 5u IPv6 0x1b4146e9b69ff987 0t0 TCP localhost:56510->localhost:30330 (ESTABLISHED)
You can see kplex server listening for new connections and then one established connection from application nc.
As far as I understand this kplex is not handling connections that are closed by a client properly but keeps the file descriptor open with the connection in CLOSE_WAIT state - when there is no data being processed. From what you are saying it closes the connections properly if there is data flowing.
What i don't understand is that in your listings signalk-server does not have any open connections: it is only listening for new http connections on port 3000.
(2018-08-05, 08:16 PM)tkurki Wrote: I am confused - in http://forum.openmarine.net/showthread.p...41#pid6541 data routing is different from the pic in http://forum.openmarine.net/showthread.p...41#pid6541, which claims to be from the documentation??
Ooops, I meant
https://sailoog.gitbooks.io/openplotter-..._work.html
and the picture in
http://forum.openmarine.net/showthread.p...41#pid6541