[OUTDATED] Repository https://abcd567a.github.io/ppa/piaware error 404 - Cannot update

Either (1) something other than dump1090-fa is using the dongle, OR (2) some files have gone corrupt.

In first case most likely candidate which may use dongle are FR24 or RB24 and dump978-fa. Test again with all these also stopped, and post the results

sudo systemctl stop piaware dump1090-fa fr24feed rbfeeder dump978-fa dump978-rb   

rtl_test -t    

 

Thanks. 978 isnt installed but the others seemed to stop.

pi@raspberrypi:~ $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2832U, SN: 00001000

Using device 0: Generic RTL2832U

Kernel driver is active, or device is claimed by second instance of librtlsdr.
In the first case, please either detach or blacklist the kernel module
(dvb_usb_rtl28xxu), or enable automatic detaching at compile time.

usb_claim_interface error -6
Failed to open rtlsdr device #0.

 

Seems corrupted install of dump1090-fa and/or it’s dependencies. Try this:

sudo apt purge dump1090-fa   

sudo apt autoremove   

sudo apt install --reinstall dump1090-fa   

sudo reboot   

 

After reboot, check status of dump1090-fa piaware

sudo systemctl status dump1090-fa   

sudo systemctl status piaware   

 

All went well until:

pi@raspberrypi:~ $ sudo apt install -reinstall dump1090-fa
E: Command line option ‘r’ [from -reinstall] is not understood in combination with the other options.
pi@raspberrypi:~ $

It doesnt seem to recognise the command. What should I do?

Sorry, while typing the command, I missed one - before reinstall. There should be two (-- ) but I typed only one ( - ). The correct command is below:

sudo apt install --reinstall dump1090-fa   

I will correct this typo in my above post so that anyone else using it does not end up in failed command.

 

Thanks. I ran the command and rebooted. then tried the sudo systemctl status dump1090-fa but the terminal window hung. What should I do?

pi@raspberrypi:~ $ sudo systemctl status dump1090-fa

  • dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
    Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor p>
    Active: activating (auto-restart) (Result: exit-code) since Tue 2022-01-11>
    Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
    Process: 2227 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-js>
    Main PID: 2227 (code=exited, status=1/FAILURE)
    CPU: 109ms
    lines 1-7/7 (END)

Ran the last command in a separate terminal…

pi@raspberrypi:~ $ sudo systemctl status piaware

  • piaware.service - FlightAware ADS-B uploader
    Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor prese>
    Active: active (running) since Tue 2022-01-11 00:15:14 WET; 16min ago
    Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
    Main PID: 801 (piaware)
    Tasks: 2 (limit: 4915)
    CPU: 6.395s
    CGroup: /system.slice/piaware.service
    `-801 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -stat>

Jan 11 00:30:59 raspberrypi sudo[2916]: pam_unix(sudo:session): session closed >
Jan 11 00:30:59 raspberrypi piaware[801]: no ADS-B data program is serving on p>
Jan 11 00:31:40 raspberrypi sudo[2971]: piaware : PWD=/ ; USER=root ; COMMAND=>
Jan 11 00:31:40 raspberrypi sudo[2971]: pam_unix(sudo:session): session opened >
Jan 11 00:31:40 raspberrypi sudo[2971]: pam_unix(sudo:session): session closed >
Jan 11 00:31:40 raspberrypi piaware[801]: no ADS-B data program seen listening >
Jan 11 00:31:59 raspberrypi sudo[2979]: piaware : PWD=/ ; USER=root ; COMMAND=>
Jan 11 00:31:59 raspberrypi sudo[2979]: pam_unix(sudo:session): session opened >
Jan 11 00:31:59 raspberrypi sudo[2979]: pam_unix(sudo:session): session closed >
Jan 11 00:31:59 raspberrypi piaware[801]: no ADS-B data program is serving on p>
lines 1-20/20 (END)

Issue these commands. What does last command show?

sudo systemctl stop dump1090-fa   

sudo rmmod dvb_usb_rtl28xxu   

sudo systemctl restart dump1090-fa    

sudo systemctl status dump1090-fa   

it had an error in the second command:

pi@raspberrypi:~ $ sudo systemctl stop dump1090-fa
pi@raspberrypi:~ $ sudo rmmod dvb_usb_rtl28xxu
rmmod: ERROR: Module dvb_usb_rtl28xxu is in use
pi@raspberrypi:~ $ sudo systemctl restart dump1090-fa
pi@raspberrypi:~ $ sudo systemctl status dump1090-fa

  • dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
    Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor p>
    Active: activating (auto-restart) (Result: exit-code) since Tue 2022-01-11>
    Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
    Process: 5737 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-js>
    Main PID: 5737 (code=exited, status=1/FAILURE)
    CPU: 70ms
    lines 1-7/7 (END)

Try following command:
It is very long command. Scroll right to see and copy it in full

sudo echo 'blacklist dvb_usb_rtl28xxu' | sudo tee --append /etc/modprobe.d/blacklist-dvb_usb_rtl28xxu.conf   

Next issue these commands:

sudo reboot   

sudo systemctl status dump1090-fa   

Not trying to interfere, but it seems more likely something is still using the SDR.

pgrep -af dump

Check what (and let’s hope you haven’t installed something like acarsdec or some other decoder that would be using the SDR).

1 Like

pi@raspberrypi:~ $ sudo echo ‘blacklist dvb_usb_rtl28xxu’ | sudo tee --append /etc/modprobe.d/blacklist-dvb_usb_rtl28xxu.conf
blacklist dvb_usb_rtl28xxu

What was the command for?

Rebooted and then…

pi@raspberrypi:~ $ sudo systemctl status dump1090-fa

  • dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
    Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor p>
    Active: active (running) since Tue 2022-01-11 09:17:06 WET; 1h 10min ago
    Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
    Main PID: 586 (dump1090-fa)
    Tasks: 3 (limit: 4915)
    CPU: 6min 12.447s
    CGroup: /system.slice/dump1090-fa.service
    `-586 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --gain 60 >

Jan 11 09:59:56 raspberrypi dump1090-fa[586]: adaptive: changing gain from 42.1>
Jan 11 09:59:56 raspberrypi dump1090-fa[586]: rtlsdr: tuner gain set to 40.2 dB>
Jan 11 10:00:06 raspberrypi dump1090-fa[586]: adaptive: available dynamic range>
Jan 11 10:00:06 raspberrypi dump1090-fa[586]: adaptive: changing gain from 40.2>
Jan 11 10:00:06 raspberrypi dump1090-fa[586]: rtlsdr: tuner gain set to 38.6 dB>
Jan 11 10:00:16 raspberrypi dump1090-fa[586]: adaptive: available dynamic range>
Jan 11 10:00:49 raspberrypi dump1090-fa[586]: adaptive: available dynamic range>
Jan 11 10:00:49 raspberrypi dump1090-fa[586]: adaptive: changing gain from 38.6>
Jan 11 10:00:49 raspberrypi dump1090-fa[586]: rtlsdr: tuner gain set to 37.2 dB>
Jan 11 10:00:59 raspberrypi dump1090-fa[586]: adaptive: available dynamic range>
lines 1-20/20 (END)

  • dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customizat>
    Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; >
    Active: active (running) since Tue 2022-01-11 09:17:06 WET; 1h 10m>
    Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
    Main PID: 586 (dump1090-fa)
    Tasks: 3 (limit: 4915)
    CPU: 6min 12.447s
    CGroup: /system.slice/dump1090-fa.service
    `-586 /usr/bin/dump1090-fa --quiet --device-type rtlsdr →

Jan 11 09:59:56 raspberrypi dump1090-fa[586]: adaptive: changing gain f>
Jan 11 09:59:56 raspberrypi dump1090-fa[586]: rtlsdr: tuner gain set to>
Jan 11 10:00:06 raspberrypi dump1090-fa[586]: adaptive: available dynam>
Jan 11 10:00:06 raspberrypi dump1090-fa[586]: adaptive: changing gain f>
Jan 11 10:00:06 raspberrypi dump1090-fa[586]: rtlsdr: tuner gain set to>
Jan 11 10:00:16 raspberrypi dump1090-fa[586]: adaptive: available dynam>
Jan 11 10:00:49 raspberrypi dump1090-fa[586]: adaptive: available dynam>
Jan 11 10:00:49 raspberrypi dump1090-fa[586]: adaptive: changing gain f>
Jan 11 10:00:49 raspberrypi dump1090-fa[586]: rtlsdr: tuner gain set to>
Jan 11 10:00:59 raspberrypi dump1090-fa[586]: adaptive: available dynam>
~
~
lines 1-20/20 (END)

Thanks! Its entirely possible I installed a competing program… what do these tealeaves tell you?

pi@raspberrypi:~ $ pgrep -af dump
586 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --gain 60 --adaptive-range --fix --lat 28.03045 --lon -16.59137 --max-range 360 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 1 --write-json /run/dump1090-fa
795 /usr/bin/python3.9 /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:32457 --server mlat1.rb24.com:40900 --lat 28.030439 --lon -16.591377 --alt 23 --user EXTRPI015758 --results beast,connect,127.0.0.1:32004
1475 /usr/local/share/adsbexchange/venv/bin/python3 /usr/local/share/adsbexchange/venv/bin/mlat-client --input-type dump1090 --no-udp --input-connect 127.0.0.1:30005 --server feed.adsbexchange.com:31090 --user PMF1-Tenerife --lat 28.03045 --lon -16.59137 --alt 75ft --results beast,connect,localhost:30104 --results basestation,listen,31003 --results beast,listen,30157 --results beast,connect,localhost:30154
1494 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 206.253.84.195:12091:3657585555

Im not sure which of the last two posts of changes fixed FA but its back. As is ADSBx. Thank you both so much for the help! Im a little lost as to what we changed thoug, and am wondering if in reactivating FA we havee taken eg, FR24, PF or PP offline? FR24 I have emailed but it does seem to be working. RB24 also seems to be working. Is there a workaround so they can all live in harmony on the same Pi that I can use as a guiding principle when tinkering with them?

It would be amazing if someone were to build a multifeeder that plugged in to all the sites more or less turnkey, or eg with a small fee for some help getting it up and running… Im guessing most people would want to feed all the sites if it was easy, so it would probably be popular. If a user could pick and choose which features from which sites they want in a front end that would be amazing also but Id be happy with a turnkey multiinstaller.

Following command fixed the problem by blacklisting the kernel module
dvb_usb_rtl28xxu which has grabbed the dvbt dongle, and was not letting dump1090-fa to use it.

 

Following command was for diagnosis:

So … after installing librtlsdr (installed when installing dump1090-fa), you need to reboot or replug the SDR.
Otherwise you won’t be able to use the SDR.

The udev rules are applied on boot or when you replug the SDR.

Rethinking it … that wouldn’t have presented like this.
No clue why you needed the blacklisting or why it helped.

grep -e network_mode /etc/rbfeeder.ini
grep -e receiver /etc/fr24feed.ini

You could check if those two have the configuration set correctly …

 

Well that is what he was asked to do, and I believe he has done it.

 

 

Following results of “rtl_test -t” and “sudo rmmod dvb_usb_rtl28xxu” lead me to use blacklisting

 

 

Does that blacklisting mean that one of the other feeders is now missing access to something it needs? ADSBx, FR24, PF and RB24 all seem to be working. The final feeder I was trying to set up was PP and I used an outdated setup process by accident. I’m guessing its the culprit so will try to work out how to reverse what I did and follow the correct procedure this time. The thread showing the stroy so far is at How-to Feed Plane Plotter Site directly from Raspberry Pi if you want to have a look and see if you think this may have caused the issues we’ve now corrected.

Having made no changes at all since the above modifications that we did together. I’m sad to say that 1090 radio and mlat are both down again on FA, ADSBx and RB24 show no flights either. FR24 and PF are seemingly still online. PP I haven’t started trying to reverse the damage as am awaiting feedback in that other thread as to how to do so.

Dump1090-fa is seemingly still running. pi@raspberrypi:~ $ sudo systemctl status dump1090-fa

  • dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
    Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor p>
    Active: active (running) since Wed 2022-01-12 11:26:59 WET; 28min ago
    Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
    Main PID: 526 (dump1090-fa)
    Tasks: 3 (limit: 4915)
    CPU: 7min 3.244s
    CGroup: /system.slice/dump1090-fa.service
    `-526 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --gain 60 >

Jan 12 11:26:59 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (Flight>
Jan 12 11:27:00 raspberrypi dump1090-fa[526]: Wed Jan 12 11:27:00 2022 WET dum>
Jan 12 11:27:00 raspberrypi dump1090-fa[526]: rtlsdr: using device #0: Generic >
Jan 12 11:27:00 raspberrypi dump1090-fa[526]: Found Rafael Micro R820T tuner
Jan 12 11:27:00 raspberrypi dump1090-fa[526]: rtlsdr: tuner gain set to about 5>
Jan 12 11:27:01 raspberrypi dump1090-fa[526]: adaptive: using 50% duty cycle
Jan 12 11:27:01 raspberrypi dump1090-fa[526]: adaptive: enabled adaptive gain c>
Jan 12 11:27:01 raspberrypi dump1090-fa[526]: adaptive: enabled dynamic range c>
Jan 12 11:27:11 raspberrypi dump1090-fa[526]: adaptive: reached upper gain limi>
lines 1-19/19 (END)