Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: bdb equality error

  1. #1
    jeepville is offline Active Member
    Join Date
    Jul 2007
    Location
    Indiana
    Posts
    45
    Rep Power
    8

    Default bdb equality error

    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

  2. #2
    jeepville is offline Active Member
    Join Date
    Jul 2007
    Location
    Indiana
    Posts
    45
    Rep Power
    8

    Default

    BTT

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

    Any Help?

  3. #3
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,470
    Rep Power
    56

    Default

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


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  4. #4
    jeepville is offline Active Member
    Join Date
    Jul 2007
    Location
    Indiana
    Posts
    45
    Rep Power
    8

    Default

    thanks good to know

  5. #5
    bowergo is offline Senior Member
    Join Date
    Jan 2007
    Location
    Baltimore, Maryland
    Posts
    51
    Rep Power
    8

    Default

    Quote Originally Posted by phoenix View Post
    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

  6. #6
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,470
    Rep Power
    56

    Default

    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.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  7. #7
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    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)

  8. #8
    bowergo is offline Senior Member
    Join Date
    Jan 2007
    Location
    Baltimore, Maryland
    Posts
    51
    Rep Power
    8

    Default

    Quote Originally Posted by mmorse View Post
    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.

  9. #9
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    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
    Last edited by mmorse; 08-10-2007 at 12:49 PM.

  10. #10
    bowergo is offline Senior Member
    Join Date
    Jan 2007
    Location
    Baltimore, Maryland
    Posts
    51
    Rep Power
    8

    Default

    Quote Originally Posted by mmorse View Post
    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?

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 23
    Last Post: 01-24-2013, 03:44 PM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 12:42 AM
  3. M3 problem with shares
    By titangears in forum Users
    Replies: 4
    Last Post: 01-12-2006, 01:01 PM
  4. Replies: 14
    Last Post: 12-22-2005, 04:59 PM
  5. Building native libraries on MacOS X
    By ajmas in forum Developers
    Replies: 3
    Last Post: 10-14-2005, 11:00 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •