Re: syncrepl_message_to_op

[Quanah Gibson-Mount <quanah@zimbra.com>]

--On December 12, 2007 10:35:57 PM -0800 Digant C Kasundra 
<digant@stanford.edu> wrote:

> I noticed this in my logs when replication failed.  Besides increasing
> the number of locks, is there something larger that is going on that
> might be causing a problem?
>
> Dec 12 15:06:01 ldap4 slapd[14212]: bdb(dc=stanford,dc=edu): Lock table
> is out of available locks
> Dec 12 15:06:01 ldap4 slapd[14212]: => bdb_idl_delete_key: c_get id
> failed: Cannot allocate memory (12)
> Dec 12 15:06:01 ldap4 slapd[14212]: Attribute index delete failure
> Dec 12 15:06:01 ldap4 slapd[14212]: null_callback: error code 0x50
> Dec 12 15:06:01 ldap4 slapd[14212]: syncrepl_message_to_op: rid 000
> be_modify suRegID=xxxx,cn=People,dc=Stanford,dc=edu (80)


Did you look at the data from the db_stat command to see what your 
lock/locker objects/locker usage is?  Increasing the locks is pointless if 
you aren't running out of them. :)

--Quanah


--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration