-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/25/2013 3:29 PM, Daniel Kahn Gillmor wrote:
>
> are you running your keyserver behind an HTTP proxy? It's a known
> flaw in SKS that a single slow client can prevent any other client
> from accessing the service. using a reverse proxy directly
On 02/25/2013 03:21 PM, David Benfell wrote:
> If I'm reading this right, it's still running, but these timeouts are
> ridiculous:
>
> graton% gpg --recv-key "2512E3C7"
> gpg: requesting key 2512E3C7 from hkp server disunitedstates.com
> gpg: keyserver timed out
> gpg: keyserver receive failed: ke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
My sks server does not seem to be healthy.
It looks to me like the problem may be the database. Here's a snippet
from db.log:
2013-02-25 14:54:52 Adding hash 3CE97D7E43467554B625403596990171
2013-02-25 14:54:52 Del'ng hash 63E14B0382B749F673
