[
https://issues.apache.org/jira/browse/DIRSERVER-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021208#comment-16021208
]
Emmanuel Lecharny commented on DIRSERVER-2192:
----------------------------------------------
1) No, we don't have such a procedure
2) This is not the rootDSE. You need to do a search on "", (objectClass=*),
scope = BASE to get it
3) We don't have a solution for M21, this is why we released M23. And even for
M23, the repair may fail... You really need to backup your data regularly.
4) We don't have a clear explanation about why we do have corruptions, but we
know we have some. We have added some locks all over the server to limit such
corruptions, but still it happens from time to time. IMHO, this is really a bug
in teh JDBM library we are using, and this is the reason we are working on
switching to something we know will be reliable...
> apcheds M23 - ERR_554 AND ERR_562
> ---------------------------------
>
> Key: DIRSERVER-2192
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2192
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: sasha
> Priority: Critical
>
> once a week im getting this errors , the only solution is to restart apacheds
> ,
> how can i fix it?
> Unexpected exception forcing session to close: sending disconnect notice to
> client.
> java.lang.Error: ERR_554 double get for block 11,085
> at jdbm.recman.RecordFile.get(RecordFile.java:185)
> at
> jdbm.recman.PhysicalRowIdManager.allocNew(PhysicalRowIdManager.java:202)
> at
> jdbm.recman.PhysicalRowIdManager.alloc(PhysicalRowIdManager.java:177)
> at
> jdbm.recman.PhysicalRowIdManager.update(PhysicalRowIdManager.java:101)
> at jdbm.recman.BaseRecordManager.update(BaseRecordManager.java:281)
> at
> jdbm.recman.CacheRecordManager.updateCacheEntries(CacheRecordManager.java:417)
> at jdbm.recman.CacheRecordManager.commit(CacheRecordManager.java:349)
> at
> org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.sync(JdbmTable.java:976)
> at
> org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmPartition.sync(JdbmPartition.java:577)
> at
> org.apache.directory.server.core.partition.impl.btree.AbstractBTreePartition.add(AbstractBTreePartition.java:871)
> at
> org.apache.directory.server.core.shared.partition.DefaultPartitionNexus.add(DefaultPartitionNexus.java:361)
> at
> org.apache.directory.server.core.api.interceptor.BaseInterceptor$1.add(BaseInterceptor.java:107)
>
>
>
>
>
>
>
>
>
>
> [03:28:29] WARN
> [org.apache.directory.server.ldap.LdapProtocolHandler] - Unexpected exception
> forcing session to close: sending disconnect notice to client.
> java.lang.Error: ERR_562 Offset too large for record header (11,085:30,012)
> at jdbm.recman.RecordHeader.<init>(RecordHeader.java:83)
> at
> jdbm.recman.PhysicalRowIdManager.allocNew(PhysicalRowIdManager.java:224)
> at
> jdbm.recman.PhysicalRowIdManager.alloc(PhysicalRowIdManager.java:177)
> at
> jdbm.recman.PhysicalRowIdManager.update(PhysicalRowIdManager.java:101)
> at jdbm.recman.BaseRecordManager.update(BaseRecordManager.java:281)
> at
> jdbm.recman.CacheRecordManager.updateCacheEntries(CacheRecordManager.java:417)
> at jdbm.recman.CacheRecordManager.commit(CacheRecordManager.java:349)
> at
> org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmTable.sync(JdbmTable.java:976)
> at
> org.apache.directory.server.core.partition.impl.btree.jdbm.JdbmPartition.sync(JdbmPartition.java:577)
> at
> org.apache.directory.server.core.partition.impl.btree.AbstractBTreePartition.add(AbstractBTreePartition.java:871)
> at
> org.apache.directory.server.core.shared.partition.DefaultPartitionNexus.add(DefaultPartitionNexus.java:361)
> at
> org.apache.directory.server.core.api.interceptor.BaseInterceptor$1.add(BaseInterceptor.java:107)
> at
> org.apache.directory.server.core.api.interceptor.BaseInterceptor.next(BaseInterceptor.java:341)
> at
> org.apache.directory.server.core.journal.JournalInterceptor.add(JournalInterceptor.java:139)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
