| View previous topic :: View next topic |
| Author |
Message |
nelsooon
n00b
Joined: 08 Aug 2004
Posts: 73
|
 Posted: Sat Oct 19, 2019 11:29 pm Post subject: [SOLVED] emerge --sync - gpg: keyserver refresh failed |
 |
|
Hello,
Performing a portage sync through emerge --sync fails with the following error:
| Code: |
# emerge --sync
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys via WKD ... [ !! ]
* Refreshing keys from keyserver hkps://keys.gentoo.org ...OpenPGP keyring refresh failed:
gpg: refreshing 4 keys from hkps://keys.gentoo.org
gpg: keyserver refresh failed: No keyserver available
# emaint sync --repo gentoo
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys via WKD ... [ !! ]
* Refreshing keys from keyserver hkps://keys.gentoo.org ...OpenPGP keyring refresh failed:
gpg: refreshing 4 keys from hkps://keys.gentoo.org
gpg: keyserver refresh failed: No keyserver available
gpg --locate-key developer@gentoo.org
gpg: error retrieving 'developer@gentoo.org' via WKD: General error
gpg: error reading key: General error
|
Content of /etc/portage/repos.conf/gentoo.conf:
| Code: |
# cat /etc/portage/repos.conf/gentoo.conf
[DEFAULT]
main-repo = gentoo
[gentoo]
location = /var/db/repos/gentoo
sync-type = rsync
sync-uri = rsync://rsync.gentoo.org/gentoo-portage
auto-sync = yes
sync-rsync-verify-jobs = 1
sync-rsync-verify-metamanifest = yes
sync-rsync-verify-max-age = 24
sync-openpgp-key-path = /usr/share/openpgp-keys/gentoo-release.asc
sync-openpgp-key-refresh-retry-count = 40
sync-openpgp-key-refresh-retry-overall-timeout = 1200
sync-openpgp-key-refresh-retry-delay-exp-base = 2
sync-openpgp-key-refresh-retry-delay-max = 60
sync-openpgp-key-refresh-retry-delay-mult = 4
# for daily squashfs snapshots
#sync-type = squashdelta
#sync-uri = mirror://gentoo/../snapshots/squashfs
|
However, it works fine with emerge-webrsync.
This seems to have started happening after the SKS issue https://gentoo.org/news/2019/07/03/sks-key-poisoning.html
Any idea how to fix this?
Thanks,
Last edited by nelsooon on Sun Oct 20, 2019 1:32 am; edited 2 times in total |
|
| Back to top |
|
 |
mike155
Advocate
Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany
|
|
| Back to top |
|
|
nelsooon
n00b
Joined: 08 Aug 2004
Posts: 73
|
| Posted: Sun Oct 20, 2019 1:30 am Post subject: |
|
|
Thanks, reemerging gnutls fixed the issue:
| Code: |
gentoobox ~ # emerge --sync
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys via WKD ... [ !! ]
* Refreshing keys from keyserver hkps://keys.gentoo.org ...OpenPGP keyring refresh failed:
gpg: refreshing 4 keys from hkps://keys.gentoo.org
gpg: keyserver refresh failed: No keyserver available
^C
Exiting on signal Signals.SIGINT
gentoobox ~ # emerge -1 gnutls -q
* IMPORTANT: 11 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) net-libs/gnutls-3.6.7::gentoo
>>> Installing (1 of 1) net-libs/gnutls-3.6.7::gentoo
!!! existing preserved libs found
* IMPORTANT: 11 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
gentoobox ~ # emerge --sync
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys via WKD ... [ ok ]
>>> Starting rsync with rsync://89.238.71.6/gentoo-portage...
>>> Checking server timestamp ...
Welcome to turnstone.gentoo.org / rsync.gentoo.org
Server Address : 89.238.71.6, 2a00:1828:a00d:ffff::6
Contact Name : mirror-admin@gentoo.org
Hardware : 16 x Intel(R) Xeon(R) CPU E5530 @ 2.40GHz, 24160MB RAM
Sponsor : Manitu GmbH, St. Wendel, Germany
|
|
|
| Back to top |
|
|
archenroot
Apprentice
Joined: 13 Dec 2011
Posts: 218
Location: Lake Macha, Czech republic
|
| Posted: Thu May 28, 2020 7:11 am Post subject: |
|
|
I had system which has been shutdown for more than 1 year, reemerge gnutls helped initial emerge --sync, now I will look if the system is upgradable or I need fresh stage...
_________________
Emperor wants to control outer space Yoda wants to explore inner space that's the fundamental difference between good and bad sides of the Force |
|
| Back to top |
|
|
Moriah
Advocate
Joined: 27 Mar 2004
Posts: 2383
Location: Kentucky
|
| Posted: Sat Aug 29, 2020 3:26 am Post subject: |
|
|
Emerge --sync is failing on only 1 system:
| Code: |
# emerge --sync
>>> Syncing repository 'gentoo' into '/usr/portage'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys via WKD ... [ !! ]
* Refreshing keys from keyserver hkps://keys.gentoo.org ...OpenPGP keyring refresh failed:
gpg: refreshing 4 keys from hkps://keys.gentoo.org
gpg: keyserver refresh failed: Invalid URI
OpenPGP keyring refresh failed:
gpg: refreshing 4 keys from hkps://keys.gentoo.org
gpg: keyserver refresh failed: Invalid URI
|
I tried re-emerging gnutls, but it didn't help. This happened last week when I did my weekly updates, but I don't remember how I got it to work. I think I just re-emerged gnutls.
What is going wrong, and how do I fix it?  
_________________
The MyWord KJV Bible tool is at http://www.elilabs.com/~myword
Foghorn Leghorn is a Warner Bros. cartoon character. |
|
| Back to top |
|
|
guid0
Guru
Joined: 06 Jul 2003
Posts: 377
Location: The Netherlands / Nederland
|
| Posted: Sat Oct 17, 2020 8:31 pm Post subject: |
|
|
remerging gnutls did not work for me. i also had to remerge gnupg to get this to work.
- guid0 |
|
| Back to top |
|
|
Moriah
Advocate
Joined: 27 Mar 2004
Posts: 2383
Location: Kentucky
|
| Posted: Sat Oct 17, 2020 9:20 pm Post subject: |
|
|
Interesting. I got tired of fighting with it and just did an emerge-webrsync instead. Worked fine.
_________________
The MyWord KJV Bible tool is at http://www.elilabs.com/~myword
Foghorn Leghorn is a Warner Bros. cartoon character. |
|
| Back to top |
|
|
Jalanhi
n00b
Joined: 14 Feb 2025
Posts: 1
|
| Posted: Fri Feb 14, 2025 8:43 pm Post subject: |
|
|
Hello everyone,
I had the same message as Budoka but I managed to do an “emerge --sync”.
The solution I propose:
nano /etc/resolv.conf
and in the file [which will normally be empty], add :
nameserver 8.8.8.8
nameserver 8.8.4.4
ctrl+X to save, then yes, enter and finally recall the command and it should work without a hitch |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23113
|
| Posted: Fri Feb 14, 2025 9:29 pm Post subject: |
|
|
| Jalanhi wrote: | Hello everyone,
I had the same message as Budoka but I managed to do an “emerge --sync”. |
Welcome to the forums. Are you sure you posted in the right thread? Budoka has not posted here, and in any case, the error reported here would not be caused by bad DNS entries. | Jalanhi wrote: | The solution I propose:
nano /etc/resolv.conf
and in the file [which will normally be empty], add : |
No, this is not normally empty. If it is empty, something is wrong with your network, which needs to be fixed. |
|
| Back to top |
|
|
|
Portage & Programming
