Re: [Sks-devel] database corruption

[Yaron Minsky]

SKS is not set-up for multi-process access to the database, and trying
to do so will lead to corruption.  sksdump does just that, and so you
should shutdown your SKS processes before trying to run it.

The proper usage is "sks dump #keys_per_file directory_to_create_dump_in"

y


On Mon, 13 Sep 2004 00:41:16 +0200, Robert Urban <address@hidden> wrote:
> 
> after I had gotten "sks" compiled, I started it in the background
> using "sks build" and then "sks db &".
> 
> I put a single key into the db using "gpg --send-keys".
> 
> I tried various combinations of "sks dump" (documentation?):
> 
> sks dump /tmp key
> sks dump 1 /tmp key
> sks dump all /tmp key
> sks dump 0 /tmp key
> 
> That last one "dump 0 ..." is interesting: sks goes into an infinite
> loop writing zero-length files.
> 
> Later on I noticed that I was unable to retrieve a key using "gpg".  When
> I looked in the log I found the following error:
> 
> 2004-09-12 23:49:27 <mail transmit keys> error in callback.:
> Bdb.DBError("fatal
> region error detected; run recovery")
> 
> After running the berkeley-db program "db_recover" blindly (documentation?)
> in the sks-db directory, and restarting sks, sks seemed happy again.
> 
> This can be reproduced anytime simply by running:
> 
>         sks dump 0 /tmp key
> 
> Can it be true?
> 
> cheers,
> 
> Robert Urban
> 
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/sks-devel
>