I have a small problem here, set up a new feeder based on arm64 Debian.
Compiled and installed dump1090-fa just fine, build piaware using piaware-builder and installed everything.
Dump1090-fa works, piaware works but mlat-client does not work.
systemctl status reports:
mlat-client(3637): Fatal Python error: initfsencoding: Unable to get the locale encoding
mlat-client(3637): ImportError: invalid flags 1554269952 in ‘encodings’
mlat-client(3637): Current thread 0x0000007fa2bfa010 (most recent call first):
got EOF from multilateration client
fa-mlat-client exited with SIG SIGABRT
How do I get mlat-client working as the issue is related to an incompatibility with Python3 as google suggests.
As it is now confirmed that cx_Freez-5.1.1 is causing mlat/Python3 issue on some distros/architecture, hopefully @obj will take care of it in the next version of piaware_builder.
I used the dev branch building for Buster, and MLAT worked great - but ADS-B upload stopped completely. FAUP1090 was running, and I could see position data on stdout; but nothing seemed to be getting to the statistics page. Planes could be seen on the local webserver.
I’ve gone back to master, building for Debian Stretch, and ADS-B works fine, but, of course, no MLAT. Any ideas?
@obj
About half an hour ago on Debian 10.2 amd64, I finished installing Piaware 3.8.0~dev and dump1090-mutbility EB_VERSION. All seems OK on local checks. On stats page three buttons are green, but stats are not populating.
Dec 10 12:38:58 debian piaware[1952]: creating pidfile /run/piaware/piaware.pid
Dec 10 12:38:58 debian piaware[1952]: ****************************************************
Dec 10 12:38:58 debian piaware[1952]: piaware version 3.8.0~dev is running, process ID 1952
Dec 10 12:38:58 debian piaware[1952]: your system info is: Linux debian 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux
Dec 10 12:39:00 debian piaware[1952]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Dec 10 12:39:00 debian piaware[1952]: Connection with adept server at piaware.flightaware.com/1200 established
Dec 10 12:39:00 debian piaware[1952]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Dec 10 12:39:00 debian piaware[1952]: FlightAware server certificate validated
Dec 10 12:39:00 debian piaware[1952]: encrypted session established with FlightAware
Dec 10 12:39:01 debian piaware[1952]: adept reported location: 43.xxxxx, -79.xxxxx, 4xxft AMSL
Dec 10 12:39:01 debian piaware[1952]: Receiver location changed, restarting dump1090 and skyaware978
Dec 10 12:39:01 debian piaware[1952]: attempting to restart dump1090..
Dec 10 12:39:01 debian piaware[1952]: can't restart dump1090, no services that look like dump1090 found
Dec 10 12:39:01 debian piaware[1952]: attempting to restart skyaware978..
Dec 10 12:39:01 debian piaware[1952]: can't restart skyaware978, no services that look like skyaware978 found
Dec 10 12:39:01 debian piaware[1952]: logged in to FlightAware as user abcd567
Dec 10 12:39:01 debian piaware[1952]: my feeder ID is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Dec 10 12:39:01 debian piaware[1952]: site statistics URL: https://flightaware.com/adsb/stats/user/abcd567#stats-114692
Dec 10 12:39:01 debian piaware[1952]: NOTICE from adept server: Use of development versions of piaware is not recommended. Please use a supported stable version.
Dec 10 12:39:01 debian piaware[1952]: ADS-B data program 'dump1090-mutab' is listening on port 30005, so far so good
Dec 10 12:39:01 debian piaware[1952]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.xxx --lon -79.xxx
Dec 10 12:39:01 debian piaware[1952]: Started faup1090 (pid 1967) to connect to dump1090-mutab
Dec 10 12:39:01 debian piaware[1952]: UAT support disabled by local configuration setting: uat-receiver-type
Dec 10 12:39:01 debian piaware[1952]: multilateration data requested
Dec 10 12:39:02 debian piaware[1952]: 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.204:8624:4108051657
Dec 10 12:39:02 debian piaware[1952]: mlat-client(1970): fa-mlat-client 0.2.11 starting up
Dec 10 12:39:02 debian piaware[1952]: mlat-client(1970): Using UDP transport to 70.42.6.204 port 8624
Dec 10 12:39:02 debian piaware[1952]: mlat-client(1970): Listening for Beast-format results connection on port 30105
Dec 10 12:39:02 debian piaware[1952]: mlat-client(1970): Listening for Extended Basestation-format results connection on port 30106
Dec 10 12:39:02 debian piaware[1952]: mlat-client(1970): Route MTU changed to 1500
Dec 10 12:39:02 debian piaware[1952]: mlat-client(1970): Input connected to localhost:30005
Dec 10 12:39:02 debian piaware[1952]: mlat-client(1970): Input format changed to BEAST, 12MHz clock
Dec 10 12:39:02 debian piaware[1952]: piaware received a message from dump1090-mutab!
Dec 10 12:39:03 debian piaware[1952]: mlat-client(1970): Beast-format results connection with ::1:30104: connection established
Dec 10 12:39:06 debian piaware[1952]: piaware has successfully sent several msgs to FlightAware!
Dec 10 12:39:33 debian piaware[1952]: 25 msgs recv'd from dump1090-mutab; 25 msgs sent to FlightAware
Dec 10 12:44:33 debian piaware[1952]: 187 msgs recv'd from dump1090-mutab (162 in last 5m); 187 msgs sent to FlightAware
Dec 10 12:49:33 debian piaware[1952]: 456 msgs recv'd from dump1090-mutab (269 in last 5m); 456 msgs sent to FlightAware
abcd@debian:~/piaware_builder$ git checkout dev
Branch 'dev' set up to track remote branch 'dev' from 'origin'.
Switched to a new branch 'dev'
abcd@debian:~/piaware_builder$ git log
commit f6ab1594567cf3cf1ed3252278a6cd1f0084702a (HEAD -> dev, origin/dev)
Author: Oliver Jowett <oliver@mutability.co.uk>
Date: Thu Nov 28 13:41:46 2019 +0800
Add a rule for building on Ubuntu disco per report on the forums
OK; this is probably just that the server side hasn’t been updated to process data from 3.8.0~dev yet. (it’s mostly there but it looks like we missed one spot)