[Sks-devel] more sks db problems

[Chris Kuethe]

Thinking I may have bollixed something while loading my last keyring,
I tried a complete rebuild with the keydump from debian/noreply. The
load completed successfully, so I ran cleandb to make the database
ready to start syncing.

here's what cleandb says:
2004-01-29 09:01:36 Opening log
2004-01-29 09:01:36 Opening KeyDB database
2004-01-29 09:01:37 Keydb opened
2004-01-29 09:01:37 Database already deduped
2004-01-29 09:01:37 Merging keys in database
2004-01-29 09:01:37 Starting key merge
2004-01-29 09:01:37 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:37 Hash: 4A890E696081B0D3B747143BFB881E79
2004-01-29 09:01:37 Hash: 600066ED625D84CE88211E0252A675D7
2004-01-29 09:01:37 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:37 Hash: AAC4EE9160676C62F1BEDF8B74108154
2004-01-29 09:01:37 Hash: F87E832671B9C61F4ADAABFAC83DBC86
2004-01-29 09:01:37 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:37 Hash: 6A0F6639D1B70ECA6D8205F7A86D792C
2004-01-29 09:01:37 Hash: A01F53A7B4FB435470BFCBBF0E07160C
2004-01-29 09:01:37 10 thousand steps processed
2004-01-29 09:01:37 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:37 Hash: 1768F356D81C537E811183F5AB07A2AC
2004-01-29 09:01:37 Hash: 8EC45621CAF6D96D217E2DD7E01AD261
2004-01-29 09:01:38 20 thousand steps processed
2004-01-29 09:01:38 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:38 Hash: 3A2D825000E94AD1FF9CC832CF44CDC5
2004-01-29 09:01:38 Hash: B33E5F8EABE7AD4C465150B07D96983C
2004-01-29 09:01:38 30 thousand steps processed
2004-01-29 09:01:38 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:38 Hash: 69EE7077DBB67C5DBE17ADDC6130BED4
2004-01-29 09:01:38 Hash: A24947DB4E81A5EEC3528D7A11294E60
2004-01-29 09:01:38 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:38 Hash: 58BE68CE36AF26FD19A948BC298CFF77
2004-01-29 09:01:38 Hash: 8615A327D1DB0F9541151AA2BA246688
2004-01-29 09:01:38 40 thousand steps processed
2004-01-29 09:01:38 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:38 Hash: 1A5E96A986C18513217BE436D39ECA14
2004-01-29 09:01:38 Hash: F5A20D0DCE2F4B84FDA139C127B12670
2004-01-29 09:01:38 50 thousand steps processed
2004-01-29 09:01:39 Multiple keys found with same ID.  merge_from_hashes called
2004-01-29 09:01:39 Hash: 13E37C592A17EA2A345ED114BEA5D281
2004-01-29 09:01:39 Hash: 9C2FDB7AC49D748F12937C01463FB8B3
Fatal error: exception KeyMerge.Unparseable_packet_sequence
*exits here*

so i ran pbuild which claims to have completed successfully:
...
2004-01-29 09:09:49 1935000 hashes processed
2004-01-29 09:09:50 1937671 hashes processed
2004-01-29 09:09:50 Cleaning Tree.

yet I get the same error running cleandb... so i'm going to rebuild again,
this time doing a build with just one file used to "build" and then i'm
going to do a cleandb, pbuild and then merge all the keyfiles again to see
if that helps. feh.

by the way, what's the deal with all hashqueries?

2004-01-29 09:32:50 Handling /pks/hashquery                                     
2004-01-29 09:32:50 100 keys found                                              
2004-01-29 09:32:54 Handling /pks/hashquery                                     
2004-01-29 09:32:54 100 keys found                                              

every time i get one of these i my disk gets beaten on for 30 to 40 seconds
at a time...

CK

-- 
Chris Kuethe, GCIA CISSP: Secure Systems Specialist - U of A CNS
      office: 157 General Services Bldg.    +1.780.492.8135
              address@hidden

     GDB has a 'break' feature; why doesn't it have 'fix' too?