What do you think the issue is, Pi been running fine for years. I have trred different dongles still the same issue. It says not connecting to Mode S receiver but the Pi is recognising it and so does a PC if I plug it in.
what is the status of the dump1090-fa process?
sudo service dump1090-fa status
It seems that that proces is not running.
Piaware and Flightaware things that are looked at and show if the piaware process is running and if you are connected to FA. When the dump1090-fa isn’t running MLAT will turn red as well as in your case.
Thanks for the reply
pi@piaware:~ $ sudo service dump1090-fa status
● 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 Thu 2025-06-26 16:33:24 BST; 17s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 5624 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1/
Main PID: 5624 (code=exited, status=1/FAILURE)
It is failing, did you try to reboot the Pi?
That usually cleans the error, otherwise we have to dig deeper
why is no one asking for the log right at the start 
sudo journalctl -u dump1090-fa -n30 --no-pager
1 Like
Ah brainfart, couldn’t remember the correct command, thanks
1 Like
Yeah its been rebooted many times, I changed the dongle from the flightaware blue to a chinese version, same issue.
pi@piaware:~ $ sudo journalctl -u dump1090-fa -n30 --no-pager
– Logs begin at Thu 2019-02-14 10:11:59 GMT, end at Thu 2025-06-26 16:59:34 BST. –
Jun 26 16:58:30 piaware systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 12.
Jun 26 16:58:30 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Jun 26 16:58:31 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jun 26 16:58:31 piaware dump1090-fa[970]: Thu Jun 26 16:58:31 2025 BST dump1090-fa 10.0.1~bpo10+1 starting up.
Jun 26 16:58:31 piaware dump1090-fa[970]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)
Jun 26 16:58:31 piaware dump1090-fa[970]: Found Rafael Micro R820T tuner
Jun 26 16:58:31 piaware dump1090-fa[970]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Jun 26 16:58:31 piaware dump1090-fa[970]: Error opening the listening port 30003 (Basestation TCP output): bind: Address already in use
Jun 26 16:58:31 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 16:58:31 piaware systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Jun 26 16:58:52 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Jun 26 16:58:53 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jun 26 16:58:53 piaware dump1090-fa[985]: Thu Jun 26 16:58:53 2025 BST dump1090-fa 10.0.1~bpo10+1 starting up.
Jun 26 16:58:53 piaware dump1090-fa[985]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)
Jun 26 16:58:53 piaware dump1090-fa[985]: Found Rafael Micro R820T tuner
Jun 26 16:58:53 piaware dump1090-fa[985]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Jun 26 16:58:53 piaware dump1090-fa[985]: Error opening the listening port 30003 (Basestation TCP output): bind: Address already in use
Jun 26 16:58:53 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 16:58:53 piaware systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Jun 26 16:59:24 piaware systemd[1]: dump1090-fa.service: Service RestartSec=30s expired, scheduling restart.
Jun 26 16:59:24 piaware systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 13.
Jun 26 16:59:24 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Jun 26 16:59:24 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Jun 26 16:59:24 piaware dump1090-fa[1003]: Thu Jun 26 16:59:24 2025 BST dump1090-fa 10.0.1~bpo10+1 starting up.
Jun 26 16:59:24 piaware dump1090-fa[1003]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)
Jun 26 16:59:24 piaware dump1090-fa[1003]: Found Rafael Micro R820T tuner
Jun 26 16:59:24 piaware dump1090-fa[1003]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Jun 26 16:59:25 piaware dump1090-fa[1003]: Error opening the listening port 30003 (Basestation TCP output): bind: Address already in use
Jun 26 16:59:25 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 16:59:25 piaware systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
Likely misconfiguration of fr24.
For non-technical people who want to feed multiple aggregators i’d recommend giving http://adsb.im/ a try (as a fresh image).
Anyhow if you want to confirm:
sudo netstat -tlpn | grep 30003
1 Like
Its been sat in the loft for years feeding both fr24 and FA, I wonder if something has updated automatically and broke it. Check my site stats. Suddendly stopped a couple of weeks ago.
pi@piaware:~ $ sudo netstat -tlpn | grep 30003
tcp6 0 0 :::30003 :::* LISTEN 486/fr24feed
Take a look at airplanes.live / adsb.lol as well. There are various other sites as well.
Regardless FR24 is best not to be allowed to autoupdate, they have broken stuff before.
(adsb.im runs the various aggregators that their own software in its own container preventing such issues)
But if you just want to fix it that shouldn’t be super complicated either …
If you’re handy with the editor change /etc/fr24feed.ini
probably has some “yes” in there for basestation.
receiver=“beast-tcp”
fr24key=“xxxxxxxxxxxxxx”
host=“127.0.0.1:30005”
bs=“yes”
raw=“yes”
logmode=“0”
windowmode=“0”
logpath=“/var/log/fr24feed”
mpx=“no”
mlat=“yes”
mlat-without-gps=“yes”
all working now thanks
1 Like
Those need to be no.
1 Like