MLAT connection errors - could use some advice

I'm using a Flight Feeder Orange from FlightAware as my main tracker.

I'm running a separate Raspi 0W with FR24 and ADSBx feeders connected on the BEAST port on the FA Orange feeder.

I'm seeing the following in the logs for adsbx mlat feed:

Code:

Dec 15 14:32:31 pizerow adsbexchange-mlat[5708]: mlat-client 0.4.2 starting up
Dec 15 14:32:31 pizerow adsbexchange-mlat[5708]: Listening for Basestation-format results connection on port 31003
Dec 15 14:32:31 pizerow adsbexchange-mlat[5708]: Listening for Beast-format results connection on port 30157
Dec 15 14:32:31 pizerow adsbexchange-mlat[5708]: Connected to multilateration server at feed2.adsbexchange.com:64590, handshaking
Dec 15 14:32:31 pizerow adsbexchange-mlat[5708]: Lost connection to feed2.adsbexchange.com:64590
Dec 15 14:32:31 pizerow adsbexchange-mlat[5708]: Reconnecting in 10.4 seconds
Dec 15 14:32:32 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:32:32 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30154: connection established
Dec 15 14:32:42 pizerow adsbexchange-mlat[5708]: Connected to multilateration server at feed1.adsbexchange.com:31090, handshaking
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]: Server says:
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]:
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]:         The multilateration server source code is available under
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]:         the terms of the Affero GPL (v3 or later). You may obtain
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]:         a copy of this server's source code at the following
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]:         location: https://github.com/adsbexchange/mlat-server
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]:
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]: Handshake complete: Compression zlib2, UDP transport disabled, Split sync disabled
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]: Input connected to 10.10.1.157:30005
Dec 15 14:32:47 pizerow adsbexchange-mlat[5708]: Input format changed to BEAST, 12MHz clock
Dec 15 14:33:02 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Dec 15 14:33:32 pizerow adsbexchange-mlat[5708]: Receiver: connected    10.9 msg/s received        5.6 msg/s processed (51%)
Dec 15 14:33:32 pizerow adsbexchange-mlat[5708]: Server:   ready         0.0 kB/s from server      0.0 kB/s to server
Dec 15 14:33:32 pizerow adsbexchange-mlat[5708]: Results:  0.0 positions/minute
Dec 15 14:33:32 pizerow adsbexchange-mlat[5708]: Aircraft: 1 of 3 Mode S, 4 of 4 ADS-B used
Dec 15 14:33:32 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:33:36 pizerow adsbexchange-mlat[5708]: peer_count:  23 outlier_percent: 0.0 bad_sync_timeout:   0
Dec 15 14:34:03 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Dec 15 14:34:33 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:35:04 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Dec 15 14:35:34 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:36:04 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Dec 15 14:36:35 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:37:05 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Dec 15 14:37:35 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:38:05 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Dec 15 14:38:35 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:39:06 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Dec 15 14:39:36 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:40:06 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Dec 15 14:40:36 pizerow adsbexchange-mlat[5708]: Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Dec 15 14:41:07 pizerow adsbexchange-mlat[5708]: Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused

Here's the config from /etc/default/adsbexchange:

Code:

INPUT="10.10.1.157:30005"
REDUCE_INTERVAL="0.5"

# feed name for checking MLAT sync (adsbx.org/sync)
# also displayed on the MLAT map: map.adsbexchange.com/mlat-map
USER="redacted"

LATITUDE="redacted"
LONGITUDE="redacted"

ALTITUDE="4536ft"

# this is the source for 978 data, use port 30978 from dump978 --raw-port
# if you're not receiving 978, don't worry about it, not doing any harm!
UAT_INPUT="10.10.1.157:30978"

RESULTS="--results beast,connect,localhost:30104"
RESULTS2="--results basestation,listen,31003"
RESULTS3="--results beast,listen,30157"
RESULTS4="--results beast,connect,localhost:30154"
# add --privacy between the quotes below to disable having the feed name shown on the mlat map
# (position is never shown accurately no matter the settings)
PRIVACY=""
INPUT_TYPE="dump1090"

MLATSERVER="feed.adsbexchange.com:31090"
TARGET="--net-connector feed1.adsbexchange.com,30004,beast_reduce_out,feed2.adsbexchange.com,64004"
NET_OPTIONS="--net-heartbeat 60 --net-ro-size 1280 --net-ro-interval 0.2 --net-ro-port 0 --net-sbs-port 0 --net-bi-port 30154 --net-bo-port 0 --net-ri-port 0 --write-json-every 1"
JSON_OPTIONS="--max-range 450 --json-location-accuracy 2 --range-outline-hours 24"

Oddly, it seems like MLAT is still showing up in my feed:
https://prnt.sc/e1D4sepXBzv6

So I'm not sure what to make of this, it seems there's a connection error happening, but mlat is still somehow working?

 

What results do you get from https://adsbexchange.com/myip/ ?

 

(Attached)

Thanks for the quick reply.

The mlat connection says it’s good, do you know why the errors are in the log?

 

I do not. Putting your feeder id into https://map.adsbexchange.com/mlat-map/ does not return a site either. This will require the attention of someone more knowledgeable. When I had the "connection refused" error, it was because my station was mobile. I assume you have run the setup scripts with your correct location... If so, gotta wait for the real brains around here. That's not me. Not by a long shot.

*edit* Actually, that map needs something besides feeder id, I think.

 

I can see it under 'cartpauj' - https://map.adsbexchange.com/sync/feeder.html?1B&cartpauj

 

Try reading this post, I think it matches your issue pretty close. If you do as he did, commenting out the correct line, your problem should go away.

 

OK, after reading through some other posts, and given the information you provided, I think that mlat-client is trying to send MLAT results to dump1090 on localhost:30104 so that mlat results(I think only the ones you participated in) show up on your dump1090 map. However, regardless of your logs, it looks like your setup IS sending MLAT data to adsbexchange server(s) and is doing what it is supposed to do. If you are not missing out on anything you want on your local map, my suggestion would be to ignore the errors in the log unless and until one of the admins weighs in and says otherwise.

 

Thanks for the additional information. Do you think RESULTS4 should also be commented out?

 

Given that I have not researched that particular port and have no idea about what function it facilitates, and the fact that your log above doesn't indicate any errors in what you included, I am going to say no, at this time. I keep hoping Alex or James will look at this thread and tell me to shut up and then tell you what you REALLY should be doing, but no luck so far. Maybe they are giving me enough rope to hang myself. Pffft. Like I need help with THAT. Maybe they are like my dentist... no work until January 9th.