FlightAware Discussions

How-to Install dump1090-fa and Piaware on Arch Linux x64_86 and on AlarmPi

I have built piaware package for Alarmpi OS as follows:

  • piaware - source code from Github/Flightaware
  • faup1090 - source code at Github/Flightaware
  • fa-mlat-client - source code at Github/mutability
  • tcltls-rebuild - source code at Github/Flightaware
  • dump1090-fa - source code at Github/Flightaware

I feel that the package built from Github/Flightaware/piaware_builder has something extra over the package I built. I tried to build piaware package for Alarmpi using piaware_builder, but it failed due to missing Makefile. I am sure if I could build the piaware package using piaware_builder, the missing buttons issue will go away.

I dont have depth of programming required to find the cause. It will be great if @obj can shed some light.

I don’t TCL but I would suspect the data sent to FA for their server-side matching/rendering comes from info collected during login which appears to be here:
https://github.com/flightaware/piaware/blob/master/programs/piaware/login.tcl

Again, there’s no clear/obvious tie for what FA server-side code is looking for or comparing to but looks like you could hardcode some data in that file instead of letting it query your alarmpi and get the buttons back :wink:
And back to not doing TCL… you may have to recompile?

1 Like

Missing buttons happen with both AlarmPi (Stn 76000) and Arch Linux amd64 (Stn 114692)

With Stn 76000 (RPi Model 4), I normally use Raspbian 64-bit OS. I have written Alarmpi 32-bit OS on one spare microSD card, and Alarmpi 64-bit OS on anothe spare microSD card. For trial and testing, I swap the Raspbian microSD card with AlarmPi microSD card, andd after tests, slip out the AlarmPi microSD card and slip in the Raspbian miroSD card.

I have now fired up Arch Linux arm64 and here is the log which shows handshake/login with Flightaware adept servers is OK.

 

[abcd@archlinux ~]$ journalctl -b -u piaware 

