Noticed in the logs after an update that piaware-status was saying:
got ‘couldn’t open socket: connection refused’
dump1090 is NOT producing data on localhost:30005.
Checking dump1090 it is saying:
i@PiAware:~ $ sudo systemctl status dump1090-fa -l
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2024-03-18 11:50:39 CDT; 10s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 959 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1/FAILURE)
Main PID: 959 (code=exited, status=1/FAILURE)
CPU: 102m,
On the Flightware status page it is showing that the “1090 Radio” is showing “not connected to Mode S receiver” and MLAT is showing “Multilateration enabled , but client is not running”
Any assistants will be greatly appreciated.
Update:
Looks like installing dump1090-mutability was the issue as I removed that and it looks to be working now:
dump1090-fa (pid 11198) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.dump1090 is producing data on localhost:30005.