Upgraded Debian FlightAware feeder to V 3 and now no MLAT

FlightAware ADS-B Flight Tracking
1

Hi,

I’d really appreciate some advice to get my MLAT back again.

I have been running a Debian based flight aware feeder built on a linux netbook for a couple of months. It has worked faultlessly until now.

This morning I used the scripts from here adsbreceiver.net/2016/05/12 … -released/ to upgrade my Dump1090-muta to the latest version by Joe and I supplied all of the required selections.

The install.sh script seemed to go well. The dump1090-mutab maps work and I am feeding data to piaware.

BUT…

The MLAT feature now doesn’t work.

These are the logs I have been able to get:

sudo piaware-status

returns the following output:

dump1090 is not running
faup1090 is not running
piaware is not running
dump1090-mutabi is listening for connections on port30005
faup1090 is connected to port 30005
piaware is connected to FlightAware

That looks OK to me (but I’m no expert.

When I look at the logs in the Flightaware ADSB stats page, I get the following log messages

Flightaware log extract on mlat:

mlat-client(16555): Input connected to localhost:30005
[2016-09-19 10:37 BST] mlat-client(16555): Input format changed to BEAST, 12MHz clock
[2016-09-19 10:37 BST] got EOF from multilateration client
[2016-09-19 10:37 BST] fa-mlat-client exited with SIG SIGSEGV
[2016-09-19 10:37 BST] ADS-B data program ‘dump1090-muta’ is listening on port 30005, so far so good
[2016-09-19 10:37 BST] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 55.000 --lon -1.600
[2016-09-19 10:37 BST] Started faup1090 (pid 16561) to connect to dump1090-muta
[2016-09-19 10:37 BST] 133 msgs recv’d from dump1090-muta; 133 msgs sent to FlightAware
[2016-09-19 10:38 BST] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:5461:2075706914

The log goes on to show new attempts to get MLAT going, but they fail it seems because of the EOF from the multilateration client.

This is my adsb flightaware stats page in case expert eyes can spot the problem:

flightaware.com/adsb/stats/user … tats-27881

Many thanks for looking.

Tony

2

A more full log extract from my Flightaware adsb stats page.

Up to about 1024BST is the old system. Then the reboot and after no mlat.

Hope this helps.

[2016-09-19 10:19 BST] 297259 msgs recv’d from dump1090-muta (1289 in last 5m); 296207 msgs sent to FlightAware
[2016-09-19 10:24 BST] mlat(15063): Receiver status: connected
[2016-09-19 10:24 BST] mlat(15063): Server status: synchronized with 47 nearby receivers
[2016-09-19 10:24 BST] mlat(15063): Receiver: 832.3 msg/s received 15.5kB/s from receiver
[2016-09-19 10:24 BST] mlat(15063): Server: 0.6 kB/s from server 0.0kB/s TCP to server 2.9kB/s UDP to server
[2016-09-19 10:24 BST] mlat(15063): Results: 269.8 positions/minute
[2016-09-19 10:24 BST] mlat(15063): Aircraft: 23 of 31 Mode S, 13 of 57 ADS-B used
[2016-09-19 10:24 BST] mlat(15063): Beast-format results connection with localhost:30104: connection lost
[2016-09-19 10:24 BST] mlat(15063): Lost connection to localhost:30005
[2016-09-19 10:24 BST] mlat(15063): Reconnecting in 30.0 seconds
[2016-09-19 10:24 BST] lost connection to dump1090-muta via faup1090
[2016-09-19 10:24 BST] reconnecting to dump1090-muta
[2016-09-19 10:24 BST] no ADS-B data program seen listening on port 30005 for 0 seconds, next check in 60s
[2016-09-19 10:24 BST] 298452 msgs recv’d from dump1090-muta (1193 in last 5m); 297400 msgs sent to FlightAware
[2016-09-19 10:24 BST] mlat(15063): Beast-format results connection with localhost:30104: connection established
[2016-09-19 10:24 BST] mlat(15063): Input connected to localhost:30005
[2016-09-19 10:25 BST] ADS-B data program ‘dump1090-muta’ is listening on port 30005, so far so good
[2016-09-19 10:25 BST] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 55.000 --lon -1.600
[2016-09-19 10:25 BST] Started faup1090 (pid 12283) to connect to dump1090-muta
[2016-09-19 10:29 BST] 299439 msgs recv’d from dump1090-muta (987 in last 5m); 298387 msgs sent to FlightAware
[2016-09-19 10:29 BST] mlat(15063): Beast-format results connection with localhost:30104: connection lost
[2016-09-19 10:29 BST] mlat(15063): Lost connection to localhost:30005
[2016-09-19 10:29 BST] mlat(15063): Reconnecting in 30.0 seconds
[2016-09-19 10:29 BST] lost connection to dump1090-muta via faup1090
[2016-09-19 10:29 BST] reconnecting to dump1090-muta
[2016-09-19 10:29 BST] no ADS-B data program seen listening on port 30005 for 0 seconds, next check in 60s
[2016-09-19 10:29 BST] mlat(15063): Beast-format results connection with localhost:30104: connection established
[2016-09-19 10:29 BST] mlat(15063): Input connected to localhost:30005
[2016-09-19 10:30 BST] ADS-B data program ‘dump1090-muta’ is listening on port 30005, so far so good
[2016-09-19 10:30 BST] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 55.000 --lon -1.600
[2016-09-19 10:30 BST] Started faup1090 (pid 13031) to connect to dump1090-muta
[2016-09-19 10:34 BST] 300436 msgs recv’d from dump1090-muta (997 in last 5m); 299384 msgs sent to FlightAware
[2016-09-19 10:36 BST] piaware (process 518) is shutting down because it received a shutdown signal (SIGTERM) from the system…
[2016-09-19 10:36 BST] multilateration data no longer required, disabling mlat client
[2016-09-19 10:36 BST] piaware (process 518) is exiting…
[2016-09-19 10:36 BST] ====== successful login from piaware 3.0.1 from 82.35.238.165 ======
[2016-09-19 10:36 BST] ADS-B data program ‘dump1090-muta’ is listening on port 30005, so far so good
[2016-09-19 10:36 BST] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
[2016-09-19 10:36 BST] Started faup1090 (pid 16538) to connect to dump1090-muta
[2016-09-19 10:36 BST] Receiver location changed, restarting dump1090
[2016-09-19 10:36 BST] attempting to restart dump1090…
[2016-09-19 10:36 BST] can’t restart dump1090, no services that look like dump1090 found
[2016-09-19 10:36 BST] Receiver location changed, restarting faup1090
[2016-09-19 10:36 BST] faup1090 exited with SIG SIGHUP
[2016-09-19 10:36 BST] will reconnect to dump1090-muta in 5 seconds
[2016-09-19 10:36 BST] multilateration data requested
[2016-09-19 10:36 BST] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:5461:2075706914
[2016-09-19 10:37 BST] mlat-client(16555): fa-mlat-client 0.2.5~dev starting up
[2016-09-19 10:37 BST] mlat-client(16555): Using UDP transport to 70.42.6.224 port 5461
[2016-09-19 10:37 BST] mlat-client(16555): Listening for Extended Basestation-format results connection on port 30106
[2016-09-19 10:37 BST] mlat-client(16555): Input connected to localhost:30005
[2016-09-19 10:37 BST] mlat-client(16555): Input format changed to BEAST, 12MHz clock
[2016-09-19 10:37 BST] got EOF from multilateration client
[2016-09-19 10:37 BST] fa-mlat-client exited with SIG SIGSEGV
[2016-09-19 10:37 BST] ADS-B data program ‘dump1090-muta’ is listening on port 30005, so far so good
[2016-09-19 10:37 BST] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 55.000 --lon -1.600
[2016-09-19 10:37 BST] Started faup1090 (pid 16561) to connect to dump1090-muta
[2016-09-19 10:37 BST] 133 msgs recv’d from dump1090-muta; 133 msgs sent to FlightAware
[2016-09-19 10:38 BST] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:5461:2075706914
[2016-09-19 10:38 BST] mlat-client(16775): fa-mlat-client 0.2.5~dev starting up
[2016-09-19 10:38 BST] mlat-client(16775): Using UDP transport to 70.42.6.224 port 5461
[2016-09-19 10:38 BST] mlat-client(16775): Listening for Extended Basestation-format results connection on port 30106
[2016-09-19 10:38 BST] mlat-client(16775): Input connected to localhost:30005
[2016-09-19 10:38 BST] mlat-client(16775): Input format changed to BEAST, 12MHz clock
[2016-09-19 10:38 BST] got EOF from multilateration client
[2016-09-19 10:38 BST] fa-mlat-client exited with SIG SIGSEGV
[2016-09-19 10:38 BST] lost connection to dump1090-muta via faup1090
[2016-09-19 10:38 BST] faup1090 exited normally
[2016-09-19 10:38 BST] reconnecting to dump1090-muta
[2016-09-19 10:38 BST] no ADS-B data program seen listening on port 30005 for 1 seconds, next check in 60s
[2016-09-19 10:39 BST] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:5461:2075706914
[2016-09-19 10:39 BST] mlat-client(17127): fa-mlat-client 0.2.5~dev starting up
[2016-09-19 10:39 BST] mlat-client(17127): Using UDP transport to 70.42.6.224 port 5461
[2016-09-19 10:39 BST] mlat-client(17127): Listening for Extended Basestation-format results connection on port 30106
[2016-09-19 10:39 BST] mlat-client(17127): Input connected to localhost:30005
[2016-09-19 10:39 BST] mlat-client(17127): Input format changed to BEAST, 12MHz clock
[2016-09-19 10:39 BST] got EOF from multilateration client
[2016-09-19 10:39 BST] fa-mlat-client exited with SIG SIGSEGV
[2016-09-19 10:39 BST] ADS-B data program ‘dump1090-muta’ is listening on port 30005, so far so good
[2016-09-19 10:39 BST] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 55.000 --lon -1.600
[2016-09-19 10:39 BST] Started faup1090 (pid 17171) to connect to dump1090-muta
[2016-09-19 10:40 BST] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:5461:2075706914
[2016-09-19 10:40 BST] mlat-client(17217): fa-mlat-client 0.2.5~dev starting up
[2016-09-19 10:40 BST] mlat-client(17217): Using UDP transport to 70.42.6.224 port 5461
[2016-09-19 10:40 BST] mlat-client(17217): Listening for Extended Basestation-format results connection on port 30106
[2016-09-19 10:40 BST] mlat-client(17217): Input connected to localhost:30005
[2016-09-19 10:40 BST] mlat-client(17217): Input format changed to BEAST, 12MHz clock
[2016-09-19 10:40 BST] got EOF from multilateration client
[2016-09-19 10:40 BST] fa-mlat-client exited with SIG SIGSEGV
[2016-09-19 10:41 BST] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:5461:2075706914
[2016-09-19 10:41 BST] mlat-client(17267): fa-mlat-client 0.2.5~dev starting up
[2016-09-19 10:41 BST] mlat-client(17267): Using UDP transport to 70.42.6.224 port 5461
[2016-09-19 10:41 BST] mlat-client(17267): Listening for Extended Basestation-format results connection on port 30106
[2016-09-19 10:41 BST] mlat-client(17267): Input

3

Your piaware & mlat-client are old; you are probably hitting the bug fixed by this commit: github.com/mutability/mlat-clie … 08b83146c0
Update to latest master (piaware 3.0.5 / mlat-client 0.2.6) and try again.

4

This is how you can do the upgrade

cd
git clone github.com/flightaware/piaware_builder.git
cd piaware_builder/
./sensible-build.sh jessie
cd package-jessie
dpkg-buildpackage -b
sudo dpkg -i …/piaware_3.0.5_armhf.deb
sudo piaware-config -restart

This will work on an RPI or ARM device.
Not sure how different an x86 device would be.

look at the end of the build to see the filename

    chmod 644 debian/piaware/DEBIAN/md5sums
    chown 0:0 debian/piaware/DEBIAN/md5sums

dh_builddeb
dpkg-deb --build debian/piaware …
dpkg-deb: building package piaware' in …/piaware_3.0.5_armhf.deb’.
dpkg-genchanges -b >…/piaware_3.0.5_armhf.changes
dpkg-genchanges: binary-only upload (no source code included)
dpkg-source --after-build package-jessie
dpkg-buildpackage: binary-only upload (no source included)

5

OK thanks to both of you for your advice.

I am not very skilled at the linux game, but I am prepared to try.

I used the ready made scripts produced by Joe to install the system on my old debian netbook. The scripts constrain me on what I can load and they seek out the up to date software components and install them. I just went in and re-installed using Joe’s install.sh script from here:

adsbreceiver.net/2016/09/15 … -released/

using the commands indicated for an upgrade rather than a clean new install. These are the commands:

cd ~/adsb-receiver
git fetch --all
git reset --hard origin/master
./install.sh

Unfortunately, the procedure just reinstalled the Piaware 3.01 and not the recommended 3.05 (as in obj’s remarks above. I haven’t seen the version yet of mlat client, but I am sure it will be the out of date one which I think was 2.05.

I will try and do jonhawkes2030 procedure and hope it doesn’t try and install an arm version rather than an x86 one, or I will be really ‘up the creek’.

Fingers crossed.

6

OK…

I did what Johnhawks said and copied his commands into a putty window to enact on the linux netbook.

It went well up until the end when I got this error message after enacting the command line:

sudo dpkg -i …/piaware_3.0.5_armhf.deb

"dpkg: error processing archive … /piaware_3.05_armhf.deb (–install):
cannot access archive: No such file or directory

errors were encountered while processing …/piaware_3.0.5_armhf.deb"

Just tested it…

Completely bust now. No dump1090 mutability. No piaware… :frowning:

7

search for a file starting with piaware_3.0.5 in your home directory

Then install it using dpkg -i “filename”

This should not have broken anything. All you did was compile a later version of flightware. If it was not installed then nothing should have changed.

If you also need to upgrade dump1090-mutability then these commands will do it

git clone github.com/mutability/dump1090.git
cd dump1090
dpkg-buildpackage -b
sudo dpkg -i …/dump1090-mutability_1.15~dev_armhf.deb
(Change filename to the one that was created by the build process)

It looks like piaware has been upgraded but no data is being sent

** Data Feed: Today - about 3 hours ago
Feeder Check-in: Live - 58 minutes ago**
Joined: 23/07/2016
Longest Streak: 42 days (09/08/2016 - Today)

Feeder Type: PiAware (Debian Package Add-on)** 3.0.5**
Multilateration (MLAT): Supported / Enabled

Maybe try another reboot or check the dump1090 logs.

8

you could also try to delete the original adsb-receiver dir and start again
(the MLAT client should be updated when piaware is updated)
cd
rm -r ~/adsb-receiver
cd ~/adsb-receiver
git fetch --all
git reset --hard origin/master
./install.sh

9

I will admit the scripts are all about the latest and greatest and this is on purpose. That being said I am perplexed as to why PiAware did not upgrade to the latest build available. When prompted to did you select to update/reinstall PiAware when after running ./install.sh? If for some reason you were not prompted to upgrade PiAware let me know.

Lets make sure you are in fact running an older version of PiAware and not a later version after running the scripts again.
Execute the following command…


aptitude versions piaware

You should see something like so displaying what version of PiAware is installed.


pi@adsbreceiver:~/Projects/adsb-receiver $ aptitude versions piaware
Package piaware:
i   3.0.5

Also…
I will keep an eye on this thread for responses but for anyone else reading this and using my code to set up their receivers who have questions and/or issues I would be more than happy to help you troubleshoot any problems encountered but I ask that you use the following thread to discus them.

ads-b-flight-tracking-f21/ads-b-receiver-project-setup-scripts-t36532.html

It is just too hard to follow all discussions on multiple forums where things pertaining to the scripts reside. Besides that I am sure the folks at FlightAware would rather have discussions on my project limited down to a single thread as well.