search

wellenvogel / avnav

using the raspberry pi as a nav computer
MIT License
87 stars 27 forks source link

Ocharts disappear after a while #386

Open Fietsenwiel opened 1 day ago

Fietsenwiel commented 1 day ago

My O-charts disappear after a while. I don't know after how long but that could be after one or two hours.

After restarting AvNav the O-charts are back, again for some time.

I made pictures of the situation and I enclose the logfile. This is on a Raspberry pi 4b.

avnav-20241116.log No ocharts1 No ocharts2 No ocharts3 No ocharts4 No ocharts5

Fietsenwiel commented 17 hours ago

Here the issue with O-charts disapearing.

You say: "The broken pipes are pointing to a networking issue (the browser was running into a timeout and closing the connection)."

I have three wifi connections:

No ocharts6

Wlan0 connects to an accespoint of the harbor Wlan1 is an accespoint to acces the raspberry directly when sailing. tun0 is a vpn tunnel over wlan0 to acces the raspberry pi from home and to get info about humidity, temp, alarms etc.

I know that o-charts don't work over the vpn. I have the problem over Wlan0 and Wlan1.

All three connections works without problems (for as I know).

This configuration always worked witout problems, also o-charts did not disapear. But I don't know what has been changed why this problem occures

Can you explain how network issues make o-charts diaspear but everything else keeps working? This might help solving this.

Fietsenwiel commented 15 hours ago

I have no idea where to look. Just looking around: But I see is the /var/log/syslog "TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters." Is this a problem?

free-x commented 14 hours ago

very interesting What is output of

ss -nta | grep 8080
Fietsenwiel commented 12 hours ago

ss -nta | grep 8080

LISTEN 0 5 0.0.0.0:8080 0.0.0.0:* ESTAB 0 0 192.168.0.198:8080 192.168.0.85:63677 ESTAB 0 0 192.168.0.198:8080 192.168.0.85:63683 ESTAB 0 0 192.168.0.198:8080 192.168.0.21:54418 ESTAB 0 0 192.168.0.198:8080 192.168.0.21:51687 ESTAB 0 0 192.168.0.198:8080 192.168.0.85:63692 ESTAB 0 0 192.168.0.198:8080 192.168.0.85:63458

But I think I have found the cause of the network problems. The ss -nta | grep 8080 output is after "solving" the problem. Deactivation the VHFInfo Signalk plugin solved the problem. The VHFinfo plugin helps finding the right VHF channel at the right places.

Somehow the plugin does something wrong when there is no GPS signal, its keeps complaining about it and it looks like it leads to signalk timeouts. A lot of them:

info is missing (navigation.position) Nov 17 00:02:41 Relexed signalk-server[28812]: 2024-11-16T23:02:41.364Z vhfinfo searchPolygon is null Nov 17 00:02:46 Relexed signalk-server[28812]: 2024-11-16T23:02:46.365Z vhfinfo createSearchPolygon: coordinates info is missing (navigation.position) Nov 17 00:02:46 Relexed signalk-server[28812]: 2024-11-16T23:02:46.366Z vhfinfo searchPolygon is null Nov 17 00:02:51 Relexed signalk-server[28812]: 2024-11-16T23:02:51.366Z vhfinfo createSearchPolygon: coordinates info is missing (navigation.position)

But I still don't understand the relation between o-charts and network issues.