Piaware version 7.2 is running

FlightAware ADS-B Flight Tracking
1

Hi guys,
Just updated my flightaware on my Raspberry Pi from v7.1 to 7.2

Any idea where I can find some more info about the v7.2?
Are there any official Release Notes?

Cheers,

2

Dump1090-FA Version 7.2 brings minor changes

  • dump1090: Fix Makefile syntax error for Darwin OS build
  • dump1090: set _POSIX_C_SOURCE to fix build failure with uclibc-ng
  • SkyAware: Remove obselete map interface at /dump1090-fa
  • SkyAware: Remove OSM Black & White layer which is no longer in service

Piaware version 7.2 brings no change, just an updated version number:

1 Like
3

Awesome … thanks for that quick answer

1 Like
4

This is not correct. The piaware ver 7.2 incorporates an important change. The ver 7.1 used tcl-tls_1.7.22 from raspbian repository. This had a bug which caused occasional failure of piaware to connect to Flightaware server.

The ver 7.2 uses a rebuild version tcl-tls_1.7.22-2+fa1 from Flightaware repositories. This rebuild version has a workaround for that bug.

3 Likes
5

Thanks @abcd567 , I just followed the statement from Obj that stated that there was no change to the 7.2 version :innocent:

6

I also upgraded to 7.2 on "Raspbian GNU/Linux 10 (buster). I found that the graph1090 app for collectd stopped updating right after the update.

So, there is yet another feature upgrade.

Depending on your configuration, update collectd.conf to the correct URL that points to http://localhost/skyaware/data/stats.json Bear in mind rewrting of the URL in lighttpd.conf (89-skyaware.conf). I recall dump1090-fa changed to skyaware, there too so be forewarned.

from

               <Instance localhost>
                        URL "http://localhost/dump1090-fa"
                </Instance>

to

  <Instance localhost>
                        URL "http://localhost/skyaware/"
                </Instance>

restart collectd.

fixed it for me.

7

Is this also a bug in the 7.2 SD card image? I have this in collectd.conf:

<Instance localhost>
                        URL "file:///usr/share/graphs1090/data-symlink"
                        URL_978 "file:///usr/share/graphs1090/978-symlink"
           </Instance>

I’ve yet to upgrade to 7.2 and curious if 7.2 will break graphs1090 since I’m in the middle of UAT gain tweaks.

8

I didn’t have to change anything after upgrading to 7.2. Graphs1090 seems to work just fine.

10

I’ve always had issues with piaware and graph1090 documentation. I don’t generally accept the upgrades modification my configuration files. This can occasionally cause pain.

So, yes, using file:// URI to read the stats.json file is a great idea.

I did notice after making my change to the URL, things immediately started working again.

I don’t know if they pushed changes to the lighttpd.conf to support the change from dump1090-fa/dump1090 to using skyaware. So depending on how you’ve been upgrading, might explain why some experienced no issues going from 7.1 to 7.2.

I did also notice the recent upgrade to graph1090 moved the location of the rrd files around a bit too. What used to have the RRD files /var/lib/collectd/rrd, now just has localhost.tar.gz. The new location is /run/collectd/localhost/dump1090-localhost. But this migration seemed to cause no issues.

I can’t always check all the content works correctly after an upgrade. Nagios told me the file wasn’t being updated so this popped right out post upgrade.

11

I found the best habit is to wait for that prompt during update, then open another terminal session and make a backup of the file in question, then accept the overwrite with the package maintainer’s version. Lowest pain option with easy reference if something breaks. :grin: (I got the same two prompts you did, made backups before allowing the update to proceed, but nothing broke after the update).

12

Low and behold, this change to the URL appears to have happened with the update to graph1090! Mine now matches yours! As [davidinjp] said, a better process is to compare the diffs of the file vs the upgrade, that would have saved me the grief.

Now I know to also check the rrd directory after upgrading to make sure graph1090 is working!

That will remind me to make sure the correct full path is used for bacula backups too!

13

Hey @abcd567 I see you have debian packages for piaware 7.2. I’m running piaware 6. Can I run the commands to install 7.2 or do I have to remove version 6 first? Thanks!

14

You can do it both ways.

  • While keeping ver 6, run the command to install ver 7.2. It will install ver 7.2 over ver 6
  • Alternatively first remove ver 6 then install ver 7.2

 

2 Likes
15

Thanks! I’ll back up my station and try the overwriting method.

16

@jepolch
I understand you are NOT using Raspberry PI (armhf or arm64/aarch64). You are using Laptop/Desktop with amd64 x86_x64 architecture.

OPTION-1: You can install pre-build packages
For Debian 11 amd64 x86_x64 from here
https://github.com/abcd567a/debian/blob/master/README.md

For Ubuntu 20 amd64 x86_x64 from here
https://github.com/abcd567a/ubuntu/blob/master/README.md

 

OPTION-2: Build packages right on your computer from source-code, and then install these packages (Any architecture of your computer):
https://github.com/abcd567a/piaware-ubuntu20-amd64/blob/master/README.md

2 Likes
17

Tnx @abcd567!

You, @obj & @wiedehopf do especially good work. I “unintentionally” updated from v. 6.2 on my pi B+ and it was seamless. She runs fine and sails true.

Thanks!

vb77

18

… don’t let me forget @foxhunter.

I’ve learned a lot from you all, and I only speak Fortran IV.

1 Like
19

That’s right. Linux Mint 20.1 (Ubuntu) on an Intel i5. I’ll use your packages. Thanks again and have a good night.

20

I do not speak any coding language. All i know is learning by doing :slight_smile:

21

That’s the best way to go!