Re: [Sks-devel] Slow syncing

[Arnold]

On 08-02-10 20:50, Arnold wrote:
> On 03-02-10 08:15, John Clizbe wrote:
>> Ryan wrote:
>>> I had the same issue develop last year, never figured out why but when the
>>> server was unexpectedly rebooted it came back and started working fine.  I
>>> recompiled/rebuilt the db, everything and nothing worked, it'd get stuck on 
>>> a
>>> loop requesting same keys over and over again never getting anywhere.
>>>
>>> I retired the server shortly after this reboot and I have not had any issues
>>> w/my current setup.
>> The only time I've seen anything like that recently was a problem that looked
>> like a locking issue on the DB files. I setup DB_CONFIG files in both KDB and
>> PTree and haven't had any problem since.
>>
>> address@hidden:/var/sks/KDB# cat DB_CONFIG
> 
> First I tried db4.6_verify on the database files. No luck. Then I removed
> the PTree directory and rebuilt the PTree -> same loop. Now I stopped the
> server, added the DB_CONFIG file in both the directories (DB and PTree) and
> still the same looping behaviour, as shown in the log below.
...
> Does anyone have any idea?

Apparently not.

After a busy period, I now found time for some more testing. I found
something strange. My log still shows many lines like:

2010-02-19 21:02:05 Requesting 200 missing keys from <ADDR_INET
76.191.185.172:11371>, starting with 1ECBAAC1A284D69B93901F676074D62F
2010-02-19 21:02:11 200 keys received
2010-02-19 21:02:16 Requesting 174 missing keys from <ADDR_INET
76.191.185.172:11371>, starting with 1ED076B0B2BF85AFD448275BFC7F9821
2010-02-19 21:02:21 174 keys received
2010-02-19 21:03:11 Recon partner: <ADDR_INET 76.191.185.172:11370>
2010-02-19 21:03:11 Initiating reconciliation
2010-02-19 21:03:17 Reconciliation complete
2010-02-19 21:03:17 10177 hashes recovered from <ADDR_INET 76.191.185.172:11371>

I figured the key with hash 1ECBAAC1A284D69B93901F676074D62F seems to be
missing on my server. To verify, I tried to query that key. Much to my
surprise, I found the following URL returns the correct key!!!
 
http://pgpkeys.mallos.nl:11371/pks/lookup?op=hget&search=1ECBAAC1A284D69B93901F676074D62F

This key has key ID 0x8523592f. Now the following URL *should* also give
some result, but is does NOT!

http://pgpkeys.mallos.nl:11371/pks/lookup?search=0x8523592F&hash=on

So, I guess my +/- 10000 missing keys are actually in my database, but not
indexed or so. Do you agree with this conclusion? If so, how can I recover
from this?

Thank you,
   Arnold

signature.asc
Description: OpenPGP digital signature