No more flights showing after installing FR24

Tanukik · May 28, 2025, 5:35pm

Hi,

I’ve been struggeling for a few days now and I think that I need help from experts. I have a RPI5 and using Pi OS.

I initially setup correctly Flightaware and then FR24 and it worked perfectly. I had to format and reinstall Pi OS and then, after installing everything again, it is not working properly.

This time, I installed FR24 and then Flightaware. I usually can see planes up to 150NM, but after both installed, that is now reduced to 40NM. I woke up this morning and now, I can`t see any plans at all. Based on what I read, it could be dump1090 but I am not sure, I am new to this and it’s not easy to understand.

To check the status of dump1090-fa, I used: sudo systemctl status dump1090-fa

and the answer is:

● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
     Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2025-05-28 10:33:11 >
       Docs: https://flightaware.com/adsb/piaware/
    Process: 2033 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/du>
   Main PID: 2033 (code=exited, status=1/FAILURE)
        CPU: 10ms

I can see that there is a failure notice but I don’t understand. I am aware that it could be one problems out of a few…

Can anyone help me make both work? Thanks so much

foxhunter · May 28, 2025, 6:46pm

Please excecute the command
journalctl -xe|grep dump1090
and show us the results

wiedehopf · May 28, 2025, 7:23pm

You have 2 decoders competing for the SDR.
(because of the changed install order)

There is a premade image that allows config via webinterface: https://adsb.im/
In case that’s something you’re interested in.

Or you can reconfigure fr24feed to use “modeS Beast - TCP” and connect it to 127.0.0.1 30005.

abcd567 · May 29, 2025, 2:29am

The problem is caused because you installed fr24feed before installing dump1090-fa. When fr24feed did not find any decoder, it installed dump1090-mutability, which grabbed the dongle. Next you installed dump1090-fa, but it failed as it could not find a free dongle to use.

To solve this problem, follow the steps given below.

STEP-1:
Purge fr24feed and dump1090-mutability (which was installed by fr24feed in background, without you noticing it).

sudo apt purge fr24feed  

sudo apt purge dump1090-mutability

STEP-2
Reboot Pi. Upon reboot, the dump1090-fa will use the dongle which is now available as dump1090-mutability has been purged.

sudo reboot

STEP-3
Check status of dump1090-fa.

sudo systemctl status dump1090-fa

STEP-4:
If dump1090-fa is working OK, re-install fr24feed

sudo apt install fr24feed

The installer will detect that dump1090-fa exists, and wont install dump1090-mutability. ~~It will procedd with signup~~.

EDIT
The installer wont proceed to signup automatically. You have to issue following command to start it.

sudo fr24feed --signup

Provide email address, feeder key etc. The installaer will suggest
Accept default configuration (* yes */no)

Type yes and press Enter key.

STEP-5:
Issue following commands to enable fr24feed so that it starts automatically on reboots.

sudo systemctl enable fr24feed  

sudo systemctl restart fr24feed

Tanukik · May 29, 2025, 3:55am

Hi,

Thanks for your reply. I did purge fr24feed and dump1090-mutability. and then checked the status of dump1090-fa and I still get the same error message. Because of that, I did not continue with step 4. Here is the result:

sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
     Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2025-05-28 20:46:01 >
       Docs: https://flightaware.com/adsb/piaware/
    Process: 1875 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/du>
   Main PID: 1875 (code=exited, status=1/FAILURE)
        CPU: 6ms

Then, I ran: journalctl -xe|grep dump1090 and here is the result:

journalctl -xe|grep dump1090
May 28 20:45:30 pi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A start job for unit dump1090-fa.service has finished successfully
░░ A start job for unit dump1090-fa.service has finished successfully.
May 28 20:45:31 pi dump1090-fa[762]: Wed May 28 20:45:31 2025 PDT  dump1090-fa 10.0.1 starting up.
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr: using device #0: Generic RTL2832U OEM (Nooelec, NESDR SMArt v5, SN 00000001)
May 28 20:45:31 pi dump1090-fa[762]: Detached kernel driver
May 28 20:45:31 pi dump1090-fa[762]: Found Rafael Micro R820T tuner
May 28 20:45:31 pi dump1090-fa[762]: r82xx_write: i2c wr failed=-4 reg=0a len=1
May 28 20:45:31 pi dump1090-fa[762]: r82xx_init: failed=-4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: r82xx_write: i2c wr failed=-4 reg=05 len=1
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr: failed to enable tuner AGC
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: r82xx_write: i2c wr failed=-4 reg=17 len=1
May 28 20:45:31 pi dump1090-fa[762]: r82xx_set_freq: failed=-4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: r82xx_write: i2c wr failed=-4 reg=0a len=1
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: adaptive: using 50% duty cycle
May 28 20:45:31 pi dump1090-fa[762]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
May 28 20:45:31 pi dump1090-fa[762]: adaptive: enabled dynamic range control, target dynamic range 30.0dB
May 28 20:45:31 pi dump1090-fa[762]: Allocating 4 zero-copy buffers
May 28 20:45:31 pi dump1090-fa[762]: Failed to submit transfer 0
May 28 20:45:31 pi dump1090-fa[762]: Please increase your allowed usbfs buffer size with the following command:
May 28 20:45:31 pi dump1090-fa[762]: echo 0 > /sys/module/usbcore/parameters/usbfs_memory_mb
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr: rtlsdr_read_async returned unexpectedly, probably lost the USB device, bailing out
May 28 20:45:31 pi dump1090-fa[762]: Wed May 28 20:45:31 2025 PDT  Waiting for receive thread termination
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: r82xx_write: i2c wr failed=-4 reg=06 len=1
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_demod_read_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: rtlsdr_write_reg failed with -4
May 28 20:45:31 pi dump1090-fa[762]: Reattaching kernel driver failed!
May 28 20:45:31 pi dump1090-fa[762]: Wed May 28 20:45:31 2025 PDT  Abnormal exit.
May 28 20:45:31 pi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit dump1090-fa.service has exited.
May 28 20:45:31 pi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
░░ The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.
May 28 20:46:01 pi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 1.
░░ Automatic restarting of the unit dump1090-fa.service has been scheduled, as the result for
May 28 20:46:01 pi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A stop job for unit dump1090-fa.service has finished
░░ A stop job for unit dump1090-fa.service has finished.
May 28 20:46:01 pi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A start job for unit dump1090-fa.service has finished successfully
░░ A start job for unit dump1090-fa.service has finished successfully.
May 28 20:46:01 pi dump1090-fa[1875]: Wed May 28 20:46:01 2025 PDT  dump1090-fa 10.0.1 starting up.
May 28 20:46:01 pi dump1090-fa[1875]: rtlsdr: no supported devices found.
May 28 20:46:01 pi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit dump1090-fa.service has exited.
May 28 20:46:01 pi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
░░ The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.
May 28 20:46:11 pi piaware[1222]: 0 msgs recv'd from dump1090; 0 msgs sent to FlightAware
May 28 20:46:24 pi sudo[1898]: takayukibru : TTY=pts/0 ; PWD=/home/takayukibru ; USER=root ; COMMAND=/usr/bin/systemctl status dump1090-fa
May 28 20:46:31 pi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 2.
░░ Automatic restarting of the unit dump1090-fa.service has been scheduled, as the result for
May 28 20:46:31 pi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A stop job for unit dump1090-fa.service has finished
░░ A stop job for unit dump1090-fa.service has finished.
May 28 20:46:31 pi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A start job for unit dump1090-fa.service has finished successfully
░░ A start job for unit dump1090-fa.service has finished successfully.
May 28 20:46:31 pi dump1090-fa[1902]: Wed May 28 20:46:31 2025 PDT  dump1090-fa 10.0.1 starting up.
May 28 20:46:31 pi dump1090-fa[1902]: rtlsdr: no supported devices found.
May 28 20:46:31 pi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit dump1090-fa.service has exited.
May 28 20:46:31 pi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
░░ The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.
May 28 20:47:02 pi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 3.
░░ Automatic restarting of the unit dump1090-fa.service has been scheduled, as the result for
May 28 20:47:02 pi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A stop job for unit dump1090-fa.service has finished
░░ A stop job for unit dump1090-fa.service has finished.
May 28 20:47:02 pi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A start job for unit dump1090-fa.service has finished successfully
░░ A start job for unit dump1090-fa.service has finished successfully.
May 28 20:47:02 pi dump1090-fa[1909]: Wed May 28 20:47:02 2025 PDT  dump1090-fa 10.0.1 starting up.
May 28 20:47:02 pi dump1090-fa[1909]: rtlsdr: no supported devices found.
May 28 20:47:02 pi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit dump1090-fa.service has exited.
May 28 20:47:02 pi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
░░ The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.
May 28 20:47:32 pi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 4.
░░ Automatic restarting of the unit dump1090-fa.service has been scheduled, as the result for
May 28 20:47:32 pi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A stop job for unit dump1090-fa.service has finished
░░ A stop job for unit dump1090-fa.service has finished.
May 28 20:47:32 pi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A start job for unit dump1090-fa.service has finished successfully
░░ A start job for unit dump1090-fa.service has finished successfully.
May 28 20:47:32 pi dump1090-fa[1913]: Wed May 28 20:47:32 2025 PDT  dump1090-fa 10.0.1 starting up.
May 28 20:47:32 pi dump1090-fa[1913]: rtlsdr: no supported devices found.
May 28 20:47:32 pi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit dump1090-fa.service has exited.
May 28 20:47:32 pi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
░░ The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.
May 28 20:48:02 pi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 5.
░░ Automatic restarting of the unit dump1090-fa.service has been scheduled, as the result for
May 28 20:48:02 pi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A stop job for unit dump1090-fa.service has finished
░░ A stop job for unit dump1090-fa.service has finished.
May 28 20:48:02 pi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A start job for unit dump1090-fa.service has finished successfully
░░ A start job for unit dump1090-fa.service has finished successfully.
May 28 20:48:02 pi dump1090-fa[1920]: Wed May 28 20:48:02 2025 PDT  dump1090-fa 10.0.1 starting up.
May 28 20:48:02 pi dump1090-fa[1920]: rtlsdr: no supported devices found.
May 28 20:48:02 pi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit dump1090-fa.service has exited.
May 28 20:48:02 pi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
░░ The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.
May 28 20:48:32 pi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 6.
░░ Automatic restarting of the unit dump1090-fa.service has been scheduled, as the result for
May 28 20:48:32 pi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A stop job for unit dump1090-fa.service has finished
░░ A stop job for unit dump1090-fa.service has finished.
May 28 20:48:32 pi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A start job for unit dump1090-fa.service has finished successfully
░░ A start job for unit dump1090-fa.service has finished successfully.
May 28 20:48:32 pi dump1090-fa[1924]: Wed May 28 20:48:32 2025 PDT  dump1090-fa 10.0.1 starting up.
May 28 20:48:32 pi dump1090-fa[1924]: rtlsdr: no supported devices found.
May 28 20:48:32 pi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit dump1090-fa.service has exited.
May 28 20:48:32 pi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
░░ The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.
May 28 20:49:03 pi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 7.
░░ Automatic restarting of the unit dump1090-fa.service has been scheduled, as the result for
May 28 20:49:03 pi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A stop job for unit dump1090-fa.service has finished
░░ A stop job for unit dump1090-fa.service has finished.
May 28 20:49:03 pi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
░░ Subject: A start job for unit dump1090-fa.service has finished successfully
░░ A start job for unit dump1090-fa.service has finished successfully.
May 28 20:49:03 pi dump1090-fa[1932]: Wed May 28 20:49:03 2025 PDT  dump1090-fa 10.0.1 starting up.
May 28 20:49:03 pi dump1090-fa[1932]: rtlsdr: no supported devices found.
May 28 20:49:03 pi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit dump1090-fa.service has exited.
May 28 20:49:03 pi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
░░ The unit dump1090-fa.service has entered the 'failed' state with result 'exit-code'.

Thanks for your help :)

Tanukik · May 29, 2025, 3:55am

Thanks for your help. See my previous message with the log.

abcd567 · May 29, 2025, 4:12am

Problem seems to be either defective dongle, or defective usb cable between dongle & pi, or defective usb port. It may also be due to low dc voltage (cpu gone bad). Let us try to isolate the issue, one at a time.

First check dongle. Issue following commands, and post output of last command only.

sudo apt install rtl-sdr  

rtl_test -t

Tanukik · May 29, 2025, 4:16am

This is the result:

sudo apt install rtl-sdr  

rtl_test -t 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
rtl-sdr is already the newest version (0.6.0-4).
The following packages were automatically installed and are no longer required:
  libjs-excanvas libjs-jquery-ui libjs-jquery-ui-theme-smoothness
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Found 1 device(s):
  0:  Nooelec, NESDR SMArt v5, SN: 00000001

Using device 0: Generic RTL2832U OEM
usb_claim_interface error -6
Failed to open rtlsdr device #0.

I can see that I am now starting to see some planes:

abcd567 · May 29, 2025, 4:22am

Ok, stop dump1090-fa and test again. Post result of command rtl_test -t only

sudo systemctl stop dump1090-fa  

rtl_test -t

Tanukik · May 29, 2025, 4:23am

rtl_test -t
Found 1 device(s):
0: Nooelec, NESDR SMArt v5, SN: 00000001

Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.
Reattached kernel driver

abcd567 · May 29, 2025, 4:28am

Your dongle seems OK
Reboot pi and after reboot check status of dump1090-fa

sudo journalctl -u dump1090-fa -n10

Tanukik · May 29, 2025, 4:37am

Thanks for your help. This is the status:

sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
     Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled)
     Active: active (running) since Wed 2025-05-28 21:35:01 PDT; 2min 0s ago
       Docs: https://flightaware.com/adsb/piaware/
   Main PID: 763 (dump1090-fa)
      Tasks: 3 (limit: 4762)
        CPU: 6.724s
     CGroup: /system.slice/dump1090-fa.service
             └─763 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --gain 60 --adaptive>

May 28 21:35:32 pi dump1090-fa[763]: adaptive: available dynamic range (25.0dB) < require>
May 28 21:35:32 pi dump1090-fa[763]: adaptive: changing gain from 48.0dB (step 27) to 44.>
May 28 21:35:32 pi dump1090-fa[763]: rtlsdr: tuner gain set to 44.5 dB (gain step 26)
May 28 21:35:43 pi dump1090-fa[763]: adaptive: available dynamic range (28.5dB) < require>
May 28 21:35:43 pi dump1090-fa[763]: adaptive: changing gain from 44.5dB (step 26) to 43.>
May 28 21:35:43 pi dump1090-fa[763]: rtlsdr: tuner gain set to 43.9 dB (gain step 25)
May 28 21:35:53 pi dump1090-fa[763]: adaptive: available dynamic range (28.0dB) < require>
May 28 21:35:53 pi dump1090-fa[763]: adaptive: changing gain from 43.9dB (step 25) to 43.>
May 28 21:35:53 pi dump1090-fa[763]: rtlsdr: tuner gain set to 43.4 dB (gain step 24)
May 28 21:36:03 pi dump1090-fa[763]: adaptive: available dynamic range (30.8dB) >= requir>
lines 1-20/20 (END)

abcd567 · May 29, 2025, 4:50am

Great, your dump1090-fa has started working after reboot.

Just the last check to ensure that dump1090-mutability has been purged successfully, please issue following command and post its output

apt-cache policy dump1090-mutability

Tanukik · May 29, 2025, 4:52am

Result:

apt-cache policy dump1090-mutability   
dump1090-mutability:
  Installed: (none)
  Candidate: 1.15~20180310.4a16df3+dfsg-8.1
  Version table:
     1.15~20180310.4a16df3+dfsg-8.1 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages

Now, I need to install FR24 right? I am hoping it won’t mess up anything because it usually does.

abcd567 · May 29, 2025, 4:57am

Great. The dump1090-mutability no more exists on your system.

As dump-1090-fa is running successfully, please install fr24feed as per STEP-4 & STEP-5 in my post above.

Tanukik · May 29, 2025, 5:00am

I am so annoyed. Thanks so much for your support.

Now, when I run step 4, I am getting this and not the regular install:

sudo apt install fr24feed  
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libjs-excanvas libjs-jquery-ui libjs-jquery-ui-theme-smoothness
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  fr24feed
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 0 B/4,997 kB of archives.
After this operation, 14.3 MB of additional disk space will be used.
Selecting previously unselected package fr24feed.
(Reading database ... 133078 files and directories currently installed.)
Preparing to unpack .../fr24feed_1.0.51-0_arm64.deb ...
Unpacking fr24feed (1.0.51-0) ...
Setting up fr24feed (1.0.51-0) ...
useradd: user 'fr24' already exists

abcd567 · May 29, 2025, 5:30am

This is perfectly OK.
Sorry, in STEP-4, I missed to write the signup command after fr24feed install command. Please issue following command and complete signup procedure as per Step-4

sudo fr24feed --signup

Tanukik · May 29, 2025, 5:39am

Thanks so much. I also changed this setting to Beast and I hope that everything will work fine now.

I guess we will see tomorrow if I can see planes further away. It’s now too late and there are not many planes flying.

THANK YOU SO MUCH!!

Tanukik · May 29, 2025, 4:20pm

The problem is still there… Here is the error message I have:

Problem fetching data from dump1090.
AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
The displayed map data will be out of date.

sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
     Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2025-05-29 08:56:53 >
       Docs: https://flightaware.com/adsb/piaware/
    Process: 2817 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/du>
   Main PID: 2817 (code=exited, status=1/FAILURE)
        CPU: 9ms

rtl_test -t
No supported devices found.

sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
     Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2025-05-29 09:19:56 PDT;>
       Docs: https://flightaware.com/adsb/piaware/
    Process: 3099 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump10>
   Main PID: 3099 (code=exited, status=1/FAILURE)
        CPU: 10ms

Unsure what to do…

Thanks

biekerc · May 29, 2025, 4:56pm

I’d try this, might even temp you to feed even more sites.

Topic		Replies	Views
Having trouble with Rpi feeding ADS-B Flight Tracking	6	1469	January 26, 2018
No Dump1090 Local ADS-B Flight Tracking	11	1159	September 2, 2021
PiAware Feed ADS-B Flight Tracking	15	3239	January 25, 2018
FlightAware Feeds; Other Feeds Go Down ADS-B Flight Tracking	45	2157	July 11, 2019
SD Card failed, new card is now a new site and white screen when accessing dump1090-fa ADS-B Flight Tracking	4	455	October 20, 2018

No more flights showing after installing FR24

Related topics