Re: [Sks-devel] sks recon getting same keys over and over again

[Marco Nenciarini]

On Wed, Aug 02, 2006 at 08:52:52PM +0200, Sascha Silbe wrote:
> 
> After having problem with the update to to sks-1.0.10 and ocaml-3.08.3 
> and Berkeley DB 4.1 some time ago (and not having time to fix it due to 
> exams), I've rebuilt the database from fresh keydumps [1] yesterday. 
> During the night, sks recon catched up with most updates, but now it's 
> stuck in a loop:
> 
> [snip]
> 
> The documentation wiki [2] is down due to hardware failure currently, so 
> I cannot check it for explanations and/or solutions.
> I've tried getting the first mentioned key 
> (00255E90BBC68E7F8E45701361E7FDAD) from both subkeys.pgp.net and the 
> recon peer (using the last 8/16 characters of it as key ID), but without 
> success.
> If this key does not exist on any server, why does sks think it needs 
> it? And why does it receive the full 100 keys, if at least one of them 
> doesn't exist?
> 
> 
> [1] ftp://ftp.pramberger.at/services/keyserver/keydump/
> [2] http://documentation.penguin.de//cgi-bin/twiki/view/SKSKeyserver/WebHome
> 

This is probably because a PTree corruption. Please try to regenerate
your PTree.

Ciao

-- 
---------------------------------------------------------------------
|    Marco Nenciarini    | Debian/GNU Linux Developer - Plug Member |
| address@hidden | http://www.prato.linux.it/~mnencia       |
---------------------------------------------------------------------
Key fingerprint = FED9 69C7 9E67 21F5 7D95  5270 6864 730D F095 E5E4

signature.asc
Description: Digital signature