Error when attempting to update to latest release on Ubuntu relay node - please help

General
1

I have attempted to update an Ubuntu relay node that uses default locations for binary and data directories. According to the documentation, it should automatically update to the current release 3.4.2. That didn’t happen, so I tried to run apt-get update to force the update. When I run the command, I get the below error. I hid the public key value just in case it is sensitive, but it is an alpha-numeric string that starts with A and ends with E. Can anyone verify if this is a widespread issue, or is it isolated just to this relay node? Any ideas how to fix this?

Get:7 https://releases.algorand.com/deb stable InRelease [3,194 B]
Err:7 https://releases.algorand.com/deb stable InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A…E
Reading package lists… Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: https://releases.algorand.com/deb stable InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A…E
W: Failed to fetch https://releases.algorand.com/deb/dists/stable/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A…E
W: Some index files failed to download. They have been ignored, or old ones used instead.

2

I guess this is because the public key of Algorand got updated some time ago:

3

Ok, done. The node is running 3.4.2. Thanks for the help. It is odd though - I ran the add key command last night and the update failed. Everything checks out ok now though, so all good. Thanks for the assist.

1 Like