J'ai installé Ubuntu 16.04 la semaine dernière sur mon serveur avec un droplet Digital Ocean et depuis, je ne peux plus rien mettre à jour ni mettre à niveau sur mon serveur. Ma version Linux 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Je reçois cette erreur après un Sudo apt-get update
:
Get:1 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease [23.9 kB]
Ign:1 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
Hit:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Get:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease [247 kB]
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Could not execute 'apt-key' to verify signature (is gnupg installed?)
Err:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Could not execute 'apt-key' to verify signature (is gnupg installed?)
Hit:7 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Err:7 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
Could not execute 'apt-key' to verify signature (is gnupg installed?)
Hit:8 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Err:8 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
Could not execute 'apt-key' to verify signature (is gnupg installed?)
Fetched 272 kB in 0s (363 kB/s)
Reading package lists... Done
W: GPG error: http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease: Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: The repository 'http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://security.ubuntu.com/ubuntu xenial-security InRelease: Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: GPG error: https://apt.dockerproject.org/repo ubuntu-xenial Release: Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu xenial InRelease: Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease: Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease: Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Could not execute 'apt-key' to verify signature (is gnupg installed?)
W: Some index files failed to download. They have been ignored, or old ones used instead.
J'ai vérifié apt-key
qui est là et fonctionne.
J'ai eu le même problème sur mon droplet Ubuntu à Digital Ocean (après une mise à niveau de la distribution).
Il suffit de mettre à jour votre noyau dans le site d’administration de Digital Ocean (oui, c’est bizarre). Il y a une option "noyau" dans le menu sur le côté gauche où vous pouvez sélectionner une nouvelle image du noyau.
Dans mon cas, la mise à niveau était de la série 3.x à la série 4.x
Changer la permission de/tmp a fonctionné pour moi.
chmod 777 /tmp
apt-get update --allow-unauthenticated
Dans mon cas, j'ai joué avec AppArmor et activé le mode de réclamation sur sshd
. La désactivation par aa-disable /usr/sbin/sshd
et la reconnexion ont corrigé mon problème.
J'ai eu le même problème et je l'ai "corrigé" en rétrogradant à la version d'apt présente dans 15.10.
Dans mon cas, j'ai fait ce qui suit:
Sudo add-apt-repository 'deb http://archive.ubuntu.com/ubuntu wily-updates main'
Sudo apt-get update # and ignore the errors
Sudo aptitude install apt=1.0.10.2ubuntu2
Et choisissez l'option la moins perturbante. ATTENTION: Le choix d'une mauvaise option peut supprimer des paquets importants de votre système, procédez avec prudence. J'ai choisi l'option suivante:
The following actions will resolve these dependencies:
Remove the following packages:
1) libapt-inst2.0
2) libapt-pkg5.0
Install the following packages:
3) libapt-inst1.7 [1.0.10.2ubuntu2 (wily-updates)]
Downgrade the following packages:
4) apt-transport-https [1.2.10ubuntu1 (now, xenial) -> 1.0.10.2ubuntu2 (wily-updates)]
5) apt-utils [1.2.10ubuntu1 (now, xenial) -> 1.0.10.2ubuntu2 (wily-updates)]
6) aptitude [0.7.4-2ubuntu2 (now, xenial) -> 0.7.3-1ubuntu1.1 (wily-updates)]
7) aptitude-common [0.7.4-2ubuntu2 (now, xenial) -> 0.7.3-1ubuntu1.1 (wily-updates)]
8) python-apt [1.1.0~beta1build1 (now, xenial) -> 1.0.1ubuntu0.1 (wily-updates)]
9) python3-apt [1.1.0~beta1build1 (now, xenial) -> 1.0.1ubuntu0.1 (wily-updates)]
Leave the following dependencies unresolved:
10) libapt-pkg5.0 recommends apt (>= 1.2.10ubuntu1)
Accept this solution? [Y/n/q/?] Y