PiAware 6 Upgrade Issue

dannco01 · September 2, 2021, 7:26pm

Hi all tried to update via the gear on my feeder page. I keep getting a NO_PUBKEY error. How do I fix this?
Thanks

[2021-09-02 15:24 EDT] performing manual update, action: piaware
[2021-09-02 15:24 EDT] manual update (user-initiated via their flightaware control page) requested by adept server
[2021-09-02 15:24 EDT] *** running command '/usr/lib/piaware/helpers/run-apt-get update' and logging output
[2021-09-02 15:24 EDT] run-apt-get(6218): Get:2 http://flightaware.com/adsb/piaware/files/packages buster InRelease [1,858 B]
[2021-09-02 15:24 EDT] run-apt-get(6218): Hit:1 http://repo.feed.flightradar24.com flightradar24 InRelease
[2021-09-02 15:24 EDT] run-apt-get(6218): Hit:4 http://raspbian.raspberrypi.org/raspbian buster InRelease
[2021-09-02 15:24 EDT] run-apt-get(6218): Hit:6 https://apt.rb24.com buster InRelease
[2021-09-02 15:24 EDT] run-apt-get(6218): Hit:5 https://linux.teamviewer.com/deb stable InRelease
[2021-09-02 15:24 EDT] run-apt-get(6218): The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B931BB28DE85F0DD
[2021-09-02 15:24 EDT] run-apt-get(6218): Fetched 1,858 B in 3s (718 B/s)
[2021-09-02 15:24 EDT] *** running command '/usr/lib/piaware/helpers/run-apt-get upgrade-package piaware' and logging output
[2021-09-02 15:24 EDT] run-apt-get(6218): W: Some index files failed to download. They have been ignored, or old ones used instead.
[2021-09-02 15:24 EDT] run-apt-get(6218): W: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B931BB28DE85F0DD
[2021-09-02 15:24 EDT] run-apt-get(6218): W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://flightaware.com/adsb/piaware/files/packages buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B931BB28DE85F0DD
[2021-09-02 15:24 EDT] run-apt-get(6645): Reading package lists...
[2021-09-02 15:24 EDT] run-apt-get(6645): Building dependency tree...
[2021-09-02 15:24 EDT] run-apt-get(6645): Reading state information...
[2021-09-02 15:24 EDT] run-apt-get(6645): Reading package lists...
[2021-09-02 15:24 EDT] run-apt-get(6645): 0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
[2021-09-02 15:24 EDT] run-apt-get(6645): Building dependency tree...
[2021-09-02 15:24 EDT] run-apt-get(6645): 0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
[2021-09-02 15:24 EDT] run-apt-get(6645): piaware is already the newest version (5.0).
[2021-09-02 15:24 EDT] attempting to restart piaware using 'systemctl --no-block try-restart piaware.service < /dev/null'...
[2021-09-02 15:24 EDT] restarting piaware. hopefully i'll be right back...
[2021-09-02 15:24 EDT] multilateration data no longer required, disabling mlat client
[2021-09-02 15:24 EDT] faup978 exited with SIG SIGTERM
[2021-09-02 15:24 EDT] site statistics URL: https://flightaware.com/adsb/stats/user/dannco01#stats-122484
[2021-09-02 15:24 EDT] logged in to FlightAware as user dannco01
[2021-09-02 15:24 EDT] Starting multilateration client: /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 2620:13d:c000:11::196:18804:3500808341
[2021-09-02 15:24 EDT] mlat-client(6827): Using UDP transport to 2620:13d:c000:11::196 port 18804
[2021-09-02 15:24 EDT] mlat-client(6827): Route MTU changed to 1500
[2021-09-02 15:24 EDT] mlat-client(6827): fa-mlat-client 0.2.11 starting up
[2021-09-02 15:24 EDT] mlat-client(6827): Input format changed to BEAST, 12MHz clock
[2021-09-02 15:24 EDT] Started faup978 (pid 6833) to connect to dump978-fa
[2021-09-02 15:24 EDT] mlat-client(6827): Listening for Beast-format results connection on port 30105
[2021-09-02 15:24 EDT] Starting faup978: /usr/lib/piaware/helpers/faup978 --connect localhost:30978
[2021-09-02 15:24 EDT] faup978(6833): Connected to [::1]:30978
[2021-09-02 15:24 EDT] faup978(6833): Connecting to localhost:30978
[2021-09-02 15:24 EDT] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 35.586 --lon -80.878
[2021-09-02 15:24 EDT] mlat-client(6827): Beast-format results connection with ::1:30104: connection established
[2021-09-02 15:24 EDT] Started faup1090 (pid 6830) to connect to dump1090-fa
[2021-09-02 15:24 EDT] mlat-client(6827): Route MTU changed to 1476
[2021-09-02 15:25 EDT] 464 msgs recv'd from dump1090-fa; 464 msgs sent to FlightAware
[2021-09-02 15:25 EDT] 9 msgs recv'd from dump978-fa; 9 msgs sent to FlightAware

