MLAT Server Health Indicator

Would it be possible to have a server health page or indicator on the My ADS-B page that shows when the MLAT servers are up?

I know that I’m fighting high CPU usage and sometimes I see MLAT results drop, but they sometimes correspond to other’s reported outages and I’d like to be able to tell if it’s a local issue or something out of my control.

Thanks and keep up the great work!

Given what appears to be a current outage, I renew this request. :slight_smile:

Hi,

At the risk of hijacking this thread, I wanted to raise what appears to be a related issue that I have seen several times now. Symptom is a loss of all MLAT aircraft, typical log file entries are:


08/01/2015 00:32:32 mlat(7619): Results:  29.9 positions/minute
08/01/2015 00:32:32 mlat(7619): Aircraft: 18 known, 10 requested by server
08/01/2015 00:33:17 170696 msgs recv'd from dump1090-mutabi (234 in last 5m); 170409 msgs sent to FlightAware
08/01/2015 00:38:17 170952 msgs recv'd from dump1090-mutabi (256 in last 5m); 170665 msgs sent to FlightAware
08/01/2015 00:43:17 171194 msgs recv'd from dump1090-mutabi (242 in last 5m); 170907 msgs sent to FlightAware
08/01/2015 00:47:33 mlat(7619): Receiver connection: ready
08/01/2015 00:47:33 mlat(7619): Server connection:   ready
08/01/2015 00:47:33 mlat(7619): Receiver:   60.3 msg/s received      1.1kB/s from receiver
08/01/2015 00:47:33 mlat(7619): Server:      0.1 kB/s from server    0.0kB/s TCP to server   0.5kB/s UDP to server
08/01/2015 00:47:33 mlat(7619): Results:  23.0 positions/minute
08/01/2015 00:47:33 mlat(7619): Aircraft: 17 known, 13 requested by server
08/01/2015 00:48:17 171390 msgs recv'd from dump1090-mutabi (196 in last 5m); 171103 msgs sent to FlightAware
08/01/2015 00:53:17 171607 msgs recv'd from dump1090-mutabi (217 in last 5m); 171320 msgs sent to FlightAware
08/01/2015 00:56:26 multilateration data no longer required, disabling mlat client
08/01/2015 00:56:26 mlat(7619): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
08/01/2015 00:56:26 the system told us that process 7619 exited cleanly
08/01/2015 00:56:26 the system confirmed that process 7619 exited with an exit status of 0
08/01/2015 00:58:17 171864 msgs recv'd from dump1090-mutabi (257 in last 5m); 171577 msgs sent to FlightAware
08/01/2015 01:03:17 172144 msgs recv'd from dump1090-mutabi (280 in last 5m); 171857 msgs sent to FlightAware
08/01/2015 01:08:17 172383 msgs recv'd from dump1090-mutabi (239 in last 5m); 172096 msgs sent to FlightAware
08/01/2015 01:13:17 172651 msgs recv'd from dump1090-mutabi (268 in last 5m); 172364 msgs sent to FlightAware
08/01/2015 01:18:17 172875 msgs recv'd from dump1090-mutabi (224 in last 5m); 172588 msgs sent to FlightAware
08/01/2015 01:23:17 173088 msgs recv'd from dump1090-mutabi (213 in last 5m); 172801 msgs sent to FlightAware
08/01/2015 01:28:17 173267 msgs recv'd from dump1090-mutabi (179 in last 5m); 172980 msgs sent to FlightAware
08/01/2015 01:33:17 173458 msgs recv'd from dump1090-mutabi (191 in last 5m); 173171 msgs sent to FlightAware
08/01/2015 01:38:17 173622 msgs recv'd from dump1090-mutabi (164 in last 5m); 173335 msgs sent to FlightAware
08/01/2015 01:43:17 173762 msgs recv'd from dump1090-mutabi (140 in last 5m); 173475 msgs sent to FlightAware
08/01/2015 01:48:17 173921 msgs recv'd from dump1090-mutabi (159 in last 5m); 173634 msgs sent to FlightAware
08/01/2015 01:53:17 174056 msgs recv'd from dump1090-mutabi (135 in last 5m); 173769 msgs sent to FlightAware
08/01/2015 01:58:17 174207 msgs recv'd from dump1090-mutabi (151 in last 5m); 173920 msgs sent to FlightAware
08/01/2015 02:03:17 174364 msgs recv'd from dump1090-mutabi (157 in last 5m); 174077 msgs sent to FlightAware
(continues until reboot)


After a reboot the MLAT client starts up immediately:


08/01/2015 02:04:55 mlat(1312): fa-mlat-client 0.2.2 starting up
08/01/2015 02:04:55 mlat(1312): Using UDP transport to 70.42.6.194:6117
08/01/2015 02:04:55 mlat(1312): Input connected to localhost:30005
08/01/2015 02:04:56 mlat(1312): Beast-format results connection with localhost:30004: connection established
08/01/2015 02:05:24 23 msgs recv'd from dump1090-mutabi; 23 msgs sent to FlightAware
08/01/2015 02:05:53 server is sending alive messages; we will expect them


And approximately 4 minutes later all of the MLAT aircraft come back…

I am running ubuntu on an Asus EEEBox, total CPU usage in top is 4.2% (95.8% idle) so I am pretty confident this issue isn’t related to local processing power.

Peter

Network issues on the FA side again. It’s flapping, so it’s a bit hit or miss how long it stays up for. I wouldn’t read much into what your system’s doing right now.

(It started at about 00:50 UTC and then it took a few minutes for the frontends to notice they were no longer connected)