-- Journal begins at Mon 2021-02-08 13:04:53 EST, ends at Tue 2021-02-16 00:52:35 EST. --
Feb 16 00:22:29 archlinux systemd[1]: Started FlightAware ADS-B uploader.
Feb 16 00:22:43 archlinux piaware[362]: creating pidfile /run/piaware/piaware.pid
Feb 16 00:22:43 archlinux piaware[362]: ****************************************************
Feb 16 00:22:43 archlinux piaware[362]: piaware version 4.0 is running, process ID 362
Feb 16 00:22:43 archlinux piaware[362]: your system info is: Linux archlinux 5.10.16-arch1-1 #1 SMP PREEMPT Sat, 13 Feb 2021 20:50:18 +0000 x86_64 GNU/Linux
Feb 16 00:22:45 archlinux piaware[362]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 16 00:22:45 archlinux piaware[362]: Connection with adept server at piaware.flightaware.com/1200 established
Feb 16 00:22:45 archlinux piaware[362]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Feb 16 00:22:45 archlinux piaware[362]: FlightAware server certificate validated
Feb 16 00:22:45 archlinux piaware[362]: encrypted session established with FlightAware
Feb 16 00:22:46 archlinux sudo[519]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 16 00:22:47 archlinux piaware[362]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Feb 16 00:22:47 archlinux piaware[362]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 4>
Feb 16 00:22:47 archlinux piaware[362]: Started faup1090 (pid 550) to connect to dump1090-fa
Feb 16 00:22:47 archlinux piaware[362]: UAT support disabled by local configuration setting: uat-receiver-type
Feb 16 00:22:52 archlinux piaware[362]: Lost connection to adept server at piaware.flightaware.com/1200: server closed connection
Feb 16 00:22:52 archlinux piaware[362]: reconnecting in 5 seconds...
Feb 16 00:22:57 archlinux piaware[362]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Feb 16 00:22:57 archlinux piaware[362]: Connection with adept server at piaware.flightaware.com/1200 established
Feb 16 00:22:57 archlinux piaware[362]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Feb 16 00:22:57 archlinux piaware[362]: FlightAware server certificate validated
Feb 16 00:22:57 archlinux piaware[362]: encrypted session established with FlightAware
Feb 16 00:22:57 archlinux piaware[362]: adept reported location: 43.xxxxx, -79.xxxxx, xxxft AMSL
Feb 16 00:22:57 archlinux piaware[362]: logged in to FlightAware as user abcd567
Feb 16 00:22:57 archlinux piaware[362]: my feeder ID is b600xxxx-xxxx-xxxx-xxxx-xxxxxxxx52c1
Feb 16 00:22:57 archlinux piaware[362]: site statistics URL: https://flightaware.com/adsb/stats/user/abcd567#stats-114692
Feb 16 00:22:57 archlinux piaware[362]: multilateration data requested
Feb 16 00:22:57 archlinux sudo[707]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Feb 16 00:22:57 archlinux sudo[707]:  piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Feb 16 00:22:57 archlinux piaware[362]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-ty>
Feb 16 00:22:57 archlinux sudo[707]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=962)
Feb 16 00:22:57 archlinux sudo[707]: pam_unix(sudo:session): session closed for user root
Feb 16 00:22:58 archlinux piaware[362]: mlat-client(716): fa-mlat-client 0.2.11 starting up
Feb 16 00:22:58 archlinux piaware[362]: mlat-client(716): Using UDP transport to 2600:c13:1002:4::232 port 11708
Feb 16 00:22:58 archlinux piaware[362]: mlat-client(716): Listening for Beast-format results connection on port 30105
Feb 16 00:22:58 archlinux piaware[362]: mlat-client(716): Listening for Extended Basestation-format results connection on port 30106
Feb 16 00:22:58 archlinux piaware[362]: mlat-client(716): Route MTU changed to 1500
Feb 16 00:22:58 archlinux piaware[362]: mlat-client(716): Input connected to localhost:30005
Feb 16 00:22:58 archlinux piaware[362]: mlat-client(716): Input format changed to BEAST, 12MHz clock
Feb 16 00:22:59 archlinux piaware[362]: mlat-client(716): Beast-format results connection with ::1:30104: connection established
Feb 16 00:23:18 archlinux piaware[362]: 0 msgs recv'd from dump1090-fa; 0 msgs sent to FlightAware
Feb 16 00:23:45 archlinux piaware[362]: piaware received a message from dump1090-fa!
Feb 16 00:27:16 archlinux piaware[362]: mlat-client(716): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Feb 16 00:27:16 archlinux piaware[362]: mlat-client(716): Input connected to localhost:30005
Feb 16 00:27:16 archlinux piaware[362]: mlat-client(716): Input format changed to BEAST, 12MHz clock
Feb 16 00:28:18 archlinux piaware[362]: 3 msgs recv'd from dump1090-fa (3 in last 5m); 3 msgs sent to FlightAware
Feb 16 00:30:29 archlinux piaware[362]: mlat-client(716): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Feb 16 00:30:29 archlinux piaware[362]: mlat-client(716): Input connected to localhost:30005
Feb 16 00:30:29 archlinux piaware[362]: mlat-client(716): Input format changed to BEAST, 12MHz clock
Feb 16 00:33:18 archlinux piaware[362]: 3 msgs recv'd from dump1090-fa (0 in last 5m); 3 msgs sent to FlightAware
Feb 16 00:33:28 archlinux piaware[362]: mlat-client(716): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Feb 16 00:33:28 archlinux piaware[362]: mlat-client(716): Input connected to localhost:30005
Feb 16 00:33:28 archlinux piaware[362]: mlat-client(716): Input format changed to BEAST, 12MHz clock
Feb 16 00:35:58 archlinux piaware[362]: mlat-client(716): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Feb 16 00:35:58 archlinux piaware[362]: mlat-client(716): Input connected to localhost:30005
Feb 16 00:35:58 archlinux piaware[362]: mlat-client(716): Input format changed to BEAST, 12MHz clock
Feb 16 00:37:58 archlinux piaware[362]: mlat-client(716): Receiver status: connected
Feb 16 00:37:58 archlinux piaware[362]: mlat-client(716): Server status:   not synchronized with any nearby receivers
Feb 16 00:37:58 archlinux piaware[362]: mlat-client(716): Receiver:    0.0 msg/s received        0.0 msg/s processed (83%)
Feb 16 00:37:58 archlinux piaware[362]: mlat-client(716): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.0kB/s UDP to server
Feb 16 00:37:58 archlinux piaware[362]: mlat-client(716): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
Feb 16 00:38:18 archlinux piaware[362]: 3 msgs recv'd from dump1090-fa (0 in last 5m); 3 msgs sent to FlightAware
Feb 16 00:38:29 archlinux piaware[362]: mlat-client(716): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Feb 16 00:38:29 archlinux piaware[362]: mlat-client(716): Input connected to localhost:30005
Feb 16 00:38:29 archlinux piaware[362]: mlat-client(716): Input format changed to BEAST, 12MHz clock
Feb 16 00:40:59 archlinux piaware[362]: mlat-client(716): Disconnecting from localhost:30005: No data (not even keepalives) received for 150 seconds
Feb 16 00:40:59 archlinux piaware[362]: mlat-client(716): Input connected to localhost:30005
Feb 16 00:40:59 archlinux piaware[362]: mlat-client(716): Input format changed to BEAST, 12MHz clock
Feb 16 00:43:18 archlinux piaware[362]: 3 msgs recv'd from dump1090-fa (0 in last 5m); 3 msgs sent to FlightAware
Feb 16 00:44:38 archlinux piaware[362]: piaware has successfully sent several msgs to FlightAware!
Feb 16 00:48:18 archlinux piaware[362]: 23 msgs recv'd from dump1090-fa (20 in last 5m); 23 msgs sent to FlightAware
Feb 16 00:52:58 archlinux piaware[362]: mlat-client(716): Receiver status: connected
Feb 16 00:52:58 archlinux piaware[362]: mlat-client(716): Server status:   not synchronized with any nearby receivers
Feb 16 00:52:58 archlinux piaware[362]: mlat-client(716): Receiver:    0.4 msg/s received        0.3 msg/s processed (64%)
Feb 16 00:52:58 archlinux piaware[362]: mlat-client(716): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.0kB/s UDP to server
Feb 16 00:52:58 archlinux piaware[362]: mlat-client(716): Aircraft: 0 of 0 Mode S, 1 of 1 ADS-B used
Feb 16 00:53:18 archlinux piaware[362]: 39 msgs recv'd from dump1090-fa (16 in last 5m); 39 msgs sent to FlightAware
Feb 16 00:58:18 archlinux piaware[362]: 55 msgs recv'd from dump1090-fa (16 in last 5m); 55 msgs sent to FlightAware

