bdb equality error

[jeepville]

Anyone know what causes this error and how to fix it?

Aug 7 14:02:44 mail slapd[23258]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)
Aug 7 14:02:44 mail slapd[23258]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
Aug 7 14:02:44 mail slapd[23258]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)
Aug 7 14:02:44 mail slapd[23258]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
Aug 7 14:02:44 mail slapd[23258]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)


I have the error quite a lot in my /var/log/zimbra.log

[jeepville]

BTT

It looks like I get it everytime the server receives a message.

Any Help?

[phoenix]

It's a warning message and it will go in your next upgrade, it's harmless and you can ignore it.

[jeepville]

thanks good to know

[bowergo]

It's a warning message and it will go in your next upgrade, it's harmless and you can ignore it.

What is the eta for 4.5.7?

This error is causing a very large number of writes to disk that I could do without. I prefer to keep log detail so I have been ignoring the errors.

Lots and lots, definitely lots and lots.
zgrep -c 'bdb_equality_candidates' zimbra.log.*
zimbra.log.1.gz:1260349
zimbra.log.2.gz:1268238
zimbra.log.3.gz:1179590

[phoenix]

I can't give you a date for 4.5.7 yet. If the error message is causing you a problem you could always set the log level to zero, search the forums for details.

[mmorse]

To further explain what Bill meant/how to do it:

Slapd logging was previously set to 0 (no logs), this has been increased to log just errors. These particular messages just indicated that there are no indexes for these items, which is harmless.

If you do not want to see the slapd errors, you can reset the log level to 0.
zmlocalconfig -e ldap_log_level=0
ldap restart (or full zmcontrol stop/start)

[bowergo]

To further explain what Bill meant/how to do it:

Slapd logging was previously set to 0 (no logs), this has been increased to log just errors. These particular messages just indicated that there are no indexes for these items, which is harmless.

If you do not want to see the slapd errors, you can reset the log level to 0.
zmlocalconfig -e ldap_log_level=0
ldap restart (or full zmcontrol stop/start)

Thanks for adding the detailed steps to the thread.

In my case performance is still high and so is fear of missing an ldap error of importance. ldap touches everything in zimbra, re-creating the error is a far second to finding it in your logs.

I have elected to ignore the noise.

[mmorse]

yup-and those warnings will probably be removed in 4.5.7 (i don't remember where the bug is) - speaking of which...don't forget about upgrading to 4.5.6

[bowergo]

yup-and those warnings will probably be removed in 4.5.7 (i don't remember where the bug is) - speaking of which...don't forget about upgrading to 4.5.6

Aww do I havta

I have been a little nervous about this upgrade, first one with multiple systems.

ldap master first, then mailstores then others.

Leave everything running still? or Do I zmcontrol stop the servers?