All Green but no connectivity

FlightAware ADS-B Flight Tracking
1

Hey all, still a lot of a newbie, my site shows “all green” on the status page to include Pi-Aware Running, Connected to Flight Aware, MLAT Synchronized but I received a notice that my Pi-Aware has stopped checking in with flightaware. When I go to Skyaware, no aircraft show up. This is the second time this has happened, the first time I had to re-load an SD card, it looks like it was corrupted, the second time I simply unplugged the Pi for about an hour, plugged it back in and eventually it connected. Any ideas about why this is happening? Posting my log below for assistance, thanks in advance!

5m); 399448 msgs sent to FlightAware
[2024-04-08 07:18 CDT] mlat-client(751): Reconnecting in 0.5 seconds
[2024-04-08 07:18 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:18 CDT] mlat-client(751): Reconnecting in 30.0 seconds
[2024-04-08 07:18 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:18 CDT] mlat-client(751): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2024-04-08 07:19 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:19 CDT] mlat-client(751): Reconnecting in 0.5 seconds
[2024-04-08 07:19 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:19 CDT] mlat-client(751): Reconnecting in 30.0 seconds
[2024-04-08 07:19 CDT] no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
[2024-04-08 07:19 CDT] mlat-client(751): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2024-04-08 07:19 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:19 CDT] mlat-client(751): Reconnecting in 0.5 seconds
[2024-04-08 07:19 CDT] mlat-client(751): Reconnecting in 30.0 seconds
[2024-04-08 07:19 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:19 CDT] mlat-client(751): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2024-04-08 07:20 CDT] mlat-client(751): Reconnecting in 0.5 seconds
[2024-04-08 07:20 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:20 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:20 CDT] mlat-client(751): Reconnecting in 30.0 seconds
[2024-04-08 07:20 CDT] attempting to start dump1090…
[2024-04-08 07:20 CDT] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2024-04-08 07:20 CDT] no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it…
[2024-04-08 07:20 CDT] dump1090 start appears to have been successful
[2024-04-08 07:20 CDT] mlat-client(751): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2024-04-08 07:20 CDT] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2024-04-08 07:20 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:20 CDT] mlat-client(751): Reconnecting in 0.5 seconds
[2024-04-08 07:20 CDT] mlat-client(751): Reconnecting in 30.0 seconds
[2024-04-08 07:20 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:20 CDT] mlat-client(751): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2024-04-08 07:21 CDT] mlat-client(751): Reconnecting in 0.5 seconds
[2024-04-08 07:21 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:21 CDT] mlat-client(751): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
[2024-04-08 07:21 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:21 CDT] mlat-client(751): Reconnecting in 30.0 seconds
[2024-04-08 07:21 CDT] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2024-04-08 07:21 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused
[2024-04-08 07:21 CDT] mlat-client(751): Reconnecting in 0.5 seconds
[2024-04-08 07:21 CDT] mlat-client(751): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
[2024-04-08 07:21 CDT] mlat-client(751): Reconnecting in 30.0 seconds
[2024-04-08 07:21 CDT] mlat-client(751): Connection to localhost:30005 lost: [Errno 111] Connection refused

2

Whole lot of Mlat-client error posting there. Have you clicked on the site configuration gear symbol to look at the latitude and longitude details? That has to be very precise to function properly. You might just try disabling MLAT on that same site configuration page to see if the system functions without the MLAT distraction while you are verifying your location parameters.

1 Like
3

reboot your system :wink:

sudo reboot

After the reboot is finished the system will be able to log in again.
At the moment the FA server is refusing the connection from your system.

1 Like
4

Thanks guys, I will double check my MLAT configuration. I see the server rejection and will reboot but am curious as to why this develops over time, is it possibly something I have configured incorrectly?

5

Is your network connection stable?

6

Would need the logs for dump1090-fa

sudo journalctl --no-pager dump1090-fa
1 Like
7

Will dump that log when I’m home from work (too clueless to do it remotely!). The network is via Ethernet and is stable.

8

You could restart the device remotely from your Flightaware stats page if you have it configured accordingly

image