Hi,
it's not a real fix and it might be annoying, but one possibility
would be to simply re-build everything from a keydump again. Maybe
something has actually been corrupted in your key database; it might
actually be a faster solution to re-build everything instead of
spending hours on troubleshooting. I personally would do that, I
think, but that's just my personal opinion. :-/
Best regards,
Tobias Frei
Am 24.02.2014 11:49, schrieb Ronny Wagner:
> Dear Community,
>
> i upgrade my two sks server from squeeze to wheezy with sks 1.1.4
> (wheezy backport).
>
> After the update, I become following failed message: Requesting 2
> missing keys from <ADDR_INET [80.101.216.220]:11371>, starting with
> 61AA86A0328D7DF39FC96E13B0A18B83 1 keys received Ctrl-C. Exiting
> eventloop Raising Sys.Break -- PTree may be corrupted:
> Bdb.DBError("unable to allocate memory for mutex; resize mutex
> region") <get_missing_keys.catchup> callback interrupted by break.
>
> I found this entry
> http://lists.nongnu.org/archive/html/sks-devel/2012-07/msg00107.html
> an recover my database, but the fail is come again.
>
> Have anybody a idea?
>
> ii sks 1.1.4-2.1 i386
> Synchronizing OpenPGP Key Server ii db4.8-util
> 4.8.30-12 i386 Berkeley v4.8 Database Utilities ii
> libdb4.6 4.6.21-16 i386
> Berkeley v4.6 Database Libraries [runtime] ii libdb4.7
> 4.7.25-9 i386 Berkeley v4.7 Database Libraries [runtime]
>
>
>
> _______________________________________________ Sks-devel mailing
> list Sks-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/sks-devel
>
_______________________________________________
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel
