gpg key server refresh failed

--
I need to fix this error

sudo pacman-key --refresh-keys
gpg: refreshing 131 keys from hkps://hkps.pool.sks-keyservers.net
gpg: keyserver refresh failed: Server indicated a failure
==> ERROR: A specified local key could not be updated from a keyserver.

I have also tried this but no result

sudo pacman-key --refresh-keys --keyserver pgp.mit.edu
gpg: refreshing 131 keys from hkp://pgp.mit.edu
gpg: keyserver refresh failed: Server indicated a failure
==> ERROR: A specified local key could not be updated from a keyserver.

thank you

  1. Remove old (and possibly broken) keys by entering this command:
    sudo rm -r /etc/pacman.d/gnupg
  2. Reinstall keyrings including the latest keys:
    sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring
  3. Initialize the pacman keyring:
    sudo pacman-key --init
  4. Load the signature keys:
    sudo pacman-key --populate archlinux manjaro
  5. Refresh and update the signature keys:
    sudo pacman-key --refresh-keys
  6. Clear out the software packages downloaded during the aborted installation (optional):
    sudo pacman -Sc

after removing /etc/pacman.d/gnupg

I have tried

sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring
:: Synchronizing package databases...
core is up to date 0.0 B 0.00B/s 00:00 [---------------------------------] 0%
extra 1789.2 KiB 269K/s 00:07 [#################################] 100%
community is up to date 0.0 B 0.00B/s 00:00 [---------------------------------] 0%
multilib is up to date 0.0 B 0.00B/s 00:00 [---------------------------------] 0%
warning: gnupg-2.2.17-2 is up to date -- reinstalling
warning: archlinux-keyring-20190805-1 is up to date -- reinstalling
warning: manjaro-keyring-20190608-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (3) archlinux-keyring-20190805-1 gnupg-2.2.17-2 manjaro-keyring-20190608-1
Total Installed Size: 10.89 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(3/3) checking keys in keyring [#################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "EEEEE2EEEE2EEEEE" could not be looked up remotely
error: key "A6234074498E9CEE" could not be looked up remotely
error: key "CAA6A59611C7F07E" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

Please check this thread - what happened - and what to do.

And a note: It is not at all Manjaro related but a larger issue with keyserver network's autonomi.

Maybe change keyserver to pgp.mit.edu but due to the above mentioned issue be careful what you do.

I have tried

sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring
:: Synchronizing package databases...
core is up to date 0.0 B 0.00B/s 00:00 [---------------------------------] 0%
extra 1789.2 KiB 269K/s 00:07 [#################################] 100%
community is up to date 0.0 B 0.00B/s 00:00 [---------------------------------] 0%
multilib is up to date 0.0 B 0.00B/s 00:00 [---------------------------------] 0%
warning: gnupg-2.2.17-2 is up to date -- reinstalling
warning: archlinux-keyring-20190805-1 is up to date -- reinstalling
warning: manjaro-keyring-20190608-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (3) archlinux-keyring-20190805-1 gnupg-2.2.17-2 manjaro-keyring-20190608-1
Total Installed Size: 10.89 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(3/3) checking keys in keyring [#################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "EEEEE2EEEE2EEEEE" could not be looked up remotely
error: key "A6234074498E9CEE" could not be looked up remotely
error: key "CAA6A59611C7F07E" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

I have just installed manjaro, updated my system and tried to install texlive before getting the issue described in this post. Is that normal ?

Maybe this thread will help you.

thank you for your time

Is the solution provided in the tutorial (first thread) relevant as is to manjaro and pacman

For the solution provided in the second thread how to

drop NetworkManager and go to netctl

Use other servers. Here's a list of keyservers were used in sks-keyservers.net pool

For a starters may I suggest to use keys2.kfwebs.net? I found that server is quite responsive and reachable from my place (Indonesia)

sudo pacman-key --refresh-keys --keyserver keys2.kfwebs.net
gpg: refreshing 153 keys from hkp://keys2.kfwebs.net
gpg: key BBE43771487328A9: 27 signatures not checked due to missing keys
gpg: key BBE43771487328A9: "Bartlomiej Piotrowski <b@bpiotrowski.pl>" 15 new signatures
gpg: key 6D1655C14CE1C13E: 2 duplicate signatures removed
gpg: key 6D1655C14CE1C13E: 75 signatures not checked due to missing keys
gpg: key 6D1655C14CE1C13E: 1 bad signature
gpg: key 6D1655C14CE1C13E: 2 signatures reordered
gpg: key 6D1655C14CE1C13E: "Florian Pritz <bluewind@xinu.at>" 4 new signatures
...

same output error

sudo pacman-key --refresh-keys --keyserver keys2.kfwebs.net
gpg: refreshing 1 key from hkp://keys2.kfwebs.net
gpg: keyserver refresh failed: Server indicated a failure
==> ERROR: A specified local key could not be updated from a keyserver.

I had the exact same problem and I solved it by changing my DNS to Cloudflare's DNS of 1.1.1.1, 1.0.0.1 Make sure you reboot for it to take effect.

Then:

sudo pacman-key --init

sudo pacman-key --populate archlinux manjaro

sudo pacman-key --refresh-keys

1 Like

How to change DNS ?

I used this tutorial: https://www.addictivetips.com/ubuntu-linux-tips/change-dns-settings-on-linux/

I don't know what desktop version you are using so I can't give specific instructions. It is done through the network manager as described above.

@puffinthunder Thank you very much your solution solves the problem.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by Bytemark