Eu instalei o Ubuntu 16.04 na semana passada no meu servidor em um droplet da Digital Ocean e desde então não consigo atualizar nem atualizar nada no meu servidor.
Versão Ma 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
Eu recebo este erro depois de um 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.
Eu verifiquei por apt-key , que está lá e funcionando.
Eu tive o mesmo problema no meu Ubuntu no Digital Ocean (após uma atualização de distro).
Atualize seu kernel no site de administração do oceano digital (sim, é estranho). Existe uma opção "kernel" no menu do lado esquerdo onde você pode selecionar uma nova imagem do kernel.
No meu caso, a atualização foi da série 3.x para 4.x
Altere a permissão de / tmp trabalhada para mim.
chmod 777 /tmp
apt-get update --allow-unauthenticated
No meu caso, eu joguei com o AppArmor e ativei o modo de reclamação em sshd . Desativando-o por aa-disable /usr/sbin/sshd e re-conectando, resolvi meu problema.
Eu peguei esse mesmo problema e o "consertei" fazendo downgrade para a versão do apt presente em 15.10.
No meu caso, fiz o seguinte:
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
E escolha a opção menos perturbadora. AVISO: a escolha de uma opção inválida pode remover pacotes importantes do sistema, continue com cautela. Eu escolhi a seguinte opção:
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