FlightAware Discussions

My Flightradar24 feeder keeps stopping

How do I reimage the Pi?

I have been working with my own setup and with FlightRadar24 on this problem. Please read their response to me this morning…

Hello Mark,

Thank you for contacting Flightradar24.com.

Your Support reference is 383795.

Sorry about this confusion. We’are aware of this issue and a new version with a fix has already been released. You don’t need to do anything, it should get installed automatically within the next 24 hours.

Best regards,

Olga

On Tue, 15 Sep at 1:30 PM , Mark Paladino <32verdi32@gmail.com> wrote:

This is why my feeder keeps going offline. The routing to FlightRadar24 is broken and has been for weeks…There are many others having similar difficulty…

Tracing route to 185.218.24.1 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 9 ms 11 ms 9 ms 142.254.215.1
3 101 ms 25 ms 26 ms agg62.ntnwny1702h.northeast.rr.com [24.58.216.213]
4 13 ms 12 ms 11 ms agg37.lncsnycd02r.northeast.rr.com [24.58.38.106]
5 17 ms 13 ms 15 ms be29.rochnyei01r.northeast.rr.com [24.58.32.62]
6 26 ms 28 ms 26 ms bu-ether13.tustca4200w-bcr00.tbone.rr.com [66.109.6.2]
7 30 ms 30 ms 31 ms bu-ether11.chctilwc00w-bcr00.tbone.rr.com [66.109.6.21]
8 27 ms 26 ms 26 ms ae-13.edge2.Chicago10.Level3.net [4.68.37.137]
9 135 ms 136 ms 135 ms ae-2-3204-bar1.Stockholm1.Level3.net [4.69.159.86]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

I believe that I have traced the problem to the following from the system log of my modem / router: “Started Unicast Maintenance Ranging - No Response received - T3 time-out”
That command and activity out of the modem / router (which occurs periodically) causes the Pi to lose internet connectivity to the FR24 part of the software. It doesn’t totally bonk FA from continuing to report aircraft activity however it does affect FA from continuing to report and update PiAware SkyAware. A Google of the Unicast Maintenance Ranging activity indicates
many people experience the same issue. At this point I am not sure what causes the lack of response or what to do about it. I have calls in to Spectrum tech…

The following is from my modem / router. Note the time stamps:

Time Priority Description
Mon Sep 22 12:47:15 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received -
T3 time-out; CM-MAC=b0:c2:87:b4:7a:a6;CMTS-MAC=00:01:5c:8b:c8:5a;
CM-QOS=1.1;CM-VER=3.0;

The following is from the FlightAware log. Note the time when problem arises:

[2020-09-22 12:34 EDT] mlat-client(1080): Results: 18.7 positions/minute
[2020-09-22 12:34 EDT] mlat-client(1080): Receiver status: connected
[2020-09-22 12:34 EDT] mlat-client(1080): Server status: synchronized with 219 nearby receivers
[2020-09-22 12:34 EDT] mlat-client(1080): Receiver: 145.7 msg/s received 74.7 msg/s processed (51%)
[2020-09-22 12:38 EDT] 47040 msgs recv’d from dump1090-fa (614 in last 5m); 46963 msgs sent to FlightAware
[2020-09-22 12:46 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:46 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: connection lost
[2020-09-22 12:46 EDT] faup1090 exited normally
[2020-09-22 12:46 EDT] reconnecting to dump1090-fa
[2020-09-22 12:47 EDT] mlat-client(1080): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2020-09-22 12:47 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:47 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:47 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
[2020-09-22 12:47 EDT] no ADS-B data program seen listening on port 30005 for 61 seconds, next check in 60s
[2020-09-22 12:47 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:48 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:48 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
[2020-09-22 12:48 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:48 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2020-09-22 12:48 EDT] no ADS-B data program seen listening on port 30005 for 121 seconds, next check in 60s
[2020-09-22 12:48 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:48 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
[2020-09-22 12:48 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:48 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:49 EDT] mlat-client(1080): Receiver status: disconnected
[2020-09-22 12:49 EDT] mlat-client(1080): Server status: not synchronized with any nearby receivers
[2020-09-22 12:49 EDT] mlat-client(1080): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.8kB/s UDP to server
[2020-09-22 12:49 EDT] mlat-client(1080): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
[2020-09-22 12:49 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
[2020-09-22 12:49 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:49 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:49 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2020-09-22 12:49 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:49 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:49 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:50 EDT] mlat-client(1080): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2020-09-22 12:50 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:50 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
[2020-09-22 12:50 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:50 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:50 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2020-09-22 12:50 EDT] mlat-client(1080): Reconnecting in 0.5 seconds
[2020-09-22 12:50 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:50 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:50 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:51 EDT] mlat-client(1080): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2020-09-22 12:51 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:51 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:51 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:51 EDT] no ADS-B data program seen listening on port 30005 for 301 seconds, next check in 60s
[2020-09-22 12:51 EDT] mlat-client(1080): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2020-09-22 12:52 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:52 EDT] mlat-client(1080): Reconnecting in 30.0 seconds
[2020-09-22 12:52 EDT] mlat-client(1080): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2020-09-22 12:52 EDT] mlat-client(1080): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2020-09-22 12:52 EDT] mlat-client(1080): Reconnecting in 0.5 seconds

To get things to return to normal I have to reboot Pi.

This implies that dump1090-fa is no longer running. Perhaps you have a problem with the receiver dongle.