Dear list,
what does this error mean ?
------------------------------------ bdb_index_read: failed (-30989) -----------------------------------------
and how can I fix it ?
here is the index portion of my slapd.conf
-------------------------------------------------- # Indices to maintain index objectClass eq index accountActive,virtualDomain eq index mail eq ------------------------------------------------------
thanks
On 6/17/07, JOYDEEP j.bakshi@unlimitedmail.org wrote:
Dear list,
what does this error mean ?
bdb_index_read: failed (-30989)
and how can I fix it ?
here is the index portion of my slapd.conf
# Indices to maintain index objectClass eq index accountActive,virtualDomain eq index mail eq
It looks like your index might be corrupt. When you search for something that isn't indexed but you get a message more like this: <= bdb_equality_candidates: (myAttrib) index_param failed (18).
Whereas your message (bdb_index_read: failed (-30989)) seems to be more related to sleepycat not being able to read the index, not a specific attribute. :)
Check the actual index files to make sure they're correct permissions, etc, and then try a db_recover. (although you may need to go to more extreme means like slapcat/slapadd or rm/slapindex).
matthew sporleder wrote:
On 6/17/07, JOYDEEP j.bakshi@unlimitedmail.org wrote:
Dear list,
what does this error mean ?
bdb_index_read: failed (-30989)
and how can I fix it ?
here is the index portion of my slapd.conf
# Indices to maintain index objectClass eq index accountActive,virtualDomain eq index mail eq
It looks like your index might be corrupt. When you search for something that isn't indexed but you get a message more like this: <= bdb_equality_candidates: (myAttrib) index_param failed (18).
Whereas your message (bdb_index_read: failed (-30989)) seems to be more related to sleepycat not being able to read the index, not a specific attribute. :)
Check the actual index files to make sure they're correct permissions, etc, and then try a db_recover. (although you may need to go to more extreme means like slapcat/slapadd or rm/slapindex).
Thanks a lot. I'll follow ur guide. thanks once more.
On 6/18/07, JOYDEEP j.bakshi@unlimitedmail.org wrote:
matthew sporleder wrote:
On 6/17/07, JOYDEEP j.bakshi@unlimitedmail.org wrote:
Dear list,
what does this error mean ?
bdb_index_read: failed (-30989)
and how can I fix it ?
here is the index portion of my slapd.conf
# Indices to maintain index objectClass eq index accountActive,virtualDomain eq index mail eq
It looks like your index might be corrupt. When you search for something that isn't indexed but you get a message more like this: <= bdb_equality_candidates: (myAttrib) index_param failed (18).
Whereas your message (bdb_index_read: failed (-30989)) seems to be more related to sleepycat not being able to read the index, not a specific attribute. :)
Check the actual index files to make sure they're correct permissions, etc, and then try a db_recover. (although you may need to go to more extreme means like slapcat/slapadd or rm/slapindex).
Thanks a lot. I'll follow ur guide. thanks once more.
While my answer was based on my own logs and some older posts to this mailing list, it appears that Howard Chu has more definitive ideas (as per usual) if you can post your versions of bdb and openldap.
matthew sporleder wrote:
On 6/17/07, JOYDEEP j.bakshi@unlimitedmail.org wrote:
Dear list,
what does this error mean ?
bdb_index_read: failed (-30989)
and how can I fix it ?
here is the index portion of my slapd.conf
# Indices to maintain index objectClass eq index accountActive,virtualDomain eq index mail eq
It looks like your index might be corrupt. When you search for something that isn't indexed but you get a message more like this: <= bdb_equality_candidates: (myAttrib) index_param failed (18).
Whereas your message (bdb_index_read: failed (-30989)) seems to be more related to sleepycat not being able to read the index, not a specific attribute. :)
No. Depending on the version of BerkeleyDB being used, this could be a DB_NOTFOUND result (which just means the data being queried for doesn't exist) or a DB_OLDVERSION result (which means the DB file was created by an older version of BDB). Since the original poster didn't provide a BerkeleyDB version number, it's impossible to tell what the actual problem is.
Don't just throw out random guesses when you don't have enough information to answer a question. Ask more questions and get the necessary info.
openldap-software@openldap.org