FlightAware Discussions

Installing PiAware on Ubuntu

Why it is working all of a sudden, i will never seem to know…


hscadmin@FlightAware:~$ sudo piaware-status
dump1090 is running.
faup1090 is not running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is connected to FlightAware.
dump1090 is producing data on port 30005.


next step, a sign that says “DO NOT TOUCH UNDER PENALTY OF SEVERE RIDICULE”

The actual next step is to migrate the box to a better spot for the antenna. Thanks for your help & moral support!
-Ramos

Did you use piaware_builder to build the piaware package? You should use piaware_builder.

i reinstalled using piaware builder. The program seems to be working, and it remains connected to flightaware, but no stats have been uploaded. flightaware recognizes my piaware client, but my stats box are still empty.

-ramos

I see you have a connection, but from the log messages that are being forwarded, faup1090 is not starting up properly. (See /tmp/piaware.out)

What happens if you try to start faup1090 manually?



$ /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout


(It should start writing aircraft summary information to stdout if all is well)

here is some output from /tmp/piaware.out


01/2015 16:29:50 ****************************************************
10/01/2015 16:29:50 piaware version 2.1-3 is running, process ID 1198
10/01/2015 16:29:50 your system info is: Linux FlightAware 3.19.0-30-generic #33~14.04.1-Ubuntu SMP Tue Sep 22 09:27:41 UTC 2015 i686 i686 i686 GNU/Linux
10/01/2015 16:29:50 connecting to FlightAware piaware.flightaware.com/1200
10/01/2015 16:29:50 FlightAware server SSL certificate validated
10/01/2015 16:29:50 encrypted session established with FlightAware
10/01/2015 16:29:50 autoUpdate in adept config is enabled, allowing update
10/01/2015 16:29:50 manualUpdate in adept config is enabled, allowing update
10/01/2015 16:29:50 multilateration support disabled (no fa-mlat-client found)
10/01/2015 16:29:50 ADS-B data program 'dump1090' is listening on port 30005, so far so good
10/01/2015 16:29:50 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
10/01/2015 16:29:50 Started faup1090 (pid 1310) to connect to dump1090
10/01/2015 16:29:50 lost connection to dump1090 via faup1090
10/01/2015 16:29:50 will reconnect to dump1090 in 30 seconds
10/01/2015 16:29:51 logged in to FlightAware as user RamosXN40
10/01/2015 16:30:20 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
10/01/2015 16:30:20 ADS-B data program 'dump1090' is listening on port 30005, so far so good
10/01/2015 16:30:20 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
10/01/2015 16:30:20 Started faup1090 (pid 1702) to connect to dump1090
10/01/2015 16:30:20 lost connection to dump1090 via faup1090
10/01/2015 16:30:20 will reconnect to dump1090 in 30 seconds
10/01/2015 16:30:50 server is sending alive messages; we will expect them
10/01/2015 16:30:50 ADS-B data program 'dump1090' is listening on port 30005, so far so good
10/01/2015 16:30:50 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
10/01/2015 16:30:50 Started faup1090 (pid 1708) to connect to dump1090
10/01/2015 16:30:50 lost connection to dump1090 via faup1090
10/01/2015 16:30:50 will reconnect to dump1090 in 30 seconds
10/01/2015 16:31:20 ADS-B data program 'dump1090' is listening on port 30005, so far so good
10/01/2015 16:31:20 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
10/01/2015 16:31:20 Started faup1090 (pid 1714) to connect to dump1090
10/01/2015 16:31:20 lost connection to dump1090 via faup1090
10/01/2015 16:31:20 will reconnect to dump1090 in 30 seconds

If I just try to start faup1090:


hscadmin@FlightAware:/$ faup1090
faup1090: error opening the listening port 10001 (FlightAware TSV output): Address already in use


If I start faup1090 via the command you provided:


hscadmin@FlightAware:~$ /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
hscadmin@FlightAware:~$ 
hscadmin@FlightAware:/$ sudo piaware-status
dump1090 is running.
faup1090 is not running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is NOT connected to port 30005.
piaware is connected to FlightAware.
dump1090 is producing data on port 30005.
hscadmin@FlightAware:/$ 


I tried something interesting (in my opinion), and it’s working but it’s not…


hscadmin@FlightAware:/$ faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --net-fatsv-port 10002
hscadmin@FlightAware:/$ sudo piaware-status
dump1090 is running.
faup1090 is running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090 is producing data on port 30005.
hscadmin@FlightAware:/$ 


And i forwarded the port, and it checks out., but…


10/01/2015 17:37:49 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
10/01/2015 17:37:49 Started faup1090 (pid 3827) to connect to dump1090
10/01/2015 17:37:49 lost connection to dump1090 via faup1090
10/01/2015 17:37:49 will reconnect to dump1090 in 30 seconds

I had an SD card go bad on my Raspberry Pi running the PiAware 2.1-2 image supplied by FlightAware a couple days ago. While waiting for a new SD card to arrive today and after seeing this post I decided to do a test run using a Hyper-V installation of Ubuntu 15.04. I ended up skipping the well documented and what appears to be working documentation supplied by Rubyducky. The only reason being I like packages over the make/make install method. However I did refer back to his instructions in order to try and get dependencies right which were missing following Obj’s upgrade instructions.

The following are the commands I used to install PiAware and dump1090-mutability on Raspbian Jessie as well as Ubuntu 15.04 Vivid Vervet both of which were tested to make sure both operating systems fed data to FlightAware. The commands are exactly as Obj posted earlier. There were a few missing dependencies of which are needed to install the Piaware package which I added to the sudo apt-get install line…

The following commands were ran on fresh installations of Debian Jessie, Raspbian Jessie, and Ubuntu 15.04.
Only the most recent available updates from the default repositories were applied before running the following commands.


$ sudo apt-get install build-essential debhelper librtlsdr-dev libusb-1.0-0-dev pkg-config tcl8.5-dev autoconf python3-dev python-virtualenv libz-dev git tclx8.4 tcllib tcl-tls itcl3
$ cd ~; git clone https://github.com/mutability/dump1090.git
$ cd ~/dump1090; dpkg-buildpackage -b
$ cd ~; git clone https://github.com/flightaware/piaware_builder.git
$ cd ~/piaware_builder; ./sensible-build.sh
$ cd ~/piaware_builder/package; dpkg-buildpackage -b
$ sudo dpkg -i ~/dump1090-mutability_1.15~dev_*.deb
$ sudo dpkg -i ~/piaware_builder/piaware_2.1-3_*.deb

Thanks to both Rubyducky and Obj for giving me a starting point!

EDIT:
Forgot to add refer to the piaware 2.1-3 release post for MLAT/dump1090 changes. I ended up changing the BEAST_INPUT_PORT to 30104 in the file /etc/default/dump1090-mutability as well as installed lighttpd as documented at github.com/mutability/dump1090.

OTHER EDITS:
Tested on Debian 8.2.0 Jessie as well.
Removed unnecessary packages from the sudo apt-get install line.
Published a more detailed description of the entire process. swiftbyte.com/articles/soft … -or-debian

This is an old faup1090 you still have hanging around somewhere in $PATH from some old install. It’s obsolete and can’t be used with current piaware. Current piaware+faup1090 does not start faup1090 in the background and then connect to port 10001; it starts faup1090 in the foreground and expects it to write to stdout. Port 10001 is no longer used.

If I start faup1090 via the command you provided:

hscadmin@FlightAware:~ /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout hscadmin@FlightAware:~

It just… exited with no error message? That’s very weird; I’ve never seen that type of failure before. The only path I can see that would make that happen is if it managed to establish a connection to port 30005, but got immediately disconnected. Maybe there is a firewall issue? Can you connect to port 30005 with nc and see data? (“nc localhost 30005 | hexdump -C”)

nc localhost 30005 | hexdump -C


00000000  1a 32 00 04 b1 f8 d3 8c  2a 5d a0 6f 7d 2e 01 56  |.2......*].o}..V|
00000010  1a 32 00 04 b1 fa 3a 66  27 5d a0 6f 7d 2e 01 56  |.2....:f'].o}..V|
00000020  1a 32 00 04 b3 39 28 7a  17 00 a1 85 17 32 d8 e0  |.2...9(z.....2..|
00000030  1a 32 00 04 b5 94 28 2c  21 00 81 85 17 77 a4 c9  |.2....(,!....w..|
*et cetera...

I see Hex, I’m willing to assume based on the command that this is a good sign.

a port check from canyouseeme.org

Success: I could see your service on 76.***.***.*** on port 30005.
Your ISP is not blocking port 30005.

jprochazka, your tutorial was a lifesaver. I was about ready to take the ubuntu box out back and… well, take care of business.

I got my piaware working, so thank you for your help, it was bang on. I’m having trouble with the mlat, but that was my fault (I just read the commands without reading the instructions that say “Choose one of the following options”) so I’ll tinker with that later. But I am now submitting data.

Have a good day!
-Ramos

Glad you found it helpful.

If you ran the commands for both MLAT configuration options in order including editing the file /etc/default/dump1090-mutability to listen on port 30104 then running the following command should get MLAT showing.

sudo piaware-config -mlatResultsFormat beast,connect,localhost:30104

1 Like

Actually, I got the mlat working, I just tried and tried again to set the mlat options, and eventually it just started working. However the lighttpd isn’t working. If I could pick your brain again for a second, I had to change the html port from 80 to 8080 (80 is being used for something else), but all I am getting is the default lighttpd page, I can’t seem to get the dump1090 to show. Again, your help is greatly appreciated

-Ramos

What address are you using to access the web interface?

If you changed the port lighttpd uses to 8080 you should be using an address like so:
](http://):8080/dump1090

If that does not work try hitting the .html page directly:
](http://):8080/dump1090/gmap.html

If still no luck let me know where you changed your port to 8080 at and I will take a look on one of my setups.

(dump1090-mutability is configured by default to need /dump1090 at the end of the URL to access the page. If you do not add this to the URL you will get the default lighttpd page.)

akward… I resintalled lighttpd 3 times (scrubbing ubuntu of any mention of lighttpd)… guess 3rd times a charm… Again, thanks for your help.

-Alex

repository ‘https://github.com/flightaware/dump1090_mr.git/’ not found

Err:6 http://ppa.launchpad.net/ojowett/dump1090/ubuntu disco Release
404 Not Found [IP: 91.189.95.83 80]
Reading package lists… Done
E: The repository ‘http://ppa.launchpad.net/ojowett/dump1090/ubuntu disco Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

The “4 years later” should be a hint here.

1 Like

Lol. I had hoped to prod someone into saying that there has been an update.

Looks like I might have to go the Raspberry Pi route after all, but that makes coding & debugging a pain :frowning:

You ignored other more recent threads.
Even opening your own thread and just asking how to do it is preferrable to digging up a 4 year old thread.

It’s far from impossible to compile and install on Ubuntu.
Actually it’s being discussed right now in one of the other recent threads.

If you just want a local map, this will probably work on Ubuntu:
https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb

It’s a fork of dump1090-fa, the script should compile and install it.
If you want to feed, you obviously still need piaware_builder.

So … even gonna link those threads, they are even named appropriately:
How to Install Piaware v 3.7.2 on Ubuntu 18.04 (Bionic) & Ubuntu 19.04 (Disco) amd64 / Intel PC
How to Install Dump1090-fa & Piaware v 3.8.1 on Ubuntu 18.04 (Bionic) & Ubuntu 19.04 (Disco) amd64

1 Like

I guess there was some reason for replying to the old thread - maybe it matched from particular search term.

In any case, thanks a 1,000,000 for your help. Much appreciated.

I guess the dream would be a pre-configured VM or Docker container. I will check out those trehads & see what I can do