Hi, I have just got a new Pi3 and having set it up with the piaware image I had no problems sending data.
However the Pi crashed earlier and on running dmesg -T I get the following at the end of the output:
TCP: request_sock_TCP: Possible SYN flooding on port 30106. Sending cookies. Check SNMP counters.
Could this be what caused the crash and if so what is the resolution please.
I have very little experience with the Pi, so answers for dummies would be greatly appreciated 
Thanks
Dave
30106 is the mlat result port. Youâll get the kernel complaining about that if you have something e.g. VRS that is aggressively trying to reconnect (probably the port is not open because mlat is not enabled)
Itâs unrelated to the Pi crashing. You probably have bad power.
I am using an official Raspberry adaptor with an output of 2.5A
Nothing is plugged into the Pi except for a powered hub.
The output from the piaware.log at the time it went down is:
Oct 1 06:55:30 raspberrypi piaware[586]: mlat-client(5112): Results: 564.0 positions/minute
Oct 1 06:55:30 raspberrypi piaware[586]: mlat-client(5112): Aircraft: 27 of 59 Mode S, 31 of 76 ADS-B used
Oct 1 06:57:00 raspberrypi piaware[586]: 696355 msgs recvâd from dump1090-fa (2197 in last 5m); 694456 msgs sent to FlightAware
Oct 1 07:02:00 raspberrypi piaware[586]: 698263 msgs recvâd from dump1090-fa (1908 in last 5m); 696364 msgs sent to FlightAware
Oct 1 07:06:02 raspberrypi piaware[586]: data isnât making it to FlightAware, reconnectingâŚ
Oct 1 07:06:02 raspberrypi piaware[586]: multilateration data no longer required, disabling mlat client
Oct 1 07:06:03 raspberrypi piaware[586]: fa-mlat-client exited normally
Oct 1 07:06:03 raspberrypi piaware[586]: reconnecting in 66 secondsâŚ
Oct 1 07:06:03 raspberrypi piaware[586]: mlat-client(5112): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for inpu$
Oct 1 07:06:03 raspberrypi piaware[586]: mlat-client(5112): Exiting on connection loss
Oct 1 07:07:00 raspberrypi piaware[586]: 699871 msgs recvâd from dump1090-fa (1608 in last 5m); 697661 msgs sent to FlightAware
Oct 1 07:07:09 raspberrypi piaware[586]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Oct 1 07:07:29 raspberrypi piaware[586]: Connection to adept server at piaware.flightaware.com/1200 failed: couldnât open socket: Name or service not known
Oct 1 07:07:29 raspberrypi piaware[586]: reconnecting in 53 secondsâŚ
Oct 1 07:08:22 raspberrypi piaware[586]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Oct 1 07:08:42 raspberrypi piaware[586]: Connection to adept server at piaware.flightaware.com/1200 failed: couldnât open socket: Name or service not known
Oct 1 07:08:42 raspberrypi piaware[586]: reconnecting in 58 secondsâŚ
Oct 1 07:09:40 raspberrypi piaware[586]: Connecting to FlightAware adept server at 70.42.6.197/1200
Oct 1 07:09:43 raspberrypi piaware[586]: Connection to adept server at 70.42.6.197/1200 failed: host is unreachable
Oct 1 07:09:43 raspberrypi piaware[586]: reconnecting in 55 secondsâŚ
Oct 1 07:10:38 raspberrypi piaware[586]: Connecting to FlightAware adept server at 70.42.6.198/1200
Oct 1 07:10:41 raspberrypi piaware[586]: Connection to adept server at 70.42.6.198/1200 failed: host is unreachable
Oct 1 07:10:41 raspberrypi piaware[586]: reconnecting in 69 secondsâŚ
Ok, so when you said âcrashedâ you actually meant âlost network connectivityâ?
The logs quoted above say that the Piâs network connection is hosed.
Sorry, let me try an clarify it a little 
I noticed that I was no longer receiving data back from Flightaware.
When I tried to SSH into the Pi using Putty I couldnât get a connection so couldnât do anything other than unplug it and start it again
Regards
Dave
Assuming that the problem started at around 07:06 UTC, then yes itâs a network problem.
There may be some hints in /var/log/syslog at around the same time (perhaps the ethernet link went down, or DHCP needed to renew but failed, or something like that)
Loads of stuff in there around that time, but Iâm afraid it means nothing to me
Oct 1 06:52:01 raspberrypi rsyslogd0: action âaction 18â resumed (module âbuiltin:ompipeâ) [try rsyslog.com/e/0 ]
Oct 1 06:52:01 raspberrypi rsyslogd-2359: action âaction 18â resumed (module âbuiltin:ompipeâ) [try rsyslog.com/e/2359 ]
Oct 1 06:52:01 raspberrypi CRON[10051]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly ))
Oct 1 07:04:57 raspberrypi kernel: [150502.688242] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
Oct 1 07:05:56 raspberrypi kernel: [150562.113104] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:05:56 raspberrypi kernel: [150562.113126] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:06:56 raspberrypi kernel: [150622.113551] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:06:56 raspberrypi kernel: [150622.113572] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:07:56 raspberrypi kernel: [150682.114046] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:07:56 raspberrypi kernel: [150682.114067] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:08:56 raspberrypi kernel: [150742.124615] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:08:56 raspberrypi kernel: [150742.124636] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:09:56 raspberrypi kernel: [150802.125028] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:09:56 raspberrypi kernel: [150802.125051] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:10:56 raspberrypi kernel: [150862.125492] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:10:56 raspberrypi kernel: [150862.125514] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:11:56 raspberrypi kernel: [150922.125921] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:11:56 raspberrypi kernel: [150922.125943] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:12:56 raspberrypi kernel: [150982.126419] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:12:56 raspberrypi kernel: [150982.126441] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:13:56 raspberrypi kernel: [151042.126890] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:13:56 raspberrypi kernel: [151042.126918] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:14:56 raspberrypi kernel: [151102.127359] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:14:56 raspberrypi kernel: [151102.127380] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:15:56 raspberrypi kernel: [151162.127813] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:15:56 raspberrypi kernel: [151162.127837] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:16:56 raspberrypi kernel: [151222.138263] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:16:56 raspberrypi kernel: [151222.138285] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Oct 1 07:17:01 raspberrypi CRON[10074]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 1 07:17:56 raspberrypi kernel: [151282.138711] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 06:52:01 raspberrypi rsyslogd0: action âaction 18â resumed (module âbuiltin:ompipeâ) [try rsyslog.com/e/0 ]
Oct 1 06:52:01 raspberrypi rsyslogd-2359: action âaction 18â resumed (module âbuiltin:ompipeâ) [try rsyslog.com/e/2359 ]
Oct 1 06:52:01 raspberrypi CRON[10051]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly ))
Oct 1 07:04:57 raspberrypi kernel: [150502.688242] brcmfmac: brcmf_sdio_hostmail: Unknown mailbox data content: 0x40012
Oct 1 07:05:56 raspberrypi kernel: [150562.113104] brcmfmac: brcmf_do_escan: error (-52)
Oct 1 07:05:56 raspberrypi kernel: [150562.113126] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
and goes on with similar until I reboot the Pi
Youâre using the Pi 3âs wifi?
Yes
Looks like a Pi 3 wifi bug; not much we can do about that⌠github.com/raspberrypi/linux/issues/1342
Thanks very much for your help, I donât really have to use wifi, so I think that I will switch it off and use an ethernet connection instead
Regards
Dave
In using the wifi, did you set yours up manually or using the piaware-config?
I set mine up manually, and it works like a champ! If you need help setting yours up like mine, pm me, and send you the steps I used.
This sounds like the problem I am having, though I use Ethernet connection instead of WIFI. The Pi3 will run about 2-3 days before crashing, with no Ethernet link light. Power cycling is the only option. Have not yet looked at messages prior to failure, will do so when I get home to reboot it. I have a scheduled reboot every morning at 3am but that doesnât happen when it fails.
My other unit running PiAware on a Pi2 has been running for over a month without problems.
Ron
Replaced PiAware 2.1.5 with 3.1.0 and it now has been running 3 days with no problems.
Ron