tomvdhorst · September 2, 2021, 8:50pm

Solution 1: Quick NO_PUBKEY fix for a single repository / key.

If you’re only missing one public GPG repository key, you can run this command on your Ubuntu / Linux Mint / Pop!_OS / Debian system to fix it:

sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys THE_MISSING_KEY_HERE

You’ll have to replace THE_MISSING_KEY_HERE with the missing GPG key. The key is shown in the apt update / apt-get update log, after NO_PUBKEY. For example, in the error message I posted above, the missing GPG key that must be used in this command is EA8CACC073C3DB2A .

In you case the missing key is ```
B931BB28DE85F0DD

dannco01 · September 2, 2021, 8:56pm

I tried that but got the following:

pi@Flight:~ $ sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys B931BB28DE85F0DD
Executing: /tmp/apt-key-gpghome.2jePVNY1v7/gpg.1.sh --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys B931BB28DE85F0DD
gpg: keyserver receive failed: No name

tomvdhorst · September 2, 2021, 9:01pm

Did you update your repositories ?

sudo apt update

dannco01 · September 2, 2021, 9:07pm

Yeah have tried both ways. Still getting the errors.

pi@Flight:~ $ sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys B931BB28DE85F0DD
Executing: /tmp/apt-key-gpghome.aN2fzzWjsF/gpg.1.sh --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys B931BB28DE85F0DD
gpg: keyserver receive failed: No name
pi@Flight:~ $ sudo apt update
Hit:1 http://repo.feed.flightradar24.com flightradar24 InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease                   
Get:3 http://flightaware.com/adsb/piaware/files/packages buster InRelease [1,858 B]
Hit:4 https://linux.teamviewer.com/deb stable InRelease                        
Hit:5 http://raspbian.raspberrypi.org/raspbian buster InRelease                
Hit:6 https://apt.rb24.com buster InRelease                         
Hit:7 http://giteduberger.fr rpimonitor/ InRelease
Err:3 http://flightaware.com/adsb/piaware/files/packages buster InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B931BB28DE85F0DD
Fetched 1,858 B in 3s (728 B/s)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
29 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://flightaware.com/adsb/piaware/files/packages buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B931BB28DE85F0DD
W: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/buster/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B931BB28DE85F0DD
W: Some index files failed to download. They have been ignored, or old ones used instead.
pi@Flight:~ $ sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys B931BB28DE85F0DD
Executing: /tmp/apt-key-gpghome.WZJibZwjbv/gpg.1.sh --keyserver hkp://pool.sks-keyservers.net:80 --recv-keys B931BB28DE85F0DD
gpg: keyserver receive failed: No name

tomvdhorst · September 2, 2021, 9:13pm

You could try a different key server

Check this page for instructions
https://chrisjean.com/fix-apt-get-update-the-following-signatures-couldnt-be-verified-because-the-public-key-is-not-available/

dannco01 · September 2, 2021, 9:16pm

Fixed! That last way worked. Appreciate it!

tomvdhorst · September 2, 2021, 9:17pm

You’re welcome, glad I could help you

obj · September 3, 2021, 3:23am

That key is usually provided by the piaware-repository package that also installs the sources.list.d entry for the FA repository, so I’m not sure how your system got into a state where only one was installed.

system · September 3, 2022, 3:24am

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Error whilst upgrading to PiAware 6.1 ADS-B Flight Tracking	2	609	November 24, 2022
Update server issue??? ADS-B Flight Tracking	7	1720	August 15, 2016
Can't update to V4 ADS-B Flight Tracking	9	943	November 3, 2021
Flightaware stuck on 7.2 with add on package ADS-B Flight Tracking	1	306	January 27, 2024
Can't update PiAware, ERRORS ADS-B Flight Tracking	14	1537	February 16, 2019

PiAware 6 Upgrade Issue

Related Topics