Bug 928395

Summary:	keys.gentoo.org: "500 Internal Server Error" on website, and gpg --recv-keys fails with "No data"
Product:	Gentoo Infrastructure	Reporter:	Ryan Tsien <i>
Component:	Other	Assignee:	Gentoo Infrastructure <infra-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	hlein, i
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	website screenshot

Description Ryan Tsien 2024-04-01 20:28:18 UTC

I have been unable to update gentoo gpg keys from keys.gentoo.org for several days.

for example:

> $ curl -Lf https://keys.gentoo.org/pks/lookup?op=get&search=0xDF84256885283521
> curl: (22) The requested URL returned error: 500

and

> $ gpg --keyserver hkps://keys.gentoo.org --recv-keys EF9538C9E8E64311A52CDEDFA13D0EF1914E7A72
> gpg: keyserver receive failed: No data

dig keys.gentoo.org info:

> keys.gentoo.org.	0	IN	CNAME	keys.geodns.gentoo.org.
> keys.geodns.gentoo.org.	0	IN	CNAME	keys.geodns-americas.gentoo.org.
> keys.geodns-americas.gentoo.org. 0 IN	A	140.211.166.190

I have checked it through several different servers around the world, but get the same error.

However, if I try another ip that is resolved by 'keys.geodns-asia.gentoo.org', it works fine:

> curl -Lf --resolve keys.gentoo.org:443:89.238.71.4 'https://keys.gentoo.org/pks/lookup?op=get&search=0xDF84256885283521'

Reproducible: Always

Comment 1 Ryan Tsien 2024-04-01 20:39:50 UTC

Created attachment 889230 [details]
website screenshot

Comment 2 Hank Leininger 2024-04-01 22:58:34 UTC

(In reply to Ryan Tsien from comment #0)
> I have been unable to update gentoo gpg keys from keys.gentoo.org for
> several days.
> 
> for example:
> 
> > $ curl -Lf https://keys.gentoo.org/pks/lookup?op=get&search=0xDF84256885283521
> > curl: (22) The requested URL returned error: 500
> 
> and
> 
> > $ gpg --keyserver hkps://keys.gentoo.org --recv-keys EF9538C9E8E64311A52CDEDFA13D0EF1914E7A72
> > gpg: keyserver receive failed: No data

I noticed the same about 36h ago. It seems to be resolved - both the above work from here now. Do they still error for you?

Comment 3 Ryan Tsien 2024-04-02 06:55:13 UTC

(In reply to Hank Leininger from comment #2)
> (In reply to Ryan Tsien from comment #0)
> 
> I noticed the same about 36h ago. It seems to be resolved - both the above
> work from here now. Do they still error for you?

So far it looks like the problem has been solved.