Multilateration data no longer required, disabling mlat client

FlightAware ADS-B Flight Tracking
21

The Main-router and Sub-router both are identical devices: TP-Link EX511
The Sub-router is connected to Main-router by Wireless.
Desktop is connected to Sub-router by RJ-45 wire.

20250412_075813
20250412_075813593×132 21.5 KB

 

Yes, it is in my apartment. See the photo below

Click on Photo to See Larger Size

20250412
20250412605×807 150 KB

 

22

 

:astonished_face: :astonished_face: :astonished_face:

So many notices in one day!
I hardly get one or two a day, some times none.

 

EDIT: Checked other receivers, only one (RECEIVER-5) is behaving like yours, others are OK

RECEIVER 1 of 5

pi@Armbian-trixie:~$ sudo journalctl -u piaware | grep NOTICE

Apr 11 14:33:07 armb-trixie piaware[4274]: NOTICE from adept server: 35% of multilateration messages (UDP) are not reaching the server - check your network?
pi@Armbian-trixie:~$

 

RECEIVER 2 of 5

pi@DietPi-trixie:~$
pi@DietPi-trixie:~$ sudo journalctl -u piaware | grep NOTICE

pi@DietPi-trixie:~$

RECEIVER 3 of 5

pi@orangepipc:~$ sudo journalctl -u piaware | grep NOTICE

Apr 11 14:33:20 orangepipc piaware[993]: NOTICE from adept server: 39% of multilateration messages (UDP) are not reaching the server - check your network?
pi@orangepipc:~$

 

RECEIVER 4 of 5

abcd@debian-13:~$ sudo journalctl -u piaware | grep NOTICE

Apr 08 17:54:29 debian-13 piaware[712]: NOTICE from adept server: 12% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 09 03:11:10 debian-13 piaware[724]: NOTICE from adept server: 21% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 09 03:15:11 debian-13 piaware[724]: NOTICE from adept server: 21% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 11 14:32:45 debian-13 piaware[712]: NOTICE from adept server: 36% of multilateration messages (UDP) are not reaching the server - check your network?
abcd@debian-13:~$

 

RECEIVER 5 of 5

pi@raspi-4:~ $ sudo journalctl -u piaware -n 10000 | grep NOTICE

Apr 02 17:21:36 raspi-4 piaware[2050]: NOTICE from adept server: 71% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:22:36 raspi-4 piaware[2050]: NOTICE from adept server: 100% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:23:36 raspi-4 piaware[2050]: NOTICE from adept server: 100% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:24:37 raspi-4 piaware[2050]: NOTICE from adept server: 100% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:25:37 raspi-4 piaware[2050]: NOTICE from adept server: 100% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:26:37 raspi-4 piaware[2050]: NOTICE from adept server: 100% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:27:37 raspi-4 piaware[2050]: NOTICE from adept server: 100% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:28:37 raspi-4 piaware[2050]: NOTICE from adept server: 100% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:29:38 raspi-4 piaware[2050]: NOTICE from adept server: 100% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 02 17:33:09 raspi-4 piaware[2012]: NOTICE from adept server: 44% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 03 21:40:18 raspi-4 piaware[2012]: NOTICE from adept server: 11% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 04 14:32:48 raspi-4 piaware[1877]: NOTICE from adept server: 40% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 04 15:33:06 raspi-4 piaware[1877]: NOTICE from adept server: 43% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 05 15:43:23 raspi-4 piaware[2045]: NOTICE from adept server: 11% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 06 01:21:16 raspi-4 piaware[2050]: NOTICE from adept server: 10% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 07 11:05:53 raspi-4 piaware[1965]: NOTICE from adept server: 20% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 08 21:30:24 raspi-4 piaware[2964]: NOTICE from adept server: 18% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 09 03:11:45 raspi-4 piaware[2782]: NOTICE from adept server: 23% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 09 03:14:47 raspi-4 piaware[2782]: NOTICE from adept server: 22% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 09 03:55:05 raspi-4 piaware[2782]: NOTICE from adept server: 13% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 09 04:31:19 raspi-4 piaware[2782]: NOTICE from adept server: 11% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 09 06:44:46 raspi-4 piaware[2782]: NOTICE from adept server: 22% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 09 07:27:59 raspi-4 piaware[2782]: NOTICE from adept server: 17% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 10 15:19:03 raspi-4 piaware[2037]: NOTICE from adept server: 27% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 10 22:37:13 raspi-4 piaware[2037]: NOTICE from adept server: 25% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 11 14:33:04 raspi-4 piaware[2022]: NOTICE from adept server: 37% of multilateration messages (UDP) are not reaching the server - check your network?
Apr 12 07:55:44 raspi-4 piaware[2063]: NOTICE from adept server: 14% of multilateration messages (UDP) are not reaching the server - check your network?
pi@raspi-4:~ $
23

I have this coming occasionally, mostly during night time hours.
It reports only the percentage issue, never had the disabled message in the logs of all 19 recievers.
Sometimes once a week, sometimes multiple times per day.
During night time there’s very limited network traffic inside the network so it can’t be a bandwith issue.

24

My network that has 3 Windows laptops connected to wifi and 9 RPi Bookworm devices on an Ethernet LAN. There are a variety of peripherals that are LAN connecteId as well as wifi connected. All are very active 12 hours per day and mildly active for the other 12 hours. I have not seen such notices. I’ll grep the logs. I’m connected via cable TV. Speed varies between 600mbps and 900mbps depending on congestion. Current speed is 700mbps down and 25mbps up per Ookla speedtest.net.

EDIT - My bookworm devices show a couple of the adept notices per day for 2025 when my logs were last rolled.

25

Update: My MLAT function is still active early this morning while currently tracking 356 aircraft.

26

Update: Tracking 396 aircraft. MLAT function has dropped is red status.
Log:
025-04-14 08:35 EDT] mlat-client(13643): Input connected to localhost:30005
[2025-04-14 08:35 EDT] mlat-client(13643): Using UDP transport to 2620:13d:c004:11::199 port 19095
[2025-04-14 08:35 EDT] mlat-client(13643): Input format changed to BEAST, 12MHz clock
[2025-04-14 08:35 EDT] 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 2620:13d:c004:11::199:19095:388088640
[2025-04-14 08:35 EDT] mlat-client(13643): Listening for Extended Basestation-format results connection on port 30106
[2025-04-14 08:35 EDT] mlat-client(13643): fa-mlat-client 0.2.12 starting up
[2025-04-14 08:35 EDT] mlat-client(13643): Route MTU changed to 1500
[2025-04-14 08:35 EDT] mlat-client(13643): Listening for Beast-format results connection on port 30105
[2025-04-14 08:35 EDT] mlat-client(13643): Beast-format results connection with ::1:30104: connection established
[2025-04-14 08:36 EDT] multilateration data no longer required, disabling mlat client
[2025-04-14 08:36 EDT] mlat-client(13643): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
[2025-04-14 08:36 EDT] fa-mlat-client exited normally
[2025-04-14 08:37 EDT] 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 2620:13d:c004:11::199:19095:388088640
[2025-04-14 08:37 EDT] multilateration data requested
[2025-04-14 08:37 EDT] mlat-client(14162): Using UDP transport to 2620:13d:c004:11::199 port 19095
[2025-04-14 08:37 EDT] mlat-client(14162): Route MTU changed to 1500
[2025-04-14 08:37 EDT] mlat-client(14162): fa-mlat-client 0.2.12 starting up
[2025-04-14 08:37 EDT] mlat-client(14162): Listening for Extended Basestation-format results connection on port 30106
[2025-04-14 08:37 EDT] mlat-client(14162): Input format changed to BEAST, 12MHz clock
[2025-04-14 08:37 EDT] mlat-client(14162): Listening for Beast-format results connection on port 30105
[2025-04-14 08:37 EDT] mlat-client(14162): Input connected to localhost:30005
[2025-04-14 08:37 EDT] mlat-client(14162): Beast-format results connection with ::1:30104: connection established

27

Update:
High noon and tracking 514 aircraft. MLAT can’t deal with it and continues in the red.

28

This should be fixed now (as of around 1500Z)

The adept NOTICE messages are unrelated to OP’s issue where the mlat client would stop entirely.

29

Seems better. Around 11am EDT I now have MLAT traffic showing up in my logs again and the shutdown message is gone replaced by the standard MLAT message every 5 minutes giving stats. Thank you much

Apr 15 11:57:54 piaware2 piaware[4344]: mlat-client(966317): Receiver status: connected
Apr 15 11:57:54 piaware2 piaware[4344]: mlat-client(966317): Server status:   synchronized with 500 nearby receivers
Apr 15 11:57:54 piaware2 piaware[4344]: mlat-client(966317): Receiver: 1963.4 msg/s received      707.1 msg/s processed (36%)
Apr 15 11:57:54 piaware2 piaware[4344]: mlat-client(966317): Server:      0.2 kB/s from server    0.2kB/s TCP to server     4.2kB/s UDP to server
Apr 15 11:57:54 piaware2 piaware[4344]: mlat-client(966317): Results:  74.9 positions/minute
Apr 15 11:57:54 piaware2 piaware[4344]: mlat-client(966317): Aircraft: 23 of 40 Mode S, 174 of 378 ADS-B used

dump1090-localhost-aircraft-2h
dump1090-localhost-aircraft-2h619×324 14.9 KB

1 Like
30

I have noticed a big change here today since midday. MLAT has been staying green during heavy traffic. Currently tracking 361 and in the green. Thanks for your efforts and good results.

1 Like
31

Update: Happy days! Tracking 510 aircraft in prime time this morning and MLAT process is clean and Green! Good fix obj!

3 Likes