MLAT issue- Beast-format results connection with [Errno 111] Connection refused'

I’m currently feeding Flightaware using dump1090-mutability(v.1.15) and the latest piaware-v6.1 packages. Just upgraded piaware to v6.1 from v3.8.1. Now i see the following,

unrecognized message type ‘faup_adjust_upload_rate’ from server, ignoring…

MLAT is no longer working. Has anyone else faced this issue? Any ideas on what can be done to fix this? Thank You

a) please update from dump1090-mutability to something recent - dump1090-fa or readsb
b) what is the underlying OS & version?
c) how did you install piaware, and how did you upgrade it?
d) please provide the exact log errors you’re seeing, with some context lines from immediately before/after the errors

1 Like

Currently have upgraded to dump1090-fa, and no other dump1090 decoders are present. Running the setup on a piaware raspberry pi image.
PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION=“10 (buster)”

Changing from dump1090-mutability to dump1090-fa resulted in the following,

Beast-format results connection with [Errno 111] Connection refused

How can i go about this?

Did you reboot the Pi ?
I had the same error when setting up a new station this evening and after a reboot and waiting 10 minutes the error was gone.

Sorry, can you explain more clearly what you’re currently running? Did you start from the 6.1 piaware sdcard image, or something else? Your site is currently reporting that you’re running a package-based install, not the sdcard image. What did you start from and what did you install on top of that?

Also, looking at your site at the moment, I don’t currently see any mlat problems.

Started with the piaware 3.8.1 sd card image. Currently have upgraded to the piaware 6.1 package by sending the command from the piaware my-adsb page.

Note that the piaware 3.8.1 sdcard image does not include dump1090-mutability, so I’m not sure where that came from? If you installed it manually onto a piaware sdcard image… well, don’t do that!

Also I still don’t see any problems in your site logs at the moment - are you still having problems? If so please provide the complete errors you see, with context.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.