Updating apt

Hello, Today on my Puppet master, I am receiving the following error when performing an apt-get update: [email protected]:/home/user# apt-get update Get:1 file:/opt/puppetlabs/server/data/packages/public/2016.2.1/ubuntu-16.04-amd64-1.5.3 ./ In Release Ign:1 file:/opt/puppetlabs/server/data/packages/public/2016.2.1/ubuntu-16.04-amd64-1.5.3 ./ In Release Get:2 file:/opt/puppetlabs/server/data/packages/public/2016.2.1/ubuntu-16.04-amd64-1.5.3 ./ Release [505 B] Get:2 file:/opt/puppetlabs/server/data/packages/public/2016.2.1/ubuntu-16.04-amd64-1.5.3 ./ Release [505 B] Err:3 file:/opt/puppetlabs/server/data/packages/public/2016.2.1/ubuntu-16.04-amd64-1.5.3 ./ The following signatures couldn't be verified because the public key is not available: NOPUBKEY 1054B7A24BD6EC30 Hit:4 xenial In Release Get:5 xenial-security In Release [102 k B] Get:6 xenial-updates In Release [102 k B] Get:7 xenial-backports In Release [102 k B] Fetched 306 k B in 0s (412 k B/s) Reading package lists...

Done W: An error occurred during the signature verification.

To keep your NAS in a healthy state you should know about the two methods of updating your OMV.Then stay current by using your Linux package manager to install fresh own Cloud packages.After installing upgraded packages you must run a few more steps to complete the upgrade.The folowing sections will outline who to run a update for each version Since 0.3.7.1 you can simply use the 'omv-release-upgrade' CLI command to upgrade your system.The method shown below is obsolete and only neccessary if you're on a version lower than 0.3.7.1. The logfiles in /var/log/patchman/ will point out that the shutdown signal was received by the process, and will be processed as soon as possible.

394

Leave a Reply