Results 1 to 9 of 9

Thread: [SOLVED] Messages after upgrade of 4.5.3 for 4.5.4.

  1. #1
    aabreu2005 is offline Active Member
    Join Date
    May 2006
    Location
    Espírito Santo - Brasil
    Posts
    39
    Rep Power
    8

    Default [SOLVED] Messages after upgrade of 4.5.3 for 4.5.4.

    After upgrade of 4.5.3 for 4.5.4., appears the following messages in zimbra.log:

    Mar 29 13:55:41 correio slapd[2032]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
    Mar 29 13:55:41 correio slapd[2032]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)
    Mar 29 13:55:41 correio slapd[2032]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
    Mar 29 13:55:41 correio slapd[2032]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)
    Mar 29 13:55:41 correio slapd[2032]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)
    Mar 29 13:55:41 correio slapd[2032]: is_entry_objectclass("", "2.5.6.1") no objectClass attribute

    happened this in some upgrade, what it can be?


    Ps.: It forgives me, I do not know English, I used a translator…

  2. #2
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    Don't worry-
    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 want to see the slapd errors, you can reset the log
    level to 0.

    zmlocalconfig -e ldap_log_level=0

  3. #3
    aabreu2005 is offline Active Member
    Join Date
    May 2006
    Location
    Espírito Santo - Brasil
    Posts
    39
    Rep Power
    8

    Default

    Quote Originally Posted by jholder View Post
    Don't worry-
    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 want to see the slapd errors, you can reset the log
    level to 0.

    zmlocalconfig -e ldap_log_level=0
    ------------------------------------------------------------
    I executed the command, but it continues the messages…

    Mar 30 10:32:21 correio slapd[2032]: <= bdb_equality_candidates: (zimbraAccountStatus) index_param failed (18)
    Mar 30 10:32:27 correio slapd[2032]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
    Mar 30 10:32:27 correio slapd[2032]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)
    Mar 30 10:32:27 correio slapd[2032]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18)
    Mar 30 10:32:27 correio slapd[2032]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)

    Mar 30 10:32:34 correio slapd[2032]: is_entry_objectclass("", "2.5.6.1") no objectClass attribute

  4. #4
    bobby is offline Zimbra Employee
    Join Date
    Nov 2005
    Posts
    518
    Rep Power
    10

    Default

    you'll also have to restart ldap

    su - zimbra
    ldap stop
    ldap start

  5. #5
    aabreu2005 is offline Active Member
    Join Date
    May 2006
    Location
    Espírito Santo - Brasil
    Posts
    39
    Rep Power
    8

    Thumbs up

    Quote Originally Posted by bobby View Post
    you'll also have to restart ldap

    su - zimbra
    ldap stop
    ldap start
    Decided… I am thankful all

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

    Default index_param failed

    Quote Originally Posted by jholder View Post
    Don't worry-
    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 want to see the slapd errors, you can reset the log
    level to 0.

    zmlocalconfig -e ldap_log_level=0
    I understand that these 'index_param failed' errors are harmless. But is there an option where we _could_ index these fields? I have 35,000 entries in my log related to this error. Is there a cost to indexing these fields? I suspect some of these fields only exist in one or two records, which may make indexes silly. But I see benefit in proactive over reactive ldap logging. (proactive = something bad happened, read logs) (reactive = something bad happened, turn on logging and try to duplicate)


    What level of logging 32768?
    This seems to indicate none (which does not seem to be the case)
    http://www.openldap.org/lists/openld.../msg00026.html

    This post indicates the opposite of none i.e. emergency?
    http://lists.freebsd.org/pipermail/f...ly/034254.html

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

    Default

    Quote Originally Posted by bowergo View Post
    But is there an option where we _could_ index these fields? I have 35,000 entries in my log related to this error. Is there a cost to indexing these fields?
    Under no circumstances should you index these fields. If the messages bother you then just change the logging as mentioned earlier.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #8
    dmg's Avatar
    dmg
    dmg is offline Active Member
    Join Date
    Feb 2007
    Location
    Los Angeles
    Posts
    37
    Rep Power
    8

    Default index_param Errors

    Are the index_param errors anything to be worried about? They seem to happen only when clients login to webmail.

    Code:
    Sep 10 13:28:16 mail slapd[3696]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18) 
    Sep 10 13:28:51 mail slapd[3696]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18) 
    Sep 10 13:28:51 mail slapd[3696]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18) 
    Sep 10 13:28:51 mail slapd[3696]: <= bdb_equality_candidates: (zimbraDomainType) index_param failed (18) 
    Sep 10 13:28:51 mail slapd[3696]: <= bdb_equality_candidates: (zimbraMailStatus) index_param failed (18)

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

    Default

    No, you can ignore them - read jholder's post (2nd in this thread)

    "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)

    -I don't remember, but those might get removed in 4.5.7
    EDIT- there: Bug 18087 - annoying slapd index_param failed errors
    Last edited by mmorse; 09-10-2007 at 02:54 PM.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 13
    Last Post: 05-15-2007, 06:41 AM
  2. IMAP TLS Problems after upgrade to 4.5.3
    By shanson in forum Administrators
    Replies: 4
    Last Post: 03-22-2007, 08:05 AM
  3. 3.0 to 4.5.3 Upgrade failed (mysql error)
    By dealt in forum Installation
    Replies: 35
    Last Post: 03-19-2007, 10:30 PM
  4. upgrade 3.1.4 to 4.5.3
    By ronsterchan in forum Administrators
    Replies: 4
    Last Post: 03-16-2007, 01:24 AM
  5. Spam assassain not traiing properly!
    By Mike T in forum Administrators
    Replies: 1
    Last Post: 10-09-2006, 01:34 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
  •