EDIT:

Noted this line in above logs:

Feb 16 00:22:57 archlinux sudo[707]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.

Checked:

[abcd@archlinux ~]$ pacman -Q systemd-homed
error: package 'systemd-homed' was not found

EDIT-2:

[abcd@archlinux ~]$ pacman -Qs pam
local/pam 1.5.1-1
    PAM (Pluggable Authentication Modules) library
local/pambase 20200721.1-2
    Base PAM configuration for services
local/shadow 4.8.1-4
    Password and account management tool suite with support for shadow files and PAM

Was getting this error in Piaware logs:
Feb 16 00:22:57 archlinux sudo[707]: pam_systemd_home(sudo:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.

Did this:
sudo systemctl enable systemd-homed.service
sudo systemctl start systemd-homed.service

Now getting this in Piaware logs:
Feb 16 01:27:57 archlinux sudo[21707]: pam_systemd_home(sudo:account): Not a user managed by systemd-homed: No home for user piaware known

 

Checked “My ADSB” page for Stn 114692. The 3 buttons still missing :slightly_frowning_face:

 

The health buttons are suppressed if the feeder image type is not recognized, as we don’t know what you’re running and whether the health status makes sense or not.

1 Like

Thanks Oliver for solving the riddle I was breaking my head with.
I thought there was something wrong/missing with my installation which was causing this. :slightly_smiling_face:

@obj : I cannot make out why this is happening. Is there something wrong or deficient in my installation? (Arch Lnux amd64 on Oracle VM / Win10 PC)

Feb 20 18:30:04 archlinux piaware[311]: mlat-client(425): Server status: not synchronized with any nearby receivers

https://flightaware.com/adsb/stats/user/abcd567#stats-114692
 

FULL LOG

[abcd@archlinux ~]$ journalctl -e -u piaware

Feb 20 18:14:10 archlinux piaware[311]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Feb 20 18:14:10 archlinux piaware[311]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.>
Feb 20 18:14:10 archlinux piaware[311]: Started faup1090 (pid 1045) to connect to dump1090-fa
Feb 20 18:14:10 archlinux piaware[311]: mlat-client(425): Beast-format results connection with 127.0.0.1:30104: connection established
Feb 20 18:15:04 archlinux piaware[311]: mlat-client(425): Receiver status: connected
Feb 20 18:15:04 archlinux piaware[311]: mlat-client(425): Server status:   not synchronized with any nearby receivers
Feb 20 18:15:04 archlinux piaware[311]: mlat-client(425): Receiver:    7.4 msg/s received        3.6 msg/s processed (49%)
Feb 20 18:15:04 archlinux piaware[311]: mlat-client(425): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.0kB/s UDP to server
Feb 20 18:15:04 archlinux piaware[311]: mlat-client(425): Aircraft: 8 of 10 Mode S, 9 of 12 ADS-B used
Feb 20 18:15:33 archlinux piaware[311]: 1552 msgs recv'd from dump1090-fa (132 in last 5m); 1552 msgs sent to FlightAware
Feb 20 18:20:33 archlinux piaware[311]: 1944 msgs recv'd from dump1090-fa (392 in last 5m); 1944 msgs sent to FlightAware
Feb 20 18:25:33 archlinux piaware[311]: 2282 msgs recv'd from dump1090-fa (338 in last 5m); 2282 msgs sent to FlightAware
Feb 20 18:30:04 archlinux piaware[311]: mlat-client(425): Receiver status: connected
Feb 20 18:30:04 archlinux piaware[311]: mlat-client(425): Server status:   not synchronized with any nearby receivers
Feb 20 18:30:04 archlinux piaware[311]: mlat-client(425): Receiver:   48.6 msg/s received       23.9 msg/s processed (49%)
Feb 20 18:30:04 archlinux piaware[311]: mlat-client(425): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.3kB/s UDP to server
Feb 20 18:30:04 archlinux piaware[311]: mlat-client(425): Aircraft: 7 of 9 Mode S, 11 of 15 ADS-B used
Feb 20 18:30:33 archlinux piaware[311]: 2617 msgs recv'd from dump1090-fa (335 in last 5m); 2617 msgs sent to FlightAware

 

EDIT:

Found the reason. It is due to dongle pass-through from PC to VM

Did this to find out:

[abcd@archlinux ~]$ sudo nano /etc/default/dump1090-fa 
## Added --net-only in NET_OPTIONS
## Restarted dump1090-fa
[abcd@archlinux ~]$ sudo systemctl restart dump1090-fa 

## Pulled data from RPi 
[abcd@archlinux ~]$ socat -u tcp:10.0.0.22:30005 tcp:127.0.0.1:30004 &

## Checked log, found this line
Feb 20 19:00:05 archlinux piaware[311]: mlat-client(425): Server status: synchronized with 196 nearby receivers

 

LOGS

[abcd@archlinux ~]$ journalctl -e -u piaware

Feb 20 18:51:03 archlinux piaware[311]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Feb 20 18:51:03 archlinux piaware[311]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.>
Feb 20 18:51:03 archlinux piaware[311]: Started faup1090 (pid 1155) to connect to dump1090-fa
Feb 20 18:51:31 archlinux piaware[311]: mlat-client(425): Input connected to localhost:30005
Feb 20 18:51:31 archlinux piaware[311]: mlat-client(425): Input format changed to BEAST, 12MHz clock
Feb 20 18:51:31 archlinux piaware[311]: mlat-client(425): Beast-format results connection with ::1:30104: connection established
Feb 20 18:55:33 archlinux piaware[311]: 4850 msgs recv'd from dump1090-fa (650 in last 5m); 4850 msgs sent to FlightAware
Feb 20 19:00:05 archlinux piaware[311]: mlat-client(425): Receiver status: connected
Feb 20 19:00:05 archlinux piaware[311]: mlat-client(425): Server status:   synchronized with 196 nearby receivers
Feb 20 19:00:05 archlinux piaware[311]: mlat-client(425): Receiver:   78.5 msg/s received       35.8 msg/s processed (46%)
Feb 20 19:00:05 archlinux piaware[311]: mlat-client(425): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.4kB/s UDP to server
Feb 20 19:00:05 archlinux piaware[311]: mlat-client(425): Aircraft: 6 of 11 Mode S, 13 of 16 ADS-B used
Feb 20 19:00:33 archlinux piaware[311]: 5501 msgs recv'd from dump1090-fa (651 in last 5m); 5501 msgs sent to FlightAware

Would not surprise me. Some VMs drop so much sample data that the mlat server can’t even begin the synchronization process.

To match up messages from two receivers, the mlat server looks for a pair of ADS-B position messages where both messages were received on both receivers with identical contents and approximately the same time interval between messages. Normally, this time interval will be very similar, with at most a few microseconds difference due to differences in receiver location and clock frequency. But if the VM is regularly dropping lots of data, this affects the interval dramatically and pushes it outside the time window that the server considers a match. And you get a “no synchronized receivers” status.

In contrast if you have a clock that’s only a little unstable (or only intermittently dropping samples), the interval will be close enough most of the time for synchronization to be attempted, and then the mlat server notices the clock instability and gives you a “clock unstable” status.

2 Likes