2018-08-06, 07:02 AM
I'd like to understand this problem better.
You wrote "SignalK waits ca 30 seconds for information from kplex and then thinks the connection is down and doesn't close it. It just opens a new connection. ". I am not aware of any such logic in SK server. https://github.com/sailoog/openplotter/b...tings.json only has udp connections that have no connection - where is the connection between kplex and sk configured? tcp or udp? Which one is the server and which one the client? The diagrams I found we confusing, see my other post.
Can you run
that should list all kplex open network connections.
If would be great if people could create issues at https://github.com/SignalK/signalk-server-node/issues if they encounter problems with SK server. So many forums, can't read them all...
You wrote "SignalK waits ca 30 seconds for information from kplex and then thinks the connection is down and doesn't close it. It just opens a new connection. ". I am not aware of any such logic in SK server. https://github.com/sailoog/openplotter/b...tings.json only has udp connections that have no connection - where is the connection between kplex and sk configured? tcp or udp? Which one is the server and which one the client? The diagrams I found we confusing, see my other post.
Can you run
Code:
sudo lsof -iP | grep <kplexpid>that should list all kplex open network connections.
If would be great if people could create issues at https://github.com/SignalK/signalk-server-node/issues if they encounter problems with SK server. So many forums, can't read them all...