[Sks-devel] Persistent differences with sks.keyserver.penguin.de

[Yaron Minsky]

I've noticed an interesting issue looking at the reconciliation logs. 
in particular, it appears that there is a persistent difference
between sks.keyserver.penguin.de and my computer.  This sequence comes
up over and over:

2004-11-24 22:24:31 Enabling gossip
2004-11-24 22:25:30 Recon partner: <ADDR_INET 134.169.171.249:11370>
2004-11-24 22:25:31 Initiating reconciliation
2004-11-24 22:25:31 Flush occured
2004-11-24 22:25:31 Done received
2004-11-24 22:25:31 Reconciliation complete
2004-11-24 22:25:31 Hashes recovered from <ADDR_INET 134.169.171.249:11371>
2004-11-24 22:25:31     E66B638A693C095062EA8EC1F24FCDA9
2004-11-24 22:25:31 Disabling gossip
2004-11-24 22:25:32 Requesting 1 missing keys from <ADDR_INET
134.169.171.249:11371>, starting with E66B638A693C095062EA8EC1F24FCDA9
2004-11-24 22:25:32 0 keys received
2004-11-24 22:25:32 Enabling gossip

As you can see, the key can't actually be retrieved.  I suspect that
this is because there is an inconsistency between that server's ptree
database and its key database.  Bjoern, could you try and recreate
your ptree database and see if this problem goes away.  I'm generally
quite curious how this siutation can come to be.

y