Re: [Sks-devel] sks recon DB corrupted

[Scott Grayban]

BTW google shows a lot of links about the error.

"unable to allocate memory for mutex; resize mutex region"

You could always try a reboot as well... there might be something stuck
in ram thats eating your memory up.

Regards,
Scott Grayban

 /"\
 \ /     ASCII RIBBON
  X        FIGHT BREAST CANCER
 / \


Scott Grayban said the following on 05/30/2011 06:54 AM:
> The error message suggests you may need to increase the number of
> mutexes. To resize the mutex region:
>
> http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/mutex_set_max.html
>
> Regards,
> Scott Grayban
>
>  /"\
>  \ /     ASCII RIBBON
>   X        FIGHT BREAST CANCER
>  / \
>
>
> Christoph Anton Mitterer said the following on 05/30/2011 05:55 AM:
>   
>> Hi.
>>
>> Since some days my recon DB seems DB be corrupted. recon.log gives the
>> following message.
>> ...
>> 2011-05-25 13:51:30 address for alpha.keyserver.ws:11370 changed from []
>> to [<ADDR_INET [64.70.19.33]:11370>]
>> 2011-05-25 13:51:41 <reconciliation handler> error in callback.:
>> Bdb.DBError("unable to allocate memory for mutex; resize mutex region")
>>
>> Afterwards the process stays in uninterruptable state forever (until I
>> kill it).
>>
>> Using the Debian package from sid (1.1.1+dpkgv3-6.1).
>>
>>
>> Any ideas, or do I have to recreate everything from scratch?
>>
>>
>> Cheers,
>> Chris.
>>   
>>
>>
>> _______________________________________________
>> Sks-devel mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/sks-devel
>>   
>>