Intermittent reductions in reported positions

Hi

I am getting intermittent reductions in reported positions that other receivers in the area are not seeing. I have a 2.1a power supply delivered through a rechargeable power pack that is constantly being recharged from the mains. I had experienced problems with an RPI power pack, which resulted in the dongle not starting during RPI boot up. I have had no such problems with the power pack.

I have an orange Flight Aware dongle. I have been monitoring my broadband bandwidth every 15 minutes and it was stable around the time of each reduction in the number of reported positions. An image showing these reductions is shown below:

http://www.schweboo.com/beyond/wp-content/uploads/2017/02/piaware.jpg

The charts also show that this issue has occured several times this week, mostly at different times of the day.

Where should I look next to try to resolve this problem?

Kind regards

Chris

Check /var/log/piaware.log at around the time of the problem, perhaps the connection to FA dropped for some reason.

Do you see a reduction in the traffic you see on the local webmap as well?

Below is an extract from the log at the time of one of the reductions in reported positions. Not quite sure what this is telling me:

Feb 2 16:47:32 raspberrypi piaware[557]: mlat-client(12860): Server status: synchronized with 150 nearby receivers
Feb 2 16:47:32 raspberrypi piaware[557]: mlat-client(12860): Receiver: 1021.8 msg/s received 233.8 msg/s processed (23%)
Feb 2 16:47:32 raspberrypi piaware[557]: mlat-client(12860): Server: 0.5 kB/s from server 0.0kB/s TCP to server 3.0kB/s UDP to server
Feb 2 16:47:32 raspberrypi piaware[557]: mlat-client(12860): Results: 222.3 positions/minute
Feb 2 16:47:32 raspberrypi piaware[557]: mlat-client(12860): Aircraft: 35 of 45 Mode S, 50 of 72 ADS-B used
Feb 2 16:50:09 raspberrypi piaware[557]: data isn’t making it to FlightAware, reconnecting…
Feb 2 16:50:09 raspberrypi piaware[557]: multilateration data no longer required, disabling mlat client
Feb 2 16:50:10 raspberrypi piaware[557]: fa-mlat-client exited normally
Feb 2 16:50:10 raspberrypi piaware[557]: reconnecting in 59 seconds…
Feb 2 16:50:10 raspberrypi piaware[557]: mlat-client(12860): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
Feb 2 16:50:10 raspberrypi piaware[557]: mlat-client(12860): Exiting on connection loss
Feb 2 16:51:09 raspberrypi piaware[557]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 2 16:51:09 raspberrypi piaware[557]: Connection with adept server at piaware.flightaware.com/1200 established
Feb 2 16:51:39 raspberrypi piaware[557]: 5284321 msgs recv’d from dump1090-fa (2449 in last 5m); 4978521 msgs sent to FlightAware
Feb 2 16:51:39 raspberrypi piaware[557]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Feb 2 16:51:39 raspberrypi piaware[557]: reconnecting in 51 seconds…
Feb 2 16:52:30 raspberrypi piaware[557]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 2 16:52:30 raspberrypi piaware[557]: Connection with adept server at piaware.flightaware.com/1200 established
Feb 2 16:53:00 raspberrypi piaware[557]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Feb 2 16:53:00 raspberrypi piaware[557]: reconnecting in 61 seconds…
Feb 2 16:54:01 raspberrypi piaware[557]: Connecting to FlightAware adept server at 70.42.6.197/1200
Feb 2 16:54:01 raspberrypi piaware[557]: Connection with adept server at 70.42.6.197/1200 established
Feb 2 16:54:31 raspberrypi piaware[557]: Connection attempt with adept server at 70.42.6.197/1200 timed out
Feb 2 16:54:31 raspberrypi piaware[557]: reconnecting in 57 seconds…
Feb 2 16:55:28 raspberrypi piaware[557]: Connecting to FlightAware adept server at 70.42.6.198/1200
Feb 2 16:55:28 raspberrypi piaware[557]: Connection with adept server at 70.42.6.198/1200 established
Feb 2 16:55:58 raspberrypi piaware[557]: Connection attempt with adept server at 70.42.6.198/1200 timed out
Feb 2 16:55:58 raspberrypi piaware[557]: reconnecting in 52 seconds…
Feb 2 16:56:39 raspberrypi piaware[557]: 5286715 msgs recv’d from dump1090-fa (2394 in last 5m); 4978521 msgs sent to FlightAware
Feb 2 16:56:50 raspberrypi piaware[557]: Connecting to FlightAware adept server at 70.42.6.191/1200
Feb 2 16:56:50 raspberrypi piaware[557]: Connection with adept server at 70.42.6.191/1200 established
Feb 2 16:57:20 raspberrypi piaware[557]: Connection attempt with adept server at 70.42.6.191/1200 timed out
Feb 2 16:57:20 raspberrypi piaware[557]: reconnecting in 63 seconds…
Feb 2 16:58:23 raspberrypi piaware[557]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 2 16:58:23 raspberrypi piaware[557]: Connection with adept server at piaware.flightaware.com/1200 established
Feb 2 16:58:53 raspberrypi piaware[557]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Feb 2 16:58:53 raspberrypi piaware[557]: reconnecting in 69 seconds…
Feb 2 17:00:02 raspberrypi piaware[557]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 2 17:00:02 raspberrypi piaware[557]: Connection with adept server at piaware.flightaware.com/1200 established
Feb 2 17:00:32 raspberrypi piaware[557]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Feb 2 17:00:32 raspberrypi piaware[557]: reconnecting in 61 seconds…
Feb 2 17:01:33 raspberrypi piaware[557]: Connecting to FlightAware adept server at 70.42.6.197/1200
Feb 2 17:01:33 raspberrypi piaware[557]: Connection with adept server at 70.42.6.197/1200 established
Feb 2 17:01:39 raspberrypi piaware[557]: 5289083 msgs recv’d from dump1090-fa (2368 in last 5m); 4978521 msgs sent to FlightAware
Feb 2 17:02:03 raspberrypi piaware[557]: Connection attempt with adept server at 70.42.6.197/1200 timed out
Feb 2 17:02:03 raspberrypi piaware[557]: reconnecting in 55 seconds…
Feb 2 17:02:58 raspberrypi piaware[557]: Connecting to FlightAware adept server at 70.42.6.198/1200
Feb 2 17:02:58 raspberrypi piaware[557]: Connection with adept server at 70.42.6.198/1200 established
Feb 2 17:03:28 raspberrypi piaware[557]: Connection attempt with adept server at 70.42.6.198/1200 timed out
Feb 2 17:03:28 raspberrypi piaware[557]: reconnecting in 63 seconds…
Feb 2 17:04:31 raspberrypi piaware[557]: Connecting to FlightAware adept server at 70.42.6.191/1200
Feb 2 17:04:31 raspberrypi piaware[557]: Connection with adept server at 70.42.6.191/1200 established
Feb 2 17:05:01 raspberrypi piaware[557]: Connection attempt with adept server at 70.42.6.191/1200 timed out
Feb 2 17:05:01 raspberrypi piaware[557]: reconnecting in 54 seconds…
Feb 2 17:05:55 raspberrypi piaware[557]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 2 17:05:55 raspberrypi piaware[557]: Connection with adept server at piaware.flightaware.com/1200 established
Feb 2 17:06:25 raspberrypi piaware[557]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
Feb 2 17:06:25 raspberrypi piaware[557]: reconnecting in 56 seconds…


…all the same until 17:23:55


Feb 2 17:23:55 raspberrypi piaware[557]: reconnecting in 63 seconds…
Feb 2 17:24:58 raspberrypi piaware[557]: Connecting to FlightAware adept server at 70.42.6.198/1200
Feb 2 17:24:58 raspberrypi piaware[557]: Connection with adept server at 70.42.6.198/1200 established
Feb 2 17:24:59 raspberrypi piaware[557]: TLS handshake with adept server at 70.42.6.198/1200 completed
Feb 2 17:24:59 raspberrypi piaware[557]: FlightAware server certificate validated
Feb 2 17:24:59 raspberrypi piaware[557]: encrypted session established with FlightAware
Feb 2 17:25:00 raspberrypi piaware[557]: logged in to FlightAware as user schweboo
Feb 2 17:25:00 raspberrypi piaware[557]: my feeder ID is f6deda26-76ff-427a-a423-11209e9ac056
Feb 2 17:25:00 raspberrypi piaware[557]: site statistics URL: flightaware.com/adsb/stats/user … tats-15272
Feb 2 17:25:01 raspberrypi piaware[557]: multilateration data requested
Feb 2 17:25:01 raspberrypi piaware[557]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.198:9818:167011$
Feb 2 17:25:01 raspberrypi piaware[557]: mlat-client(18423): fa-mlat-client 0.2.8 starting up
Feb 2 17:25:01 raspberrypi piaware[557]: mlat-client(18423): Using UDP transport to 70.42.6.198 port 9818
Feb 2 17:25:01 raspberrypi piaware[557]: mlat-client(18423): Listening for Beast-format results connection on port 30105
Feb 2 17:25:01 raspberrypi piaware[557]: mlat-client(18423): Listening for Extended Basestation-format results connection on port 30106
Feb 2 17:25:01 raspberrypi piaware[557]: mlat-client(18423): Input connected to localhost:30005
Feb 2 17:25:01 raspberrypi piaware[557]: mlat-client(18423): Input format changed to BEAST, 12MHz clock
Feb 2 17:25:02 raspberrypi piaware[557]: mlat-client(18423): Beast-format results connection with ::1:30104: connection established
Feb 2 17:26:39 raspberrypi piaware[557]: 5300988 msgs recv’d from dump1090-fa (2323 in last 5m); 4979337 msgs sent to FlightAware
Feb 2 17:31:39 raspberrypi piaware[557]: 5303383 msgs recv’d from dump1090-fa (2395 in last 5m); 4981732 msgs sent to FlightAware
Feb 2 17:36:39 raspberrypi piaware[557]: 5305705 msgs recv’d from dump1090-fa (2322 in last 5m); 4984054 msgs sent to FlightAware
Feb 2 17:40:02 raspberrypi piaware[557]: mlat-client(18423): Receiver status: connected
Feb 2 17:40:02 raspberrypi piaware[557]: mlat-client(18423): Server status: synchronized with 147 nearby receivers
Feb 2 17:40:02 raspberrypi piaware[557]: mlat-client(18423): Receiver: 906.8 msg/s received 221.4 msg/s processed (24%)
Feb 2 17:40:02 raspberrypi piaware[557]: mlat-client(18423): Server: 0.5 kB/s from server 0.0kB/s TCP to server 2.9kB/s UDP to server
Feb 2 17:40:02 raspberrypi piaware[557]: mlat-client(18423): Results: 217.8 positions/minute
Feb 2 17:40:02 raspberrypi piaware[557]: mlat-client(18423): Aircraft: 36 of 50 Mode S, 40 of 66 ADS-B used
Feb 2 17:41:39 raspberrypi piaware[557]: 5308030 msgs recv’d from dump1090-fa (2325 in last 5m); 4986379 msgs sent to FlightAware
Feb 2 17:46:39 raspberrypi piaware[557]: 5310617 msgs recv’d from dump1090-fa (2587 in last 5m); 4988966 msgs sent to FlightAware
Feb 2 17:51:39 raspberrypi piaware[557]: 5313349 msgs recv’d from dump1090-fa (2732 in last 5m); 4991698 msgs sent to FlightAware
Feb 2 17:55:02 raspberrypi piaware[557]: mlat-client(18423): Receiver status: connected

It’s saying there are network problems somewhere between you and the FlightAware servers; there is enough network there to establish the connection, but not for any data to flow (not even the TLS handshake)

I have BT broadband c. 60 mbit (down) and (11mbit) broadband (up). I checked it over the period concerned and it seemed to be fine. Does that point the finger at something outside of my control?

What else can I do?

See if it happens again in the same way. There was a hardware failure on the FA side at around the time of the logs that you quoted; you should have switched over to one of the other servers that was still reachable, but maybe it took a while.

Happened again today. Once around 1300 and once around 1600 (London time).

If it looks the same in piaware.log at those times, then it wasn’t the FA-side thing. I’d guess a problem between the Pi and your router if it only affects that one Pi.

DOS attack on the router?

Or just a terrible router, I am also on BT broadband here and the router is pretty flakey.

VODOS (Vendor Originated Denial Of Service) ?