is there any way to fix this?

On Fri, Dec 7, 2012 at 9:08 AM, Howard Chu <[email protected]> wrote:

> Pawan Kamboj wrote:
>
>> This error comes frequently when lots of write operation happen on ldap
>> server
>> and at the same time we do the ldapsearch from our application. ldapsearch
>> command say user does not exit in DB but user exit in DB, But after some
>> time
>> it's work well.
>>
>
> You're using an ancient release. You should consider upgrading to 2.4.33,
> and using back-mdb, which is simpler to configure and cannot deadlock.
>
>>
>>
>> On Thu, Dec 6, 2012 at 9:31 PM, Howard Chu <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Pawan Kamboj wrote:
>>
>>         Hi,
>>
>>         We are getting  "bdb_idl_fetch_key: get failed: DB_LOCK_DEADLOCK:
>> Locker
>>         killed to resolve a deadlock (-30995)" error in Openldap debug
>> log. We are
>>         using Openldap.2.3.31 and db.4.5 version and have configured
>>         master-slave. Any
>>         help on this? Is it something need to worry or we can ignore this.
>>         This error
>>         coming frequently when we do lots of write opration on ldap.
>>
>>
>>     It's normal, ignore it.
>>
>>     --
>>        -- Howard Chu
>>        CTO, Symas Corp. http://www.symas.com
>>        Director, Highland Sun http://highlandsun.com/hyc/
>>        Chief Architect, OpenLDAP 
>> http://www.openldap.org/__**project/<http://www.openldap.org/__project/>
>>
>>     <http://www.openldap.org/**project/<http://www.openldap.org/project/>
>> >
>>
>>
>>
>>
>> --
>> Thanks & Regards
>> Pawan Kamboj
>> Infra Analyst, Sapient
>>
>>
>>
>
> --
>   -- Howard Chu
>   CTO, Symas Corp.           http://www.symas.com
>   Director, Highland Sun     http://highlandsun.com/hyc/
>   Chief Architect, OpenLDAP  
> http://www.openldap.org/**project/<http://www.openldap.org/project/>
>



-- 



Thanks & Regards
Pawan Kamboj
Infra Analyst, Sapient

Reply via email to