PiAware is NOT connected to FlightAware1

FlightAware ADS-B Flight Tracking
1

Hi All
Suddenly piaware is not connected, it says on main page. Ihave not done anything last year, and have not configure anything new.

logs is as>

pi@piaware:~ $ sudo service piaware status
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2024-06-24 23:00:37 UTC; 13h ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 398 (piaware)
CGroup: /system.slice/piaware.service
├─398 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/statu
└─616 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --std

Jun 25 12:09:52 piaware piaware[398]: reconnecting in 6 seconds…
Jun 25 12:09:58 piaware piaware[398]: Connecting to FlightAware adept server at 70.42.6.198/1200
Jun 25 12:10:13 piaware piaware[398]: Connection attempt with adept server at 70.42.6.198/1200 timed o
Jun 25 12:10:13 piaware piaware[398]: reconnecting in 4 seconds…
Jun 25 12:10:17 piaware piaware[398]: Connecting to FlightAware adept server at 70.42.6.224/1200
Jun 25 12:10:32 piaware piaware[398]: Connection attempt with adept server at 70.42.6.224/1200 timed o
Jun 25 12:10:32 piaware piaware[398]: reconnecting in 5 seconds…
Jun 25 12:10:37 piaware piaware[398]: Connecting to FlightAware adept server at 70.42.6.156/1200
Jun 25 12:10:52 piaware piaware[398]: Connection attempt with adept server at 70.42.6.156/1200 timed o
Jun 25 12:10:52 piaware piaware[398]: reconnecting in 58 seconds…
lines 1-19/19 (END)…skipping…
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2024-06-24 23:00:37 UTC; 13h ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 398 (piaware)
CGroup: /system.slice/piaware.service
├─398 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
└─616 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 34.704

Jun 25 12:09:52 piaware piaware[398]: reconnecting in 6 seconds…
Jun 25 12:09:58 piaware piaware[398]: Connecting to FlightAware adept server at 70.42.6.198/1200
Jun 25 12:10:13 piaware piaware[398]: Connection attempt with adept server at 70.42.6.198/1200 timed out
Jun 25 12:10:13 piaware piaware[398]: reconnecting in 4 seconds…
Jun 25 12:10:17 piaware piaware[398]: Connecting to FlightAware adept server at 70.42.6.224/1200
Jun 25 12:10:32 piaware piaware[398]: Connection attempt with adept server at 70.42.6.224/1200 timed out
Jun 25 12:10:32 piaware piaware[398]: reconnecting in 5 seconds…
Jun 25 12:10:37 piaware piaware[398]: Connecting to FlightAware adept server at 70.42.6.156/1200
Jun 25 12:10:52 piaware piaware[398]: Connection attempt with adept server at 70.42.6.156/1200 timed out
Jun 25 12:10:52 piaware piaware[398]: reconnecting in 58 seconds…
~

2

You have an old piaware version (those fallback IPs are no longer in use), and broken DNS.

Update piaware and/or fix DNS.

1 Like
3

My DNS is just fine. No problem at all. Update piaware, I will take that under consideration. Or just change to some else.Why not reroute your dns to something that works? Or at least send message that your server is FOBAR?

4

(those fallback IPs are no longer in use)
what is your current IP nowadays, then?

5

piaware will attempt to connect to piaware.flightaware.com, which has up-to-date addresses, before falling back to the fallback IPs. If it’s failing to connect to piaware.flightaware.com, please provide logs showing that connection attempt. (The usual reason is that the Pi is having some sort of DNS problem)

Here are the default fallbacks in the current piaware version: piaware/package/fa_piaware_config.tcl at 18aaf464b49887de6afafc10cac672a74a3ac1f1 · flightaware/piaware · GitHub

6

Hi again
If those IP is not in use anymore, how come the system started to work again after ca 2 days?

7

 

Because someone has said “Wingardium Leviosa” :wink: :slightly_smiling_face:

 

 

3 Likes
8

@obj said that it will first attempt to connect to piaware.flightaware.com. If that connection fails it will use hard coded IP addresses as a fallback. The failed connection will most likely due to a failed DNS lookup on the client end. This could be caused by improper DNS config, but could be due to a server being down, a denial of service attack on the DNS host, a temporary blacklist against your ISP, or many other things.

He said that the fallback IP addresses on your older version are no longer in use. That seems to suggest that your original connection problem was that a failed DNS query caused your system to try to use the hard-coded ‘backup’ IP addresses (which don’t work anymore).

If your system is working now, my guess is that whatever was causing the DNS failure has resolved itself, so your system has stopped trying to use the fallback IP addresses and is successfully resolving the piaware.flightaware.com domain.

For your future reference, @obj is one of the authors of the software that you are using. If he tells you directly how something works, it’s a pretty good bet that that’s how it works.

2 Likes
9

In this case, in order to prevent such problem from reccuring, it will be wise to re-image microSD card with latest version of piaware image, which obviously will have latest & valid fallback IP address.