Error message trying to install PiAware on MX Linux

FlightAware ADS-B Flight Tracking
1

Hi,

I’m running Linux MX (19.2 386) on an old laptop. My hope is to use my old unused laptop as a permanent contributor to FlightAware.

Following the guide here: [OUTDATED] Howto Install Piaware 3.8.1 on Ubuntu 18 & 19 and Debian 10 amd64 on PC

I have successfully installed Dump1090-fa 3.81 and it works! (I can see aircraft).

However I have problems with installing PiAware.
I follow the instructions all the way until ( 3.3 - Clone piaware source code, build package, and install package.)
Using Case 3 I am unable to “git clone GitHub - flightaware/piaware_builder: Debian package builder for piaware” because it asks me for a username and password? Instead I downloaded the .zip file from github and used that.

I use the script “./sensible-build.sh buster” which runs and then fails with this error…

error: RPC failed, curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet.
fatal: early EOF
fatal: index-pack failed

Any ideas?

2

Another related Howto, though it may not solve your current error message issue.

Installed Piaware Data Feeder on MX-Linux on Intel PC

3

Regarding error message, it may be due to tcl-tls. Do not install it from repository. Build tcltls-rebuild from source code.

(1) Please go to this post:

Howto Install Piaware 3.8.1 on 64 bit Raspbian OS / Pi4

(2) Scroll down to following item:
3.2 - Build & Install dependency tcl-tls from source code.

4

Hi abcd567,
I’ve seen your posts all over the place on here and other ADS-B sites. So thanks for your contribution!

I followed your first link. It looks similar except for a different set of dependencies. I worked through the list. Most were already installed, some couldn’t be found, and some new ones installed.
Anyway running the “./sensible-build.sh buster” it completed! The package built, and the package installed.

I think I’m good to go. I need to work on the configuration next. It’s also not clear to me if I need to start dump1090-fa to make this all work? Or if the PiAware is now running automatically?

It’s 0109am here in the UK and I’ve been trying to get this to work for the last 6-7 hours… time for bed!

1 Like
5

MX-Linux by default disables systemd, and startup is by sysV init.d files.

Both the dump1090-fa and piaware are designed to start by systemd. I am not sure if they provide sysV init.d files. You will need to enable systemd to make these start automatically.

Quote from my 2018 post in FR24 forum:

Although MX-Linux is shipped with both systemd and sysvinit, by default systemd is disabled. The developers of MX-Linux recommend to keep systemd disabled, and use sysvinit.

Dump1090-mutability, FR24Feeder, Plane Finder Feeder, and FlightAware Feeder detect that systemd has been disabled, and install startup files in /etc/init.d folder for sysvinit. Unfortunately Opensky network feeder does not install the init file needed by sysvinit. It installs only .service files for systemd. As a result, Opensky feeder does not start at boot, and cannot be started manually as well by command “sudo service opensky start”. This situation can be overcome either by enabling systemd OR manually creating init file.

The systemd can be enabled at boot when Grub is displayed. Choose advanced boot option, and in that option enable systemd.

6

0137 and I’m still up!

I restarted my computer.
looking at the piaware.log I can see it has correctly connected and logged in to FlightAware with my username (quite clever because I haven’t touched a config file!).

However it says no ADS-B data program is serving on port 30005.

What do I need to do here? Is this something to do with systemd? FlightAware seems to have started ok.

7

It is dump1090-fa which serves data on port 30005.

Check status of dump1090-fa, first by systemd command, and if it does not work (not found), then by sysVinit command

sudo systemctl status dump1090-fa
sudo service dump1090-fa status
sudo /etc/initd/dump1090-fa start

EDIT

After installing dump1090-fa, did you reboot the computer? If not, then reboot computer and check again.

8

sudo systemctl status dump1090-fa
System has not been booted with systemd as init system (PID 1). Can’t operate.
Failed to connecy to bus: Host is down

