-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/28/2013 10:23 AM, Kristian Fiskerstrand wrote: | On 02/28/2013 07:01 PM, Doug Barton wrote: |> On 02/28/2013 09:44 AM, Kristian Fiskerstrand wrote: | Hi Doug, |> | | | | ... | |> Yes, I'm talking to different servers (as would be expected). |> Just tried it a few times ... | | | At least that explains it. For what it is worth both of those | servers are working for me now. I'd typically expect this response | while the server is running its statistics update. I notice that | the last stats update on the server you had issues with was at | 19:03 CET, so just about 20 minutes ago. Hopefully both are working | for you as well now.
~From your description I suspected that it was probably load related, so that's understandable. My concern is that I'm seeing that error way more often than not when sending keys over the last few days, and I don't remember ever seeing it before. OTOH, I recently attended a key signing party with over 40 participants, so I have been busy pulling down other people's keys, and uploading mine when new signatures come in, so I've been hitting the servers harder than usual. Sounds like I'm just getting unlucky? Doug -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQEcBAEBCAAGBQJRL6GjAAoJEFzGhvEaGryE77wIAKFYkkYbqJ1RzTi0KrC9Luzs q8a2/gToWdR7+dDLWyd/rxeLT84YSCX71IPDYIaE4zUVh6sDQ2TqVf8dGdjL8mTS ys0Oz1tXRbxi6W0s+6tsBgmAm37DxN0mROw81OI65OC0sc747/8++5tyRx48m2SC WLy9PJ3/8Dt0qe3C2T/SiszllAS1cJFnKjqyNOs6ousObj12zSuqiFKkt1G6huzc XbwVs9u/aZIBmUwGwcP8YpOPiHe+q05CQGIWfXLkdyGn3mnKMx8rgQEBZzdaXLMG HMFMsBXF96q/PjvvYaDE59enMvOxbwlmycHTmHmnBDIRAYA3fNGntpeVBaOZtC4= =2F5Y -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users