Githubusercontent.com/abcd567a/rpi/master ./ Release' no longer has a Release file

FlightAware ADS-B Flight Tracking
1

oops, on my rpi whilst trying to do routine update:
sudo apt update && sudo apt upgrade

noticed this error below

what did I screw up ?
how can I best correct this ?
everything seems working OK, graphs, fa, etc
:
Ign:5 https://raw.githubusercontent.com/abcd567a/rpi/master ./ InRelease
Get:7 Index of /debian bullseye InRelease [39.0 kB]
Err:8 https://raw.githubusercontent.com/abcd567a/rpi/master ./ Release
404 Not Found [IP: 185.199.111.133 443]
Get:9 Index of /debian bullseye/main armhf Packages [321 kB]
Get:10 Index of /debian bullseye/main arm64 Packages [314 kB]
Reading package lists… Done
E: The repository ‘https://raw.githubusercontent.com/abcd567a/rpi/master ./ Release’ no longer has a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Linux rpi2 6.6.26-v8+ #1754 SMP PREEMPT Thu Apr 11 14:49:11 BST 2024 aarch64 GNU/Linux

3

@voyteke

Please carryout STEPs 1 & 2 below to stop error messages and update and upgrade.

Please see EXPLANATION at the end of this post.

STEP-1:
Issue following two commands to stop error messages
Note: Following command is long. Scroll right to see and copy it in full.

sudo rm /etc/apt/sources.list.d/abcd567a.list 

sudo apt update

STEP-2:
Issue following commands to update / upgrade piaware & dump1090-fa from Flightaware repository:

Note: First two command below are long. Scroll right to see and copy these in full.

wget https://www.flightaware.com/adsb/piaware/files/packages/pool/piaware/f/flightaware-apt-repository/flightaware-apt-repository_1.2_all.deb  

sudo dpkg -i flightaware-apt-repository_1.2_all.deb  

sudo apt update  

sudo apt upgrade

 

EXPLANATION:
You have installed 64-bit rpi packages from my repository at github as at that time these were not available from Flightaware.

Subbsequently Flightaware has released 64-bit packages. I then deleted my packages from github to prevent duplication. This deletion gives error messages you saw.

Solution to stop error messages is to delete my repository from your rpi’s apt sources list (STEP-1 above).

 

​​

3 Likes
4

thanks for explanations!
thanks for detailed correction steps!
thanks for your help, and, thanks for your nifty round-robin graphs1090!
it’s been running without any issues for around 1 year

hmm, just noticed big jump in CPU usage since around May ? any thoughts ?

Screenshot 2024-08-29 071402
Screenshot 2024-08-29 0714021052×637 128 KB

Screenshot 2024-08-29 071855
Screenshot 2024-08-29 071855979×488 44.2 KB

5

You are welcome.
Glad to know your problem is solved

 

The graphs1090 are not by me. These are by @wiedehopf

 

No idea why.
May be @wiedehopf or @jprochazka or someone else can shed some light.

6

I have to admit I am not fully up to speed with Graphs1090 and I am guessing there is a lot more to it than the graphs which are for the time being still a part of my portal. You might want to visit wiedehopf GitHub repository. He has some documentation there as well as an issue tracker you might want to check out.

wiedehopf/graphs1090: Graphs for readsb / dump1090-fa / dump1090 (based on dump1090-tools by mutability) (github.com)

7

The issue tracker is not appropriate to ask about data you see in graphs1090 …

@voyteke 134 days uptime, some system thing consuming CPU …

Stop fr24 service, see if it removes the CPU.
Stop the piaware service, see if it removes the CPU.
Stop dump1090-fa service, see if it remove the CPU.

give it a reboot … see if that fixes it.

You can also check dmesg … possibly show kernel threads in htop

8

The graphs1090 are not by me. These are by @wiedehopf

oops… I should’ve RTFM…

@wiedehopf, thanks for your nifty rrd graphs, and, the other tools, nice and useful!

@jprochazka, thanks for your suggestions - though, the issue is just a general CPU use, unlikely to be caused by rrd tools, just some general glitch, just interesting it jumped so much - my fault for only realizing it now…

9

thanks for suggestions, I was going to try reboot eventually - though, I generally try to find or identify an issue before rebooting…
I’ll try your suggestions, and, let you know
thanks again for the tips, and, your repositories!

this rpi also runs pi-hole - though it’s seldom used. my other rpi runs pi-hole, and, has no CPU issue:

Screenshot 2024-08-29 161701
Screenshot 2024-08-29 161701975×489 40 KB

I’ve stopped and restarted the mentioned processes, no difference though.

10

as I was stopping/re-starting etc, I’ve notice this ‘setup_faup1090_vars’ message, anything I should edit/fix ?

$ sudo systemctl reload piaware

$ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2024-08-16 06:09:02 AEST; 1 weeks 6 days ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 1586130 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Main PID: 53337 (piaware)
Tasks: 4 (limit: 3930)
CPU: 1h 35min 35.121s
CGroup: /system.slice/piaware.service
├─53337 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─53453 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat -33>
└─54050 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --re>

Aug 29 15:39:55 rpi2 systemd[1]: Reloading FlightAware ADS-B uploader.
Aug 29 15:39:55 rpi2 systemd[1]: Reloaded FlightAware ADS-B uploader.
Aug 29 15:39:55 rpi2 piaware[53337]: Reloading configuration and reconnecting.
Aug 29 15:39:55 rpi2 piaware[53337]: Caught background error: invalid command name “setup_faup1090_vars”
Aug 29 15:39:55 rpi2 piaware[53337]: while executing
Aug 29 15:39:55 rpi2 piaware[53337]: “setup_faup1090_vars”
Aug 29 15:39:55 rpi2 piaware[53337]: (procedure “reload_config” line 9)
Aug 29 15:39:55 rpi2 piaware[53337]: invoked from within
Aug 29 15:39:55 rpi2 piaware[53337]: “reload_config”
Aug 29 15:39:55 rpi2 piaware[53337]: while executing signal trap code for SIGHUP signal

11

OK, I gave in and rebooted rpi, all quiet on CPU front now…:

image
image1094×713 64.1 KB

I might post later under new/more appropriate subject, and, I thnk I need to monitor it more often than I do:

image
image1034×625 122 KB

image
image1042×593 135 KB

before reboot, tried again shutting all these, with no noticeable change
fr24feed / piaware / dump1090-fa / timelapse1090 / tar1090

interestingly, ADS-B CPU utilization had minor hike to correspond with overall CPU drop - similarly, when it went up back around May, ADS-B CPU decreased
anyhow, this unit is now been running for just over 1 year with no issues

thanks again for all your help and suggestions