service dump1090-fa status
dump1090-fa: unrecognised service

/etc/initd/dump1090-fa start
bash: /etc/initd/dump1090-fa: No such file or directory

The Local Flightaware server shows the error

  • Problem fetching data from dump1090.
    AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
    The displayed map data will be out of date.*
9

What are the outputs of these two commands?

apt-cache policy dump1090-fa

sudo find / -name dump1090-fa

10

apt-cache policy dump1090-fa
Installed: 3.8.1
Candidate: 3.8.1
Version table:
*** 3.8.1 100
100 /var/lib/dpkg/status

sudo find / -name dump1090-fa
*/dump1090-fa
/dump1090-fa/debian/dump1090-fa
/dump1090-fa/debian/dump1090-fa/usr/share/dump1090-fa
/dump1090-fa/debian/dump1090-fa/usr/share/doc/dump1090-fa
/dump1090-fa/debian/dump1090-fa/usr/bin/dump1090-fa
/dump1090-fa/debian/dump1090-fa/etc/default/dump1090-fa
/dump1090-fa/debian/.debhelper/dump1090-fa
/dump1090-fa/debian/.debhelper/generated/dump1090-fa
/usr/share/dump1090-fa
/usr/share/doc/dump1090-fa
/usr/bin/dump1090-fa
find: ‘/proc/3256/task/3256/net’: Invalid argument
find: ‘/proc/3256/net’: Invalid argument
/etc/default/dump1090-fa
find: ‘/run/user/1000/gvfs’: Permission denied
*

11

Just type dump1090-fa and press Enter key. What do you see? If there is continous flow of output, press Ctrl+C keys to break it.

Note:
You can post the output with [code] above it and [/code] below it to display properly formatted code.

12 
$ dump1090-fa
Tue Jun  9 22:57:03 2020 BST  dump1090-fa 3.8.1 starting up.
rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Detached kernel driver
Found Rafael Micro R820T tuner
rtlsdr: tuner gain set to 49.6 dB
Allocating 4 zero-copy buffers

The output holds here until I pickup an aircraft (not a lot flying and I need to sort out a better antenna).

Does installing dump1090-fa supposed to make it start with system start and run in background?
Even when I start manually like above (I’ve used the --interactive to better show acft), it still doesn’t seem to put data for Piaware to send? Piaware seems to think it’s not running.

13

Have a look at my stats page. Something is getting through…
https://flightaware.com/adsb/stats/user/boulmerboy

However I’m getting nothing on local:8080 shown

**Problem fetching data from dump1090.**
AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
The displayed map data will be out of date.
14

Seems the installation did not go properly and did not install startup files.

Purge the installation, then reinstall, and reboot by following command, then check if piaware stopped complaining “no program listening at port 30005”.

sudo dpkg --purge dump1090-fa 

sudo dpkg -i dump1090-fa_3.8.1_*.deb 

sudo reboot
15

I originally installed dump1090-fa as root (does that make any difference?)
Anyway I have reinstalled with sudo and the commands you listed above. All completed successfully.

Everything seems to be exactly the same as before.

I tried manually starting dump1090-fa and then running sudo service dump1090-fa status
I still get dump1090-fa: unrecognised service even though I know it’s running.

16

What is expected behaviour if I do not see any aircraft?

Will I get:

**Problem fetching data from dump1090.**
AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
The displayed map data will be out of date.
17

Not seeing an aircraft may be because of dump1090 is not running. In this case you will get:

Problem fetching data from dump1090.** AJAX call failed (error: Not Found). Maybe dump1090 is no longer running? The displayed map data will be out of date.

 

It may also be because of some problem with the dvbt dongle or some problem with antenna and coax. In that case you will not see the AJAX warning quoted above.

