Re: [Sks-devel] Has anyone looked into bdb alternatives?

[Alex Roper]

We're using bdb 4.6.21 on Debian Stable so I doubt it's a software issue. Hardware is 
possible but unlikely, as we're properly raided and lvm-ed.

I'm really not sure what to do here. I suppose I could cronjob a shutdown sks, recover, 
start sks, but this really shouldn't be necessary. I could also try rebuilding the 
database, but I already did that once.

If no one has any other suggestions, I'll cronjob the recovery once per hour. Not ideal 
but I guess it works.

Alex

John Marshall wrote:
> On Sat, 14 Feb 2009, 14:59 -0800, Alex Roper wrote:
> > I've been having terrible corruption issues (need to run reconstruction 
> > every day), as I usually notice with bdb-based applications. I was 
>
> Perhaps the port of BDB to your platform isn't very good; or perhaps
> there's some underlying disc sub-system problem; or perhaps you are
> using an older BDB?
>
> I've only been running SKS for a few weeks but haven't seen any
> corruption issues.  The logs are clean.  I'm running SKS 1.1.0 on BDB
> 4.6.21 on FreeBSD 7.1.
>
> > wondering if anyone has experimented with patching sks to use something 
> > more reliable like mysql, postgres, sqlite, etc?
>
> If the issue is indeed the porting of BDB to your platform, one of these
> might provide a more portable solution for SKS.
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/sks-devel

signature.asc
Description: OpenPGP digital signature