[SOLVED] slapd errors after upgrade from 4.5.3 to 4.5.4

I'm getting a ton of:

Mar 29 20:02:50 infinity slapd[3785]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)\n
Mar 29 20:02:50 infinity slapd[3785]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)\n
Mar 29 20:02:50 infinity slapd[3785]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)\n
Mar 29 20:02:50 infinity slapd[3785]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)\n
Mar 29 20:02:50 infinity slapd[3785]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)\n
Mar 29 20:02:50 infinity slapd[3785]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)\n
Mar 29 20:02:50 infinity slapd[3785]: is_entry_objectclass("", "2.5.6.1") no objectClass attribute\n

in /var/log/zimbra.log after upgrading from 4.5.3 to 4.5.4.

There were no errors that I saw during the upgrade. Perhaps it went bad? Any thoughts?

I stopped ldap, ran "/opt/zimbra/openldap/sbin/slapindex -f /opt/zimbra/conf/slapd.conf", started ldap and the problem still exists.

No worries:

We previously had slapd logging set to 0 (no logs), we increased to
log just errors. These particular errors just indicated that there
are no indexes for these items, which is harmless.

If you do not care about the slapd errors, you can reset the log
level to 0.

zmlocalconfig -e ldap_log_level=0

I know the logging level changed... it just looked like a "problem" from the logs.. hence, "failed" :-) and being there are 5 lines for every email that come in.

But knowing they are harmless, that makes me happy. Thanks for the follow up. I'm only a consumer running it on my personal domains, so I'm only using the OSS edition, but I absolutely love it and the support in the forums is excellent. Much appreciated as always.

Don't thank me, thank Brian :) :)

Your welcome.

-john