Does piaware stop complaining “no adsb program listening on port 30005”, or still complaining. If dump1090-fa is running ok, even with no planes (due to problems with antenna/coax/connectors, or no flight), piaware will not complain “no program listening on port 30005”. Instead it will say “0 messages received”.

18

cat /var/log/piware.log

refused
2020-06-09 21:30:33Z mlat-client(8208): Reconnecting in 30.0 seconds
2020-06-09 21:30:35Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 21:30:35Z attempting to start dump1090.. 
2020-06-09 21:30:35Z can't start dump1090, no services that look like dump1090 found
2020-06-09 21:30:40Z piaware (process 2615) is shutting down because it received a shutdown signal (SIGTERM) from the system...
2020-06-09 21:30:40Z multilateration data no longer required, disabling mlat client
2020-06-09 21:30:41Z fa-mlat-client exited normally
2020-06-09 21:30:41Z removing pidfile /run/piaware/piaware.pid
2020-06-09 21:30:41Z piaware (process 2615) is exiting...
2020-06-09 21:32:06Z creating pidfile /run/piaware/piaware.pid
2020-06-09 21:32:06Z ****************************************************
2020-06-09 21:32:06Z piaware version 3.8.1 is running, process ID 2630
2020-06-09 21:32:06Z your system info is: Linux eeeLinux 4.19.0-9-686-pae #1 SMP Debian 4.19.118-2 (2020-04-29) i686 GNU/Linux
2020-06-09 21:32:07Z Connecting to FlightAware adept server at piaware.flightaware.com/1200
2020-06-09 21:32:07Z Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Name or service not known
2020-06-09 21:32:07Z reconnecting in 4 seconds...
2020-06-09 21:32:09Z no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
2020-06-09 21:32:09Z UAT support disabled by local configuration setting: uat-receiver-type
2020-06-09 21:32:11Z Connecting to FlightAware adept server at piaware.flightaware.com/1200
2020-06-09 21:32:11Z Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Name or service not known
2020-06-09 21:32:11Z reconnecting in 5 seconds...
2020-06-09 21:32:16Z Connecting to FlightAware adept server at 70.42.6.156/1200
2020-06-09 21:32:16Z Connection to adept server at 70.42.6.156/1200 failed: couldn't open socket: network is unreachable
2020-06-09 21:32:16Z reconnecting in 5 seconds...
2020-06-09 21:32:21Z Connecting to FlightAware adept server at 70.42.6.191/1200
2020-06-09 21:32:21Z Connection with adept server at 70.42.6.191/1200 established
2020-06-09 21:32:22Z TLS handshake with adept server at 70.42.6.191/1200 completed
2020-06-09 21:32:22Z FlightAware server certificate validated
2020-06-09 21:32:22Z encrypted session established with FlightAware
2020-06-09 21:32:27Z adept reported location: 55.07624, -1.52876, 141ft AMSL
2020-06-09 21:32:27Z logged in to FlightAware as user boulmerboy
2020-06-09 21:32:27Z my feeder ID is 8d002500-348c-4d86-aff9-eb85e5d3b042
2020-06-09 21:32:27Z site statistics URL: https://flightaware.com/adsb/stats/user/boulmerboy#stats-129677
2020-06-09 21:32:27Z multilateration data requested
2020-06-09 21:32:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:32:40Z 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
2020-06-09 21:33:09Z no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
2020-06-09 21:33:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:34:09Z no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s
2020-06-09 21:34:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:35:09Z no ADS-B data program seen listening on port 30005 for 183 seconds, next check in 60s
2020-06-09 21:35:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:36:10Z no ADS-B data program seen listening on port 30005 for 244 seconds, next check in 60s
2020-06-09 21:36:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:37:10Z no ADS-B data program seen listening on port 30005 for 304 seconds, next check in 60s
2020-06-09 21:37:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:37:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 21:38:10Z no ADS-B data program seen listening on port 30005 for 364 seconds, trying to start it...
2020-06-09 21:38:10Z attempting to start dump1090.. 
2020-06-09 21:38:10Z can't start dump1090, no services that look like dump1090 found
2020-06-09 21:38:20Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 21:38:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:39:20Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 21:39:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:40:20Z no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
2020-06-09 21:40:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:41:20Z no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
2020-06-09 21:41:28Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:42:20Z no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
2020-06-09 21:42:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:42:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 21:43:20Z no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
2020-06-09 21:43:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:44:20Z no ADS-B data program seen listening on port 30005 for 370 seconds, trying to start it...
2020-06-09 21:44:20Z attempting to start dump1090.. 
2020-06-09 21:44:20Z can't start dump1090, no services that look like dump1090 found
2020-06-09 21:44:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:44:31Z no ADS-B data program seen listening on port 30005 for 11 seconds, next check in 60s
2020-06-09 21:45:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:45:31Z no ADS-B data program seen listening on port 30005 for 71 seconds, next check in 60s
2020-06-09 21:46:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:46:31Z no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
2020-06-09 21:47:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:47:31Z no ADS-B data program seen listening on port 30005 for 191 seconds, next check in 60s
2020-06-09 21:47:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 21:48:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:48:31Z no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
2020-06-09 21:49:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:49:31Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 21:50:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:50:31Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 21:50:31Z attempting to start dump1090.. 
2020-06-09 21:50:31Z can't start dump1090, no services that look like dump1090 found
2020-06-09 21:50:41Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 21:51:29Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:51:41Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 21:52:30Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:52:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 21:52:42Z no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
2020-06-09 21:53:30Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:53:42Z no ADS-B data program seen listening on port 30005 for 191 seconds, next check in 60s
2020-06-09 21:54:30Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:54:42Z no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
2020-06-09 21:55:30Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:55:42Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 21:56:30Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:56:42Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 21:56:42Z attempting to start dump1090.. 
2020-06-09 21:56:42Z can't start dump1090, no services that look like dump1090 found
2020-06-09 21:56:52Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 21:57:30Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:57:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 21:57:52Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 21:58:30Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:58:53Z no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
2020-06-09 21:59:31Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 21:59:53Z no ADS-B data program seen listening on port 30005 for 191 seconds, next check in 60s
2020-06-09 22:00:37Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:00:53Z no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
2020-06-09 22:01:40Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:01:53Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 22:02:40Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:02:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:02:53Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 22:02:53Z attempting to start dump1090.. 
2020-06-09 22:02:53Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:03:03Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 22:03:40Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:04:03Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 22:04:40Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:05:04Z no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
2020-06-09 22:05:40Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:06:04Z no ADS-B data program seen listening on port 30005 for 191 seconds, next check in 60s
2020-06-09 22:06:40Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:07:04Z no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
2020-06-09 22:07:40Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:07:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:08:04Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 22:08:40Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:09:04Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 22:09:04Z attempting to start dump1090.. 
2020-06-09 22:09:04Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:09:14Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 22:09:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:10:14Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 22:10:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:11:14Z no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
2020-06-09 22:11:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:12:14Z no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
2020-06-09 22:12:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:12:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:13:14Z no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
2020-06-09 22:13:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:14:15Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 22:14:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:15:15Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 22:15:15Z attempting to start dump1090.. 
2020-06-09 22:15:15Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:15:25Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 22:15:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:16:25Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 22:16:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:17:25Z no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
2020-06-09 22:17:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:17:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:18:25Z no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
2020-06-09 22:18:41Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:19:25Z no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
2020-06-09 22:19:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:20:25Z no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
2020-06-09 22:20:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:21:25Z no ADS-B data program seen listening on port 30005 for 370 seconds, trying to start it...
2020-06-09 22:21:25Z attempting to start dump1090.. 
2020-06-09 22:21:25Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:21:36Z no ADS-B data program seen listening on port 30005 for 11 seconds, next check in 60s
2020-06-09 22:21:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:22:36Z no ADS-B data program seen listening on port 30005 for 71 seconds, next check in 60s
2020-06-09 22:22:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:22:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:23:36Z no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
2020-06-09 22:23:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:24:36Z no ADS-B data program seen listening on port 30005 for 191 seconds, next check in 60s
2020-06-09 22:24:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:25:36Z no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
2020-06-09 22:25:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:26:36Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 22:26:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:27:36Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 22:27:36Z attempting to start dump1090.. 
2020-06-09 22:27:36Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:27:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:27:42Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:27:46Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 22:28:43Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:28:46Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 22:29:43Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:29:46Z no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
2020-06-09 22:30:43Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:30:46Z no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
2020-06-09 22:31:43Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:31:47Z no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
2020-06-09 22:32:40Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:32:43Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:32:47Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 22:33:35Z piaware (process 2630) is shutting down because it received a shutdown signal (SIGTERM) from the system...
2020-06-09 22:33:35Z multilateration data no longer required, disabling mlat client
2020-06-09 22:33:35Z removing pidfile /run/piaware/piaware.pid
2020-06-09 22:33:35Z piaware (process 2630) is exiting...
2020-06-09 22:35:03Z creating pidfile /run/piaware/piaware.pid
2020-06-09 22:35:03Z ****************************************************
2020-06-09 22:35:03Z piaware version 3.8.1 is running, process ID 2619
2020-06-09 22:35:03Z your system info is: Linux eeeLinux 4.19.0-9-686-pae #1 SMP Debian 4.19.118-2 (2020-04-29) i686 GNU/Linux
2020-06-09 22:35:04Z Connecting to FlightAware adept server at piaware.flightaware.com/1200
2020-06-09 22:35:04Z Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: Name or service not known
2020-06-09 22:35:04Z reconnecting in 5 seconds...
2020-06-09 22:35:06Z no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
2020-06-09 22:35:06Z UAT support disabled by local configuration setting: uat-receiver-type
2020-06-09 22:35:09Z Connecting to FlightAware adept server at piaware.flightaware.com/1200
2020-06-09 22:35:10Z Connection with adept server at piaware.flightaware.com/1200 established
2020-06-09 22:35:10Z TLS handshake with adept server at piaware.flightaware.com/1200 completed
2020-06-09 22:35:10Z FlightAware server certificate validated
2020-06-09 22:35:10Z encrypted session established with FlightAware
2020-06-09 22:35:11Z adept reported location: 55.07624, -1.52876, 141ft AMSL
2020-06-09 22:35:11Z logged in to FlightAware as user boulmerboy
2020-06-09 22:35:11Z my feeder ID is 8d002500-348c-4d86-aff9-eb85e5d3b042
2020-06-09 22:35:11Z site statistics URL: https://flightaware.com/adsb/stats/user/boulmerboy#stats-129677
2020-06-09 22:35:11Z multilateration data requested
2020-06-09 22:35:11Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:35:37Z 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
2020-06-09 22:36:06Z no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
2020-06-09 22:36:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:37:06Z no ADS-B data program seen listening on port 30005 for 123 seconds, next check in 60s
2020-06-09 22:37:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:38:06Z no ADS-B data program seen listening on port 30005 for 183 seconds, next check in 60s
2020-06-09 22:38:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:39:07Z no ADS-B data program seen listening on port 30005 for 244 seconds, next check in 60s
2020-06-09 22:39:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:40:07Z no ADS-B data program seen listening on port 30005 for 304 seconds, next check in 60s
2020-06-09 22:40:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:40:37Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:41:07Z no ADS-B data program seen listening on port 30005 for 364 seconds, trying to start it...
2020-06-09 22:41:07Z attempting to start dump1090.. 
2020-06-09 22:41:07Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:41:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:41:17Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 22:42:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:42:17Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 22:43:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:43:17Z no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
2020-06-09 22:44:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:44:17Z no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
2020-06-09 22:45:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:45:17Z no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
2020-06-09 22:45:37Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:46:12Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:46:17Z no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
2020-06-09 22:47:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:47:17Z no ADS-B data program seen listening on port 30005 for 370 seconds, trying to start it...
2020-06-09 22:47:17Z attempting to start dump1090.. 
2020-06-09 22:47:17Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:47:28Z no ADS-B data program seen listening on port 30005 for 11 seconds, next check in 60s
2020-06-09 22:48:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:48:28Z no ADS-B data program seen listening on port 30005 for 71 seconds, next check in 60s
2020-06-09 22:49:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:49:28Z no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
2020-06-09 22:50:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:50:28Z no ADS-B data program seen listening on port 30005 for 191 seconds, next check in 60s
2020-06-09 22:50:37Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:51:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:51:28Z no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
2020-06-09 22:52:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:52:28Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 22:53:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:53:28Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 22:53:28Z attempting to start dump1090.. 
2020-06-09 22:53:28Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:53:38Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 22:54:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:54:38Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 22:55:13Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:55:37Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 22:55:38Z no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
2020-06-09 22:56:14Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:56:39Z no ADS-B data program seen listening on port 30005 for 191 seconds, next check in 60s
2020-06-09 22:57:14Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:57:39Z no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
2020-06-09 22:58:14Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:58:39Z no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
2020-06-09 22:59:14Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 22:59:39Z no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
2020-06-09 22:59:39Z attempting to start dump1090.. 
2020-06-09 22:59:39Z can't start dump1090, no services that look like dump1090 found
2020-06-09 22:59:49Z no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
2020-06-09 23:00:14Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 23:00:37Z 0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
2020-06-09 23:00:49Z no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
2020-06-09 23:01:14Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 23:01:49Z no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
2020-06-09 23:02:14Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 23:02:49Z no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
2020-06-09 23:03:14Z no ADS-B data program is serving on port 30005, not starting multilateration client yet
2020-06-09 23:03:49Z ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
2020-06-09 23:03:49Z Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 55.076 --lon -1.529
2020-06-09 23:03:49Z Started faup1090 (pid 4761) to connect to dump1090-fa
2020-06-09 23:04:14Z Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.232:11711:2872272799
2020-06-09 23:04:15Z mlat-client(4790): fa-mlat-client 0.2.11 starting up
2020-06-09 23:04:15Z mlat-client(4790): Using UDP transport to 70.42.6.232 port 11711
2020-06-09 23:04:15Z mlat-client(4790): Listening for Beast-format results connection on port 30105
2020-06-09 23:04:15Z mlat-client(4790): Listening for Extended Basestation-format results connection on port 30106
2020-06-09 23:04:15Z mlat-client(4790): Route MTU changed to 1500
2020-06-09 23:04:15Z mlat-client(4790): Input connected to localhost:30005
2020-06-09 23:04:15Z mlat-client(4790): Input format changed to BEAST, 12MHz clock
2020-06-09 23:04:16Z mlat-client(4790): Beast-format results connection with ::1:30104: connection established
2020-06-09 23:05:37Z 0 msgs recv'd from dump1090-fa (0 in last 5m); 0 msgs sent to FlightAware
simon@eeeLinux:~
19

See the log file above. Something seemed to work towards the end?
I’m not sure if this happened once of the times I manually started dump1090-fa. I’m confused about what is going on.

This is my current understanding

  1. dump1090-fa is installed. If I start the program I can see some aircraft (not many)
  2. PiAware is installed. It seems to be running ok. I can view the local:1080 page but I never see any aircraft (even when I’ve started dump1090-fa and i’m watching the messages come in).
  3. My user stats page on Flightaware shows some acft have been sent through at some point, but not many.
  4. The PiAware log file shows a lot of entries for No ADS-B data program is running on port 30005, but occasionally seems to show it working.
20

ok if I start dump1090-fa with --net I seem to get something happening. I think that may have been what I did when the log file showed the Input connected to localhost:30005 messages.