Troubleshooting Failed Veeam PN Update
If the Veeam PN update fails, you can look into the updater logs at /var/log/Veeam/veeam-updater/updater.log.txt and try the following solutions:
If Veeam PN update fails due to expired PGP keys for repository.veeam.com, the /var/log/Veeam/veeam-updater/updater.log.txt will contain the following error:
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repository.veeam.com/pn/public pn InRelease: The following signatures were invalid: EXPKEYSIG 3268CF038EEC045B Veeam Software Repository key <email@example.com>
Failed to fetch http://repository.veeam.com/pn/public/dists/pn/InRelease The following signatures were invalid: EXPKEYSIG 3268CF038EEC045B Veeam Software Repository key <firstname.lastname@example.org>
Some index files failed to download. They have been ignored, or old ones used instead.
To resolve the issue, you must download a new PGP key and update the apt tool. To update the pgp key, do the following:
- Open the console of Veeam PN appliance machine.
- To remove the old PGP key, run the following command:
sudo apt-key del FBF8A590
- To download a new gpg, run the following command:
sudo wget http://repository.veeam.com/keys/veeam.gpg -O /etc/apt/trusted.gpg.d/veeam.gpg
- Update the APT package manager:
sudo apt update
- Now you can update Veeam PN as described in Updating Veeam PN.
If you have deployed Veeam PN before WireGuard moved its packages from PPA to Ubuntu repositories, the update process will fail.
To resolve the issue, remove the WireGuard's PPA repository from the list of apt sources:
sudo apt-add-repository -r ppa:wireguard/wireguard