# MLAT stopped? **URL:** \ **Category:** ADS-B Flight Tracking\ **Created:** [September 14, 2024, 5:47am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642 "2024-09-14T05:47:13Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![voyteke](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/voyteke/32/114354_2.png) [@voyteke](https://discussions.flightaware.com/u/voyteke)\ **Post date:** [September 14, 2024, 5:47am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/1 "2024-09-14T05:47:13Z")
I have RTL SDR on RPi with piaware since about 1 year, working well, few days ago checking my lat/lon I though I might be out maybe ~5 metres ?, so using gmaps got better lat/lon, reentered lat/lon through FA i/f, also, edited TZ to Sydney - not sure if that is relevant ?, just noticed since few days my MLAT dropped to zero ? ![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/9/8/9851a14aa8266fab2cda6fd93a42da6a97cbda53.png) ![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/6/1/615230b7f20738dc05d3832e6e4d1b99aa55ca21.png) ● piaware.service - FlightAware ADS-B uploader Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2024-09-14 15:36:10 AEST; 31s ago Docs: [PiAware - ADS-B and MLAT Receiver - FlightAware](https://flightaware.com/adsb/piaware/) Main PID: 1318917 (piaware) Tasks: 4 (limit: 3930) CPU: 1.163s CGroup: /system.slice/piaware.service ├─1318917 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json ├─1318940 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat → └─1318943 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 → Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): fa-mlat-client 0.2.13 starting up Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Using UDP transport to 206.253.80.201 port 5406 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Listening for Beast-format results connection on port 30105 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Listening for Extended Basestation-format results connecti\> Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Route MTU changed to 1500 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Input connected to localhost:30005 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Input format changed to BEAST, 12MHz clock Sep 14 15:36:14 rpi2 piaware[1318917]: piaware received a message from dump1090-fa! Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Beast-format results connection with ::1:30104: connection\> Sep 14 15:36:14 rpi2 piaware[1318917]: piaware has successfully sent several msgs to FlightAware! Sep 14 15:36:10 rpi2 piaware[1301073]: faup1090 exited with SIG SIGTERM Sep 14 15:36:10 rpi2 piaware[1301073]: multilateration data no longer required, disabling mlat client Sep 14 15:36:10 rpi2 piaware[1301073]: fa-mlat-client exited with SIG SIGTERM Sep 14 15:36:10 rpi2 piaware[1301073]: removing pidfile /run/piaware/piaware.pid Sep 14 15:36:10 rpi2 piaware[1301073]: piaware (process 1301073) is exiting… Sep 14 15:36:10 rpi2 piaware[1318917]: creating pidfile /run/piaware/piaware.pid Sep 14 15:36:10 rpi2 piaware[1318917]: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Sep 14 15:36:10 rpi2 piaware[1318917]: piaware version 9.0.1 is running, process ID 1318917 Sep 14 15:36:10 rpi2 piaware[1318917]: your system info is: Linux rpi2 6.6.26-v8+ #1754 SMP PREEMPT Thu Apr 11 14:49:11 BST 2024 aarch64 GNU/Linux Sep 14 15:36:12 rpi2 piaware[1318917]: Connecting to FlightAware adept server at [piaware.flightaware.com/1200](http://piaware.flightaware.com/1200) Sep 14 15:36:12 rpi2 piaware[1318917]: Connection with adept server at [piaware.flightaware.com/1200](http://piaware.flightaware.com/1200) established Sep 14 15:36:12 rpi2 piaware[1318917]: TLS handshake with adept server at [piaware.flightaware.com/1200](http://piaware.flightaware.com/1200) completed Sep 14 15:36:12 rpi2 piaware[1318917]: FlightAware server certificate validated Sep 14 15:36:12 rpi2 piaware[1318917]: encrypted session established with FlightAware Sep 14 15:36:13 rpi2 piaware[1318917]: adept reported location: -… Sep 14 15:36:13 rpi2 piaware[1318917]: logged in to FlightAware as user … Sep 14 15:36:13 rpi2 piaware[1318917]: my feeder ID is … Sep 14 15:36:13 rpi2 piaware[1318917]: site statistics URL: [voyteke ADS-B Feeder Statistics - FlightAware](https://flightaware.com/adsb/stats/user/voyteke#stats-199675) Sep 14 15:36:13 rpi2 piaware[1318917]: ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good Sep 14 15:36:13 rpi2 piaware[1318917]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout … Sep 14 15:36:13 rpi2 piaware[1318917]: Started faup1090 (pid 1318940) to connect to dump1090-fa Sep 14 15:36:13 rpi2 piaware[1318917]: UAT support disabled by local configuration setting: uat-receiver-type Sep 14 15:36:13 rpi2 piaware[1318917]: multilateration data requested Sep 14 15:36:13 rpi2 piaware[1318917]: 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 206.253.80.201:5406:2932494521 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): fa-mlat-client 0.2.13 starting up Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Using UDP transport to 206.253.80.201 port 5406 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Listening for Beast-format results connection on port 30105 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Listening for Extended Basestation-format results connection on port 30106 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Route MTU changed to 1500 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Input connected to localhost:30005 Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Input format changed to BEAST, 12MHz clock Sep 14 15:36:14 rpi2 piaware[1318917]: piaware received a message from dump1090-fa! Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Beast-format results connection with ::1:30104: connection established Sep 14 15:36:14 rpi2 piaware[1318917]: piaware has successfully sent several msgs to FlightAware! Sep 14 15:36:45 rpi2 piaware[1318917]: 233 msgs recv’d from dump1090-fa; 233 msgs sent to FlightAware when it failed Sep 10 14:28:18 rpi2 piaware[3070594]: mlat-client(3070619): Server status: synchronized with 209 nearby receivers Sep 10 14:43:19 rpi2 piaware[3070594]: mlat-client(3070619): Server status: not synchronized with any nearby receivers ---
**Author:** ![voyteke](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/voyteke/32/114354_2.png) [@voyteke](https://discussions.flightaware.com/u/voyteke)\ **Post date:** [September 15, 2024, 1:22am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/2 "2024-09-15T01:22:32Z")
seems it just started working again: Sep 15 10:48:54 rpi2 piaware[1363265]: mlat-client(1363358): Server status: not synchronized with any nearby receivers Sep 15 11:18:55 rpi2 piaware[1363265]: mlat-client(1363358): Server status: synchronized with 190 nearby receivers looking in log, I can see this: Sep 15 10:59:01 rpi2 piaware[1363265]: 79770 msgs recv’d from dump1090-fa (548 in last 5m); 79770 msgs sent to FlightAware Sep 15 11:00:51 rpi2 piaware[1363265]: mlat-client(1363358): Beast-format results connection with ::1:30104: connection lost Sep 15 11:00:51 rpi2 piaware[1363265]: mlat-client(1363358): Lost connection to localhost:30005 Sep 15 11:00:51 rpi2 piaware[1363265]: mlat-client(1363358): Reconnecting in 30.0 seconds Sep 15 11:00:51 rpi2 piaware[1363265]: lost connection to dump1090-fa via faup1090 Sep 15 11:00:51 rpi2 piaware[1363265]: faup1090 exited normally Sep 15 11:00:51 rpi2 piaware[1363265]: reconnecting to dump1090-fa Sep 15 11:00:52 rpi2 piaware[1363265]: no ADS-B data program seen listening on port 30005 for 1 seconds, next check in 60s Sep 15 11:01:21 rpi2 piaware[1363265]: mlat-client(1363358): Connection to localhost:30005 lost: [Errno 111] Connection refused Sep 15 11:01:21 rpi2 piaware[1363265]: mlat-client(1363358): Reconnecting in 0.5 seconds Sep 15 11:01:21 rpi2 piaware[1363265]: mlat-client(1363358): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 15 11:01:22 rpi2 piaware[1363265]: mlat-client(1363358): Connection to localhost:30005 lost: [Errno 111] Connection refused Sep 15 11:01:22 rpi2 piaware[1363265]: mlat-client(1363358): Reconnecting in 30.0 seconds Sep 15 11:01:52 rpi2 piaware[1363265]: mlat-client(1363358): Beast-format results connection with ::1:30104: connection established Sep 15 11:01:52 rpi2 piaware[1363265]: ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good Sep 15 11:01:52 rpi2 piaware[1363265]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout … Sep 15 11:01:52 rpi2 piaware[1363265]: Started faup1090 (pid 1667474) to connect to dump1090-fa Sep 15 11:01:52 rpi2 piaware[1363265]: mlat-client(1363358): Input connected to localhost:30005 Sep 15 11:01:52 rpi2 piaware[1363265]: mlat-client(1363358): Input format changed to BEAST, 12MHz clock Sep 15 11:02:43 rpi2 piaware[1363265]: mlat-client(1363358): Lost connection to localhost:30005 Sep 15 11:02:43 rpi2 piaware[1363265]: mlat-client(1363358): Reconnecting in 30.0 seconds Sep 15 11:02:43 rpi2 piaware[1363265]: mlat-client(1363358): Beast-format results connection with ::1:30104: connection lost Sep 15 11:02:43 rpi2 piaware[1363265]: lost connection to dump1090-fa via faup1090 Sep 15 11:02:43 rpi2 piaware[1363265]: faup1090 exited normally Sep 15 11:02:43 rpi2 piaware[1363265]: reconnecting to dump1090-fa Sep 15 11:02:44 rpi2 piaware[1363265]: no ADS-B data program seen listening on port 30005 for 1 seconds, next check in 60s Sep 15 11:03:13 rpi2 piaware[1363265]: mlat-client(1363358): Connection to localhost:30005 lost: [Errno 111] Connection refused Sep 15 11:03:13 rpi2 piaware[1363265]: mlat-client(1363358): Reconnecting in 0.5 seconds Sep 15 11:03:13 rpi2 piaware[1363265]: mlat-client(1363358): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 15 11:03:14 rpi2 piaware[1363265]: mlat-client(1363358): Input connected to localhost:30005 Sep 15 11:03:14 rpi2 piaware[1363265]: mlat-client(1363358): Input format changed to BEAST, 12MHz clock Sep 15 11:03:43 rpi2 piaware[1363265]: mlat-client(1363358): Beast-format results connection with ::1:30104: connection established Sep 15 11:03:44 rpi2 piaware[1363265]: ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good Sep 15 11:03:44 rpi2 piaware[1363265]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout … Sep 15 11:03:44 rpi2 piaware[1363265]: Started faup1090 (pid 1667950) to connect to dump1090-fa Sep 15 11:03:55 rpi2 piaware[1363265]: mlat-client(1363358): Receiver status: connected Sep 15 11:03:55 rpi2 piaware[1363265]: mlat-client(1363358): Server status: clock unstable Sep 15 11:03:55 rpi2 piaware[1363265]: mlat-client(1363358): Receiver: 91.4 msg/s received 27.3 msg/s processed (30%) Sep 15 11:03:55 rpi2 piaware[1363265]: mlat-client(1363358): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server Sep 15 11:03:55 rpi2 piaware[1363265]: mlat-client(1363358): Aircraft: 1 of 3 Mode S, 12 of 12 ADS-B used Sep 15 11:04:01 rpi2 piaware[1363265]: 80158 msgs recv’d from dump1090-fa (388 in last 5m); 80158 msgs sent to FlightAware Sep 15 11:09:01 rpi2 piaware[1363265]: 80936 msgs recv’d from dump1090-fa (778 in last 5m); 80936 msgs sent to FlightAware Sep 15 11:14:01 rpi2 piaware[1363265]: 81725 msgs recv’d from dump1090-fa (789 in last 5m); 81725 msgs sent to FlightAware Sep 15 11:18:55 rpi2 piaware[1363265]: mlat-client(1363358): Receiver status: connected Sep 15 11:18:55 rpi2 piaware[1363265]: mlat-client(1363358): Server status: synchronized with 190 nearby receivers ---
**Author:** ![chemitox](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/chemitox/32/124210_2.png) [@chemitox](https://discussions.flightaware.com/u/chemitox)\ **Post date:** [September 28, 2024, 8:38pm UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/3 "2024-09-28T20:38:14Z")
Hi. What version of Raspberry Pi OS do you have? I had the identical issue on Raspbian 10. What helped was to install the version 12 image (bookworm). ---
**Author:** ![voyteke](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/voyteke/32/114354_2.png) [@voyteke](https://discussions.flightaware.com/u/voyteke)\ **Post date:** [September 29, 2024, 12:02am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/4 "2024-09-29T00:02:26Z")
running bullseye since my last post, it seems ? it’s running normal? if I wanted to upgrade OS, what’s best way: can I upgrade non-destructively in place on SD card? if I install on new SD card, what’s best way to migrate Flightaware+graphs1090 et al ? (meanwhile, reading about u/g OS, gather the ‘better way’ might be new SD card…? if I set new SD/ new OS, what’s best way to migrate Flightware et al ?) ![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/5/1/510cfa1c3b2ac35b1c5dc4da38372c9eed2e7229.png) ![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/e/2/e25829175c0dd100a89aedcdb3d71399f057f8ca.png) though, not sure if that’s the way to assess ? it says this in recent log $ grep “not synchronized” /var/log/piaware.log | wc 22 308 2662 $ grep “synchronized” /var/log/piaware.log | wc 40 542 4766 $ grep “synchronized” /var/log/piaware.log.1 | wc 663 8734 77988 $ grep “not synchronized” /var/log/piaware.log.1 | wc 115 1610 13915 $ cat /etc/os-release PRETTY\_NAME=“Debian GNU/Linux 11 (bullseye)” NAME=“Debian GNU/Linux” VERSION\_ID=“11” VERSION=“11 (bullseye)” VERSION\_CODENAME=bullseye ID=debian ---
**Author:** ![1pdy](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/1pdy/32/124467_2.png) [@1pdy](https://discussions.flightaware.com/u/1pdy)\ **Post date:** [October 2, 2024, 5:51am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/5 "2024-10-02T05:51:24Z")
I believe you can do it by following this instruction. But please image the current sd card in case something goes wrong. > **[The Easiest Way to Upgrade Raspberry Pi OS from Bullseye to Bookworm](https://dev.blues.io/blog/easiest-upgrade-raspberry-pi-bullseye-bookworm/)** > > Learn how to perform an in-place upgrade from Raspberry Pi Bullseye to Bookworm. ---
**Author:** ![voyteke](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/voyteke/32/114354_2.png) [@voyteke](https://discussions.flightaware.com/u/voyteke)\ **Post date:** [October 5, 2024, 6:50am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/6 "2024-10-05T06:50:38Z")
thanks. I was kind of thinking of do full install, but, yes, I guess I’ll image/make duplicate SD card, then, I’ll follow path 2, and, hopefully upgrade to bookworm the way, thanks for the link and advice … didn’t quite succeed. Luckily I followed your ‘please image’ part! I imaged existing SD to new SD, booted with new SD, working fine, then, followed the recipe, after the last reboot I could ping but not ssh the rpi so, rebooted from original card, brought the new card into another rpi, changed IP address, booted… hmm, ssh now works, not sure whay didn’t… BUT: (this is on backup unit WITHOUT radio) $ systemctl status dump1090-fa ● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization) Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sun 2024-10-06 00:13:25 AEST; 7s ago Docs: [PiAware - ADS-B and MLAT Receiver - FlightAware](https://flightaware.com/adsb/piaware/) Process: 17460 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, statu\> Main PID: 17460 (code=exited, status=1/FAILURE) CPU: 21ms $ systemctl status graphs1090 ● graphs1090.service - graphs1090 graph generation Loaded: loaded (/lib/systemd/system/graphs1090.service; enabled; preset: enabled) Active: active (running) since Sat 2024-10-05 23:41:50 AEST; 32min ago Main PID: 961 (service-graphs1) Tasks: 3 (limit: 8731) CPU: 1min 2.257s CGroup: /system.slice/graphs1090.service ├─ 961 /bin/bash /usr/share/graphs1090/service-graphs1090.sh ├─ 8667 /bin/bash /usr/share/graphs1090/service-graphs1090.sh └─17529 /bin/bash /usr/share/graphs1090/service-graphs1090.sh Oct 05 23:41:50 rpi2 systemd[1]: Started graphs1090.service - graphs1090 graph generation. Oct 05 23:41:50 rpi2 graphs1090[963]: 961 (process ID) old priority 19, new priority 19 Oct 05 23:41:53 rpi2 graphs1090[961]: Generating all graphs Oct 06 00:00:09 rpi2 graphs1090[961]: Done with initial graph generation Oct 06 00:07:52 rpi2 graphs1090[8667]: running scatter.sh $ systemctl status piaware Unit piaware.service could not be found. sudo apt install piaware Reading package lists… Done Building dependency tree… Done Reading state information… Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: piaware : Depends: libboost-regex1.74.0-icu67 but it is not installable Depends: libmpdec3 but it is not installable E: Unable to correct problems, you have held broken packages. ---
**Author:** ![voyteke](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/voyteke/32/114354_2.png) [@voyteke](https://discussions.flightaware.com/u/voyteke)\ **Post date:** [October 7, 2024, 1:18am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/7 "2024-10-07T01:18:32Z")
I ended up setting bookworm anew on new SD card, then, installed piaware et al as new, copied over my rrd files from old SD card, after a few minor hiccups (it’s probably better to read docs before starting, rather than not…) it seemed to be working on ‘test’ rpi (with no RTL dongle), so, gave it another IP address, shut down existing, swapped SD cards, etc, etc, and, eventually got it working as expected, on bookworm still need to figure out how to make fail2ban work on bookworm, but, FA, FR24 all working OK thanks again for all the pointers! ---
**Author:** ![voyteke](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/voyteke/32/114354_2.png) [@voyteke](https://discussions.flightaware.com/u/voyteke)\ **Post date:** [November 30, 2024, 8:28am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/9 "2024-11-30T08:28:25Z")
thanks. I think it seems OK since I’ve upgraded OS, haven’t spotted any real issues ? 880 failed in 5200 messages ? does it look OK? ```auto v@rpi2:/var/log $ grep 'not synchronized' /home/v/piaware.log | wc 880 12320 103677 v@rpi2:/var/log $ grep 'synchronized' /home/v/piaware.log | wc 5235 68935 598652 ``` ```auto Oct 06 18:50:03 raspberrypi systemd[1]: Started piaware.service - FlightAware ADS-B uploader. Oct 06 18:50:04 raspberrypi piaware[5951]: creating pidfile /run/piaware/piaware.pid Oct 06 18:50:04 raspberrypi piaware[5951]: **************************************************** Oct 06 18:50:04 raspberrypi piaware[5951]: piaware version 9.0.1 is running, process ID 5951 ``` ![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/c/b/cb68a8163fdc175ced67aec69d7878b82a77ca02.png) ![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/b/a/ba5e72bec3f9ea3d4750d140b4a1f8cc2ff63a06.png) ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/system/32/38558_2.png) [@system](https://discussions.flightaware.com/u/system)\ **Post date:** [November 30, 2025, 8:28am UTC](https://discussions.flightaware.com/t/mlat-stopped/94642/10 "2025-11-30T08:28:27Z")
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.