Anomaly report for PiAware feeder with a MAC address of b8:27:eb:0b:85:2c:
1.37% of UDP multilateration traffic sent by piaware is not reaching the FlightAware servers. This may indicate a network problem.
Did it really say 1.37% or did you typo that?
Oh, it’s the list numbering, that’s a bit confusing. (Item 1: 37% of UDP …)
It indicates a network problem that is dropping some traffic from your feeder to FlightAware. You can fix it by fixing the network problem, whatever it is.
yes I copy and paste it
Got in the last days similar message but with values between 10 and 21%.
The point is that nobody was at home to use bandwidth, no intruder was recorded in my network, nothing was running (so no win updates to blame).
After a few refresh commands the messages was gone.
Emil
All,
Not sure if this is related, but for the past few weeks I have seen the mlat traffic count fall off the almost zero at 1800 and return to “normal” at 2300. When I look at dump1090, the mlat traffic is not there, then a few hits will show up, then disappear. I have looked at other feeders in the DFW near me, and they seem to have the same issue, so I don’t think the issue is on my end. Bandwidth/server issue between 1800 and 2300?
Just an observation.
Thanks
Same here, on my feeder and pretty much every feeder I’ve looked at. Looks to be more like an issue with some sort of burden on FA MLAT servers at that time.
Mike
Actually, I’ve looked at a lot of feeder statistics lately, and the only feeder I’m seeing this issue one [out of all of the ones I looked at]. At 1800 EST the MLAT drops off.
See: flightaware.com/adsb/stats/user/mtindor
If I look in /var/log/piaware.log at 23:00 (since logs are in GMT), I see no odd behavior on my side. Everything looks good. Is there any chance that the FA server that my RPI3 connects to for MLAT is having issues around that time?
My RPI3 /var/log/piaware.log
Nov 29 22:31:45 piaware piaware[532]: 111559 msgs recv'd from dump1090-fa (886 in last 5m); 111440 msgs sent to FlightAware
Nov 29 22:32:43 piaware piaware[532]: mlat-client(894): Receiver status: connected
Nov 29 22:32:43 piaware piaware[532]: mlat-client(894): Server status: synchronized with 33 nearby receivers
Nov 29 22:32:43 piaware piaware[532]: mlat-client(894): Receiver: 515.1 msg/s received 215.7 msg/s processed (42%)
Nov 29 22:32:43 piaware piaware[532]: mlat-client(894): Server: 1.0 kB/s from server 0.0kB/s TCP to server 2.7kB/s UDP t
o server
Nov 29 22:32:43 piaware piaware[532]: mlat-client(894): Results: 469.6 positions/minute
Nov 29 22:32:43 piaware piaware[532]: mlat-client(894): Aircraft: 40 of 51 Mode S, 9 of 28 ADS-B used
Nov 29 22:36:45 piaware piaware[532]: 112555 msgs recv'd from dump1090-fa (996 in last 5m); 112436 msgs sent to FlightAware
Nov 29 22:41:45 piaware piaware[532]: 113575 msgs recv'd from dump1090-fa (1020 in last 5m); 113456 msgs sent to FlightAware
Nov 29 22:46:45 piaware piaware[532]: 114612 msgs recv'd from dump1090-fa (1037 in last 5m); 114493 msgs sent to FlightAware
Nov 29 22:47:43 piaware piaware[532]: mlat-client(894): Receiver status: connected
Nov 29 22:47:43 piaware piaware[532]: mlat-client(894): Server status: synchronized with 31 nearby receivers
Nov 29 22:47:43 piaware piaware[532]: mlat-client(894): Receiver: 765.7 msg/s received 269.2 msg/s processed (35%)
Nov 29 22:47:43 piaware piaware[532]: mlat-client(894): Server: 1.5 kB/s from server 0.0kB/s TCP to server 3.3kB/s UDP t
o server
Nov 29 22:47:43 piaware piaware[532]: mlat-client(894): Results: 692.7 positions/minute
Nov 29 22:47:43 piaware piaware[532]: mlat-client(894): Aircraft: 36 of 65 Mode S, 12 of 31 ADS-B used
Nov 29 22:51:45 piaware piaware[532]: 115706 msgs recv'd from dump1090-fa (1094 in last 5m); 115587 msgs sent to FlightAware
Nov 29 22:56:45 piaware piaware[532]: 116719 msgs recv'd from dump1090-fa (1013 in last 5m); 116600 msgs sent to FlightAware
Nov 29 23:01:45 piaware piaware[532]: 117660 msgs recv'd from dump1090-fa (941 in last 5m); 117541 msgs sent to FlightAware
Nov 29 23:02:43 piaware piaware[532]: mlat-client(894): Receiver status: connected
Nov 29 23:02:43 piaware piaware[532]: mlat-client(894): Server status: synchronized with 32 nearby receivers
Nov 29 23:02:43 piaware piaware[532]: mlat-client(894): Receiver: 879.7 msg/s received 333.4 msg/s processed (38%)
Nov 29 23:02:43 piaware piaware[532]: mlat-client(894): Server: 1.4 kB/s from server 0.0kB/s TCP to server 4.5kB/s UDP t
o server
Nov 29 23:02:43 piaware piaware[532]: mlat-client(894): Results: 625.2 positions/minute
Nov 29 23:02:43 piaware piaware[532]: mlat-client(894): Aircraft: 47 of 68 Mode S, 8 of 21 ADS-B used
Nov 29 23:06:45 piaware piaware[532]: 118649 msgs recv'd from dump1090-fa (989 in last 5m); 118530 msgs sent to FlightAware
Nov 29 23:11:45 piaware piaware[532]: 119693 msgs recv'd from dump1090-fa (1044 in last 5m); 119574 msgs sent to FlightAware
Nov 29 23:16:45 piaware piaware[532]: 120810 msgs recv'd from dump1090-fa (1117 in last 5m); 120691 msgs sent to FlightAware
Nov 29 23:17:44 piaware piaware[532]: mlat-client(894): Receiver status: connected
Nov 29 23:17:44 piaware piaware[532]: mlat-client(894): Server status: synchronized with 34 nearby receivers
Nov 29 23:17:44 piaware piaware[532]: mlat-client(894): Receiver: 978.0 msg/s received 346.9 msg/s processed (35%)
Nov 29 23:17:44 piaware piaware[532]: mlat-client(894): Server: 0.0 kB/s from server 0.0kB/s TCP to server 4.6kB/s UDP t
o server
Nov 29 23:17:44 piaware piaware[532]: mlat-client(894): Aircraft: 43 of 69 Mode S, 8 of 29 ADS-B used
Nov 29 23:21:45 piaware piaware[532]: 121886 msgs recv'd from dump1090-fa (1076 in last 5m); 121767 msgs sent to FlightAware
Nov 29 23:26:45 piaware piaware[532]: 123008 msgs recv'd from dump1090-fa (1122 in last 5m); 122889 msgs sent to FlightAware
Nov 29 23:31:45 piaware piaware[532]: 124039 msgs recv'd from dump1090-fa (1031 in last 5m); 123920 msgs sent to FlightAware
Mike
Having the exact same issue in the metroplex, as is another user nearby. Very strange.
It is mlat server overload, as mentioned in a previous thread.