New install on Ubuntu failed with exit code 127

Feeding
1

Hi all,

I recently setup an Ubuntu server and got the Piaware packages running successfully with an Airspy mini feeding to FA.

I tried to setup the ADSB exchange feeder using the usual script but got the following error. I suppose this could be because it is not a standard Piaware install, but I’m not sure.

My old RPi is still running as a client without an active feed since I have moved the Airspy mini over to the new server. I don’t think that would actually be related to the issue, though.

---------------------------------
Sep 26 14:05:26 3060 systemd[1]: Started adsbexchange-mlat.service - adsbexchange-mlat.
Sep 26 14:05:28 3060 adsbexchange-mlat[372908]: Connection to 127.0.0.1 30005 port [tcp/*] succeeded!
Sep 26 14:05:28 3060 adsbexchange-mlat[372833]: /usr/local/share/adsbexchange/adsbexchange-mlat.sh: line 26: /usr/local/share/adsbexchange/venv/bin/mlat-client: No such file or directory
Sep 26 14:05:28 3060 systemd[1]: adsbexchange-mlat.service: Main process exited, code=exited, status=127/n/a
Sep 26 14:05:28 060 systemd[1]: adsbexchange-mlat.service: Failed with result 'exit-code'.
---------------------------------
adsbexchange-mlat service couldn't be started, please report this error to the adsbexchange forum or discord.
Try an copy as much of the output above and include it in your report, thank you!
---------------------------------

Running the ADSB exchange setup script again, skipping the MLAT configuraiton, the installation was successful and I have linked the new feeder to my account.

So I guess the only problem with with MLAT.

Here is the systemctl status:

root@3060:/home/andrew# uname -a
Linux 3060 6.8.0-45-generic #45-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 30 12:02:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

root@3060:/home/andrew# sudo systemctl status adsbexchange-mlat
● adsbexchange-mlat.service - adsbexchange-mlat
     Loaded: loaded (/usr/lib/systemd/system/adsbexchange-mlat.service; enabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2024-09-26 15:09:24 JST; 8s ago
    Process: 395142 ExecStart=/usr/local/share/adsbexchange/adsbexchange-mlat.sh (code=exited, status=127)
   Main PID: 395142 (code=exited, status=127)
        CPU: 24ms

Any hints appreciated. Thanks!

Andrew

2

Ubuntu 24.04 comes with Python 3.12, which introduces a couple breaking changes that affect the MLAT client. AFAIK, at the moment any platform with Python 3.12 (or later) is not supported.

3

I submitted a pull request awhile back fixing the Python 3.12 problem that has not been merged yet. I have tested it and confirmed that MLAT data was being sent. The changes can be found in the branch named trixie in my fork of piaware_builder if you want to give it a shot.

jprochazka/piaware_builder at trixie

In all honesty I am not expecting a Python 3.12 fix for PiAware any time before Debian releases Trixie being FlightAware tends to treat Ubuntu as a second-class citizen.

Also keep in mind if you are trying to build and install PiAware on Ubuntu 24.10 Oracular Oriole you will have a bad time as well being there are a couple syntax issues in dump1090-fa’s source code which the GCC compiler in Oracular does not like. Being piaware_builder is dependent on dump1090-fa’s source code the problem affects PiAware as well. According to the comments in this pull request the syntax fix is supposed to be part of the next dump1090 release so maybe we will see an Ubuntu related fix sooner rather than later for once. :wink:

4

I got the Same issue… :confused: