FlightAware Discussions

Upgrade to 6.1 broke PiAware

Was running PiAware 5 and did upgrade to 6.1. If I connect to my LAN address, it looks normal and says running 6.1 but it’s not talking to Flight Aware. The last few log entries are shown below:

kernel 4.4.50+ (kernel.img) and initramfs initrd.img-4.4.50+
[2021-09-12 20:54 CDT] run-apt-get(15122): rpi-bootconfig: updating /boot/config.txt
[2021-09-12 20:54 CDT] attempting to restart piaware using ‘systemctl --no-block try-restart piaware.service < /dev/null’…
[2021-09-12 20:54 CDT] multilateration data no longer required, disabling mlat client
[2021-09-12 20:54 CDT] piaware (process 12550) is shutting down because it received a shutdown signal (SIGTERM) from the system…

I’ve powered down the PiAware but didn’t help.

Any suggestions would be greatly appreciated.

Thanks,
Joe

I’m a newbie but with that kernel 4.4.50+ it looks like you were on Jessie and PiAware 6 is based on Buster, two Debian versions above yours. You may need to reimage your SD card with the latest PiAware image.

1 Like

What Operating system are you running? Seem to be outdated at all
If it’s the Piaware Image from FA, reimage it.
In case you’re using the package version, your OS requires an upgrade

Piaware sdcard image or something else? Can you reach the local status page or skyaware?

Well, I reimaged the SD, and it’s behaving as before. The 6.1 image works as it shows 6.1 and planes on the local SkyAware page but it’s still not being seen by Flight Aware. I changed the config file to show my feeder ID. It’s been a LONG time since I built and configured the Pi, and lots of brain cells have died since then!

Nothing in the log.

Thanks for your help, but still need more!

Joe

Did you set in the SD card config file ?
Configure an Existing Station

(a) - Find existing station’s feeder-id (Unique Identifier)
Log-in to your Flightaware account, go to “My ADSB” / stats page
flightaware.com/adsb/stats/user/ ,
and look for 32-digit Unique Identifier: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

(b) - SSH and configure station id:

sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 
sudo systemctl restart piaware

Turns out that the IP addresses for Flight Aware that PiAware sends data to changed when going from 5.0 to 6.1. I’m behind a very strict firewall that monitors outgoing traffic as well as incoming. It didn’t like the new IP’s. Changed the rule and all is well again. I didn’t know the exact range but set it to allow anything going to 206.253.x.x based on what the firewall was blocking. Does anyone have a list of IP’s that Flight Aware uses? I would like to restrict outgoing to only those IP’s.

Thanks for everyone’s help.

Joe

1 Like

Yeah, that’s a new(-ish) IP block we’ve moving to, it’s a /21.

You can use the Firehose list of IP ranges if you want an exhaustive list: Firehose (Live Flight Data API) Documentation - FlightAware