sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] unable to allocate memory for mutex; resize mutex region


From: John Clizbe
Subject: Re: [Sks-devel] unable to allocate memory for mutex; resize mutex region [sks ubuntu/oneiric]
Date: Fri, 08 Feb 2013 14:42:44 -0600
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15.2

Moritz Rudert (helios) wrote:
> On 02/21/2012 06:02 PM, H.-Dirk Schmitt wrote:
>> Hello!
>>
>> After upgrading from ubuntu/natty to ubuntu/oneiric sks stop working
>> with the error message
>> "unable to allocate memory for mutex; resize mutex region" in db.log.
>>
>> If someone else runs in this problem below ubuntu - see
>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/937931
>>
>> Best regards,
>>
>> H.-Dirk Schmitt
> I'm getting the same error with sks 1.1.4 on debian squeeze after about
> 12 hours running.
> 
> I've copied DB_CONFIG from sampleConfig to /var/lib/sks/DB/ and
> /var/lib/sks/PTree/ but no change. I've tried sks cleandb, but no change.
> 
> I've no clue what I should do.

Does 'db53_stat -xh PTree' reflect the mutex counts set in DB_CONFIG?

If not, try recreating the DB environment for each DB:

        cd /var/lib/sks
        db53_recover -h DB
        db53_recover -h PTree

That is usually sufficient. It removes the old environment. SKS will recreate
the environment on startup.

I have an option in my sks startup script that runs the following:

    for DB in KDB PTree
        do
        (   db53_recover -h $DB;            \
            db53_checkpoint -1h $DB;        \
            db53_recover -eh $DB    )       &
        done
        wait


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]