Re: [Sks-devel] SKS: Fatal error: exception Keydb.Unsafe.No_db

[Dan Egli]

Olaf Gellert wrote:

> Hi all,
>
> some days ago our recon-server decided to stop working:
>
> 2004-06-16 20:53:45 Added 1 hash-updates. Caught up to 1087412025.024097
> 2004-06-16 20:53:45 Enabling gossip
> 2004-06-16 20:54:14 Raising Sys.Break -- PTree may be corrupted: 
> Failure("remove_from_node: attempt to delete non-existant element from prefix 
> tree")
> 2004-06-16 20:54:14 DB closed
>
> I ran a db_recover over the PTree and the KDB (with
> no errors) and started again, but same result from 
> the recon server.
>
> I rebuilt the ptree (sks pbuild), which did not print
> any error messages. So I tried to restart the sks
> server. Now I get the following:
>
> Fatal error: exception Keydb.Unsafe.No_db
>
> Anyone knows what"s going on? Any other solution than
> rebuilding the key database from a keyring?
>
> Cheers,
>   Olaf
>
>
> P.S.: When I run db_recover now, I get:
>
> db_recover: DB_ENV->log_flush: LSN past current end-of-log
> db_recover: tqueue: unable to flush page: 0
> db_recover: txn_checkpoint: failed to flush the buffer cache Invalid argument
> db_recover: PANIC: Invalid argument
> db_recover: fatal region error detected; run recovery
> db_recover: fatal region error detected; run recovery
> db_recover: fatal region error detected; run recovery
> db_recover: fatal region error detected; run recovery
> db_recover: fatal region error detected; run recovery
> db_recover: fatal region error detected; run recovery
> db_recover: fatal region error detected; run recovery
> db_recover: fatal region error detected; run recovery
> db_recover: fatal region error detected; run recovery
> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery
> db_recover: Database handles open during environment close 
> db_recover: dbenv->close: Invalid argument
welcome to Database Hell. This is one reason I think that future 
versions of sks should not use Sleepycat's DB. It gets corrupted SOO 
EASILY. A MySQL database, for example, would be much nicer, and we 
wouldn't have such an easy time getting corrupted.

As for what to do, I hate to tell you this but when I get things like 
that the only thing I've been able to do is nuke and rebuild the 
database from dump. Not pleasant, and certainly not fast, but effective 
nonetheless.


--
-- Dan