Error key could not be looked up remotely

Ran into issue today trying to update my system, I searched forums for this specific problem to no avail.
  • Index
  • » Pacman & Package Upgrade Issues
  • » [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

#1 2015-02-08 22:54:25

pdq
Member
Registered: 2012-02-12
Posts: 4

[SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

Ran into issue today trying to update my system, I searched forums for this specific problem to no avail. tongue

sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (20) cmake-3.1.2-1  gparted-0.21.0-2  kdebase-dolphin-14.12.2-1
              kdebase-lib-14.12.2-1  kdebase-runtime-14.12.2-2
              kdegraphics-mobipocket-14.12.2-1  kdelibs-4.14.5-1
              kdemultimedia-ffmpegthumbs-14.12.2-1  kdepimlibs-4.14.5-1
              kdeutils-ark-14.12.2-1  libkcddb-14.12.2-1  linux-3.18.6-1
              linux-headers-3.18.6-1  livestreamer-1.11.1-2  nvidia-346.35-6
              oxygen-icons-14.12.2-1  packagekit-1.0.4-3  parted-3.2-2
              python2-pillow-2.7.0-1  udisks2-2.1.4-1

Total Installed Size:  291.11 MiB
Net Upgrade Size:       -0.43 MiB

:: Proceed with installation? [Y/n] y
(20/20) checking keys in keyring                   [----------------------] 100%
downloading required keys...
error: key "A6234074498E9CEE" 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.

Suggestions?

Last edited by pdq (2015-02-08 23:20:37)

#2 2015-02-08 23:00:41

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,211

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

#3 2015-02-08 23:10:07

pdq
Member
Registered: 2012-02-12
Posts: 4

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

No luck with that.

sudo pacman -S archlinux-keyring && sudo pacman -Syu
warning: archlinux-keyring-20141218-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20141218-1

Total Installed Size:  0.62 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [----------------------] 100%
(1/1) checking package integrity                   [----------------------] 100%
(1/1) loading package files                        [----------------------] 100%
(1/1) checking for file conflicts                  [----------------------] 100%
(1/1) checking available disk space                [----------------------] 100%
(1/1) reinstalling archlinux-keyring               [----------------------] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
  -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
==> Updating trust database...
gpg: next trustdb check due at 2016-01-22
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (20) cmake-3.1.2-1  gparted-0.21.0-2  kdebase-dolphin-14.12.2-1
              kdebase-lib-14.12.2-1  kdebase-runtime-14.12.2-2
              kdegraphics-mobipocket-14.12.2-1  kdelibs-4.14.5-1
              kdemultimedia-ffmpegthumbs-14.12.2-1  kdepimlibs-4.14.5-1
              kdeutils-ark-14.12.2-1  libkcddb-14.12.2-1  linux-3.18.6-1
              linux-headers-3.18.6-1  livestreamer-1.11.1-2  nvidia-346.35-6
              oxygen-icons-14.12.2-1  packagekit-1.0.4-3  parted-3.2-2
              python2-pillow-2.7.0-1  udisks2-2.1.4-1

Total Installed Size:  291.11 MiB
Net Upgrade Size:       -0.43 MiB

:: Proceed with installation? [Y/n] y
(20/20) checking keys in keyring                   [----------------------] 100%
downloading required keys...
error: key "A6234074498E9CEE" 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.

#4 2015-02-08 23:13:39

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,211

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

#5 2015-02-08 23:19:47

pdq
Member
Registered: 2012-02-12
Posts: 4

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

Thanks frank604, I got it to work on the 3rd server attempt.  big_smile

#keyserver hkp://pool.sks-keyservers.net
#keyserver hkp://pgp.mit.edu:11371
keyserver hkp://keyserver.kjsl.com:80 <— finally worked

My issue is solved! I missed that part in the wiki, thanks again. smile

Last edited by pdq (2015-02-08 23:26:33)

#6 2015-02-08 23:26:28

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,211

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

Cool stuff.  happy Syu’n away big_smile

#7 2015-02-09 02:32:57

ElectricPrism
Member
Registered: 2012-12-07
Posts: 35

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

/etc/pacman.d/gnupg/gpg.conf

keyserver hkp://keyserver.kjsl.com:80

didn’t work for me sad

EDIT:

Here’s what fixed the problem for me:

# Archive the GNUPG directories
mv $HOME/.gnupg $HOME/.gnupg.bak
sudo mv /root/.gnupg /root/.gnupg.bak

# This one fixed the GNUPG Error
dirmngr </dev/null

# Refresh Keys
pacman-key --init
pacman-key --populate archlinux
pacman-key --refresh-keys

Last edited by ElectricPrism (2015-02-09 02:44:29)

#8 2015-02-09 23:59:29

McMuntjac
Member
Registered: 2015-02-09
Posts: 1

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

ElectricPrism wrote:

…

# Archive the GNUPG directories
mv $HOME/.gnupg $HOME/.gnupg.bak
>sudo mv /etc/pacman.d/gnupg /etc/pacman.d/gnupg.bak 
...

it was «mv /etc/pacman.d/gnupg /etc/pacman.d/gnupg.bak» rather than the same at «…/root/.gnupg…» that actually did something for me and allowed dirmngr to work, not sure if I’m being obvious. I should be, given that is what is written in the wiki (which needs a different password from the forum for the same profile as the forum?).

Last edited by McMuntjac (2015-02-10 00:04:26)

#9 2015-02-10 12:06:12

KatsumeBlisk
Member
Registered: 2010-12-08
Posts: 7

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

I’m still having this issue. I’ve tried switching keyservers and rebuilding the keyring. I’m not updating but installing packagekit on a new system. I see that you were upgrading that package and that the key that was having the issue is the same string. Any help? packagekit isn’t required for my system, but it makes it easier to use.

#10 2015-02-10 14:10:29

artem.jackson
Member
Registered: 2014-09-06
Posts: 22

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

Have the same problem.
But nothing helps.

#11 2015-02-10 15:32:47

mauritiusdadd
Member
From: Benevento, Italy
Registered: 2013-10-27
Posts: 776

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

Hi, I had the same problem and there is also a bug report here: https://bugs.archlinux.org/task/43759

For me the following procedure worked (as root):

# rm -R /etc/pacman.d/gnupg/
# rm -R /root/.gnupg/  # only if the directory exists
# gpg --refresh-keys
# pacman-key --init && pacman-key --populate
# pacman-key --refresh-keys

—EDIT—

Note that since this procedure resets your pacman keyring, you have to add again any custom key

Last edited by mauritiusdadd (2015-02-20 05:55:13)

registered linux user #588260 • github

— When you have eliminated the impossible, whatever remains, however improbable, must be the truth — Spock | Sherlock Holmes

#12 2015-02-11 14:07:04

poki2
Member
Registered: 2015-02-11
Posts: 1

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

mauritiusdadd wrote:

Hi, I had the same problem and there is also a bug report here: https://bugs.archlinux.org/task/43759

For me the following procedure worked (as root):

# rm -R /etc/pacman.d/gnupg/
# rm -R /root/.gnupg/  # only if the directory exists
# gpg --refresh-keys
# pacman-key --init && pacman-key --populate
# pacman-key --refresh-keys

This worked perfectly fine for me. Thanks.

#13 2015-02-12 09:28:47

despian
Member
Registered: 2014-04-13
Posts: 10

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

mauritiusdadd wrote:

Hi, I had the same problem and there is also a bug report here: https://bugs.archlinux.org/task/43759

For me the following procedure worked (as root):

# rm -R /etc/pacman.d/gnupg/
# rm -R /root/.gnupg/  # only if the directory exists
# gpg --refresh-keys
# pacman-key --init && pacman-key --populate
# pacman-key --refresh-keys

+1 worked for me too.

#14 2015-03-06 06:37:03

dharmaslacker
Member
From: Seattle, WA, USA
Registered: 2014-12-04
Posts: 6

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

I simply used the advice at https://bbs.archlinux.org/, namely:

sudo pacman -S archlinux-keyring && sudo pacman -Syu

That worked for me.

#15 2015-05-26 05:56:49

mattz
Member
Registered: 2015-05-26
Posts: 1

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

Had the same problem during initial install. Noticed that date was set to Jan 1 2000. As a result, keys were future-dated. No more problems after setting the date/time correctly.

#16 2017-11-17 20:27:50

theking2
Banned
From: Romanshorn Switzerland
Registered: 2009-03-04
Posts: 372

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

Hi there.

Have a similar problem but at pacman-key —refresh-keys I get:

gpg: refreshing 94 keys from hkp://pool.sks-keyservers.net
gpg: keyserver refresh failed: Invalid argument
==> ERROR: A specified local key could not be updated from a keyserver.

archlinux on a Gigabyte C1037UN-EU, 16GiB
a Promise  PDC40718 based ZFS set
root on a Samsung SSD PB22-J
running LogitechMediaServer(-git), Samba, MiniDLNA, TOR

#17 2017-11-17 20:55:29

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,018
Website

Re: [SOLVED] error: key «A6234074498E9CEE» could not be looked up remotely

You really don’t learn, do you? Even after eight years, and repeated reminders, you still choose to ignore our rules. Enough is enough.

Closing, binning, banning.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Источник

#
7 лет, 2 месяца назад

Темы:

1

Сообщения:

3

Участник с: 23 ноября 2015

При вводе

pacstrap -i /mnt base base-devel

Все идёт нормально до момента загрузки необходимых ключей
Результат:

ошибка: key "F99FFE0FEAE999BD" could not be looked up remotely

И система не устанавливается :-(
Как быть? Что делать?

scorpid

#
7 лет, 2 месяца назад

(отредактировано

7 лет, 2 месяца назад)

scorpid avatar

Темы:

4

Сообщения:

294

Участник с: 14 апреля 2015

pacman -Syy, ой затупил :). Вообще скрипт должен сам всё делать, в том числе и обновление ключей.

A.T.W.A.

#
7 лет, 2 месяца назад

A.T.W.A. avatar

Темы:

14

Сообщения:

657

Участник с: 21 марта 2011

Может время неправильное?

https://t.me/atvva

Sava

#
7 лет, 2 месяца назад

Темы:

1

Сообщения:

3

Участник с: 23 ноября 2015

A.T.W.A.
Может время неправильное?

Может быть, потому что ставлю на старый ноут. Батарейка у него эта видимо разряжена.
Но даже при установке времени по этому методу

https://wiki.archlinux.org/index.php/Systemd-timesyncd_(%D0%A0%D1%83%D1%81%D1%81%D0%BA%D0%B8%D0%B9)

почему-то не работает

vadik

#
7 лет, 2 месяца назад

Темы:

55

Сообщения:

5410

Участник с: 17 августа 2009

Отключите пока эту проверку ключей. Когда разберетесь — включите.

Fean

#
7 лет, 2 месяца назад

(отредактировано

7 лет, 2 месяца назад)

Темы:

5

Сообщения:

79

Участник с: 19 января 2015

Могу ошибаться, но недавно при установке Арча с Evo-lution (в общем-то чистый Арч, только меню установки неплохое) была то же самое. В одном случае просто поставил с родного Арча, в других случаях выполнил в меню установки «обновить ключи пакмана». Не уверен, какая именно команда в Арче это делает, «pacman-key —init» или «pacman-key —populate archlinux». Кажется, вторая. Или это из других областей?

Sava

#
7 лет, 2 месяца назад

Темы:

1

Сообщения:

3

Участник с: 23 ноября 2015

vadik
Отключите пока эту проверку ключей. Когда разберетесь — включите.

Можете подсказать как?)

Fean
Могу ошибаться, но недавно при установке Арча с Evo-lution (в общем-то чистый Арч, только меню установки неплохое) была то же самое. В одном случае просто поставил с родного Арча, в других случаях выполнил в меню установки «обновить ключи пакмана». Не уверен, какая именно команда в Арче это делает, «pacman-key —init» или «pacman-key —populate archlinux». Кажется, вторая. Или это из других областей?

Не очень понял, но попробую воспользоваться этими командами =)

vadik

#
7 лет, 2 месяца назад

Темы:

55

Сообщения:

5410

Участник с: 17 августа 2009

Sava
Можете подсказать как?)

В /etc/pacman.conf закомментировать строки SigLevel = PackageRequired.
Источник

This is the long video. I do not know the solution and we analyze the problem together with the help of the Arch Wiki.

We have installed ArchMerge 6.2.1 (other ArchMerge and ArchMergeD ssd’s are getting the same error) after asking to update with

sudo pacman -Syu

Then we get this error about …

Key “123456789” could not be looked up remotely.

First you check the Arch Wiki and read the solution from there.

First thing we try is this

sudo pacman-key --refresh-keys

We get an error:

gpg: keyserver refresh failed : Server indicated a failure

Second thing we try is to update the archlinux-keyring but if you have followed the video than you see that there was no recent update of this package. It is very unlikely that a reinstall will fix our issue.

sudo pacman -Sy archlinux-keyring
sudo pacman -Syu

Third attempt is to reset all pacman keys from this link on Arch Wiki.

sudo pacman-key --init
sudo pacman-key --refresh-keys

On any other day this solution will work BUT then it struck me that there might be an issue in communicating with the keyservers.

This is what triggered my search to analyze my issue.

“which might not be possible e.g. behind proxys or firewalls and results in the stated error”

If you check this wiki page about gpg it is suggested to put a port number behind the keyserver line.

  • If your network blocks ports used for hkp/hkps, you may need to specify port 80, i.e.pool.sks-keyservers.net:80

In my personal case I need to add a port to the get the keys from the keyserver.

There is no communication between my computer and the keyserver.

Can be due to a firewall on your personal computer, the firewall on your router, the firewall on your modem or the firewall of your internet service provider. I think the last one since nothing change on my end.

Edit this file and add port 80 behind the line with the keyserver information. Make a backup if you want to.
That solved my issue. It might solve yours too.

subl3 /etc/pacman.d/gnupg/gpg.conf
keyserver hkp://pool.sks-keyservers.net:80

You can also use the hkps keyservers and port

keyserver hkps://hkps.pool.sks-keyservers.net:443
Источник

I’m trying to install gnome on ArchLinux ARM, which runs in a UTM virtual machine using pacman -S gnome. It’s showing me the list of packages that need to be installed, I accept the installation. After it shows that I wrote in the code section and holds up for an answer. If I type n, it shows me this choosing again.

:: Import PGP key 77193F152BDBE6A6, "Arch Linux ARM Build System <builder+n1@archlinuxarm.org>"? [Y/n] y
error: key "77193F152BDBE6A6" could not be looked up remotely

asked Sep 9, 2021 at 6:07

Intolighter's user avatar

It works for me after running:

pacman-key --init

pacman-key --populate archlinuxarm

According to the Package Signing on Archlinux Arm wiki, turns out the need of verifying the master keys with special archlinuxarm instead of archlinux, please view the page above for standard configuration to enable signature checking in ArchLinux ARM.

answered Mar 9, 2022 at 23:26

Rui's user avatar

Источник

Total Installed Size: 4441.99 MiB
Net Upgrade Size: 77.06 MiB

:: Proceed with installation? [Y/n] y
(576/576) checking keys in keyring [############################] 100%
warning: Public keyring not found; have you run ‘pacman-key —init’?
downloading required keys…
error: key «F99FFE0FEAE999BD» could not be looked up remotely
error: key «94657AB20F2A092B» could not be looked up remotely
error: key «E62F853100F0D0F0» could not be looked up remotely
error: key «A5E9288C4FA415FA» could not be looked up remotely
error: key «3C1C876030B65FE2» could not be looked up remotely
error: key «B02854ED753E0F1F» could not be looked up remotely
error: key «1EB2638FF56C0C53» could not be looked up remotely
error: key «976AC6FA3B94FA10» could not be looked up remotely
error: key «BBE43771487328A9» could not be looked up remotely
error: key «771DF6627EDF681F» could not be looked up remotely
error: key «6D1655C14CE1C13E» could not be looked up remotely
error: key «7F2D434B9741E8AC» could not be looked up remotely
error: key «786C63F330D7CB92» could not be looked up remotely
error: key «51E8B148A9999C34» could not be looked up remotely
error: key «2C089F09AC97B894» could not be looked up remotely
error: key «CAA6A59611C7F07E» could not be looked up remotely
error: key «06096A6AD1CEDDAC» could not be looked up remotely
error: key «7A4E76095D8A52E4» could not be looked up remotely
error: key «AFF5D95098BC6FF5» could not be looked up remotely
error: key «8DB9F8C18DF53602» could not be looked up remotely
error: key «DAD3B211663CA268» could not be looked up remotely
error: key «E711306E3C4F88BC» could not be looked up remotely
error: key «5C2E46A0F53A76ED» could not be looked up remotely
error: key «E613C09CB4440678» could not be looked up remotely
error: key «DA6426DD215B37AD» could not be looked up remotely
error: key «39E4B877E62EB915» could not be looked up remotely
error: key «DB323392796CA067» could not be looked up remotely
error: key «396E3E25BAB142C1» could not be looked up remotely
error: key «A6234074498E9CEE» could not be looked up remotely
error: key «62443D89B35859F8» could not be looked up remotely
error: key «C06086337C50773E» could not be looked up remotely
error: key «8934292D604F8BA2» could not be looked up remotely
error: key «426991CD8406FFF3» could not be looked up remotely
error: key «9BDCF497A4BBCC7F» could not be looked up remotely
error: key «65C110C1EA433FC7» 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.

что делать? помогите.

Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.

Источник

Понравилась статья? Поделить с друзьями:
  • Error jusched exe
  • Error juris транскрипция
  • Error juris перевод
  • Error junk at end of line first unrecognized character is
  • Error jump to case label fpermissive