Broke something with Mlat

FlightAware ADS-B Flight Tracking
1

Updated to new PIAWARE and then set up Mutabilty to 30104 for Beast. But now Im getting this error, where did I go boom?

[2015-10-09 08:43 PDT] autoUpdate in adept config is enabled, allowing update
[2015-10-09 08:43 PDT] manualUpdate in adept config is enabled, allowing update
[2015-10-09 08:43 PDT] multilateration support enabled (use piaware-config to disable)
[2015-10-09 08:43 PDT] no ADS-B data program seen listening on port 30005 for 4 seconds, next check in 60s
[2015-10-09 08:43 PDT] multilateration support enabled (use piaware-config to disable)
[2015-10-09 08:43 PDT] multilateration data requested, enabling mlat client
[2015-10-09 08:43 PDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2015-10-09 08:44 PDT] 0 msgs recv’d from the ADS-B data program; 0 msgs sent to FlightAware
[2015-10-09 08:44 PDT] no ADS-B data program seen listening on port 30005 for 67 seconds, next check in 60s
[2015-10-09 08:44 PDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2015-10-09 08:45 PDT] no ADS-B data program seen listening on port 30005 for 127 seconds, next check in 60s
[2015-10-09 08:45 PDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet

2

Re-did mutability with 30005 in beast and it still telling me it cant find it

[2015-10-09 08:52 PDT] no ADS-B data program seen listening on port 30005 for 125 seconds, next check in 60s
[2015-10-09 08:52 PDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet

3

This means that dump1090 is not running; check the dump1090 logs (/var/log/dump1090-mutability.log)

4

Does not show why its not running. Ill see if I can find the config file command to run again

5

Fixed user error.

I had deleted mutability and re-installed to make sure it was working right forgot a last step

sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

OOPS.

Still not getting MLAT … but Im sure its something I did … just have to find where :slight_smile:

6

reset PIAWARE status to make sure it was on 30104 (with all the stuff I was trying to do) and its now working.