Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3A9BB17F4E for ; Fri, 6 Feb 2015 03:02:35 +0000 (UTC) Received: (qmail 69430 invoked by uid 500); 6 Feb 2015 03:02:35 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 69377 invoked by uid 500); 6 Feb 2015 03:02:35 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 69364 invoked by uid 99); 6 Feb 2015 03:02:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2015 03:02:35 +0000 Date: Fri, 6 Feb 2015 03:02:34 +0000 (UTC) From: "linzhao (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DIRSERVER-2047) Some data can be lost when using ldapadd command to insert data into apacheds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSERVER-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308517#comment-14308517 ] linzhao commented on DIRSERVER-2047: ------------------------------------ Hi Emmanuel, I also used unboundid JDK to do the back and restore function. But I found that sometimes apacheds still doesn't work for this function. My thought is that the mavibot partition "ou=supercluster" I created has some problems. I just want to do the backup and restore work for this partition. But after I create mavibot "ou=supercluster" partition, I can't read the "ou=supercluster" partition from apacheds studio. It shows that Unable to load the configuration ERR_04274 Can't find an OID for the name ads-mavibotPartition. Do you have some documents about how to create the mavibot partition? I will upload my mavibot partition ldif file into this bug, could you help to check it? One thing I want to say is that this bug happened randomly, but it is easily to reproduce. When insert many entries into apacheds at one time, some data can be lost. > Some data can be lost when using ldapadd command to insert data into apacheds > ----------------------------------------------------------------------------- > > Key: DIRSERVER-2047 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2047 > Project: Directory ApacheDS > Issue Type: Bug > Components: ldap > Affects Versions: 2.0.0-M19 > Environment: centOS 6.5 with openldap and apacheds installed > Reporter: linzhao > Priority: Blocker > Labels: LDAP > Fix For: 2.0.0-M20 > > > In our system, we need to do data backup and restore for apacheds. For now, we use the ldapsearch and ldapadd command to do BR function. We use ldapsearch to backup apacheds data to be a ldif file and use ldapadd to restore the data. But when the ldif is a little big, I always found that the data can't be restored successfully, but the ladpadd command showed that the data can be added successfully. No exceptions for ldapadd command. But the restored data didn't exist in the node. This bug only happened when the ldif file is a little big. I mean if the data entry greater than 500 entries. But the node for backup and restore is using mavibot partition. Because I found so many problems for jdbm. So I change it to mavibot partition. Another question is that do you know is there some good way to do the data backup and restore for apacheds? > May be my mavibot partition has some problems, so someone can tell me how to create a mavibot partition in APACHEDS? Because the mavibot parttion I created can't be viewed when click the "Open Configuration" in apacheds studio. Also I used unboundid JDK to insert many entries apacheds and the same problem happened. So someone can tell me how to config the mavibot partition on APACHEDS? That's may be very helpful. > Below is the exceptions from apacheds when problems happened: > [16:21:41] INFO [org.apache.directory.server.ldap.LdapServer] - Ldap service stopped. > [16:21:41] WARN [org.apache.directory.server.core.shared.partition.DefaultPartitionNexus] - Failed to flush partition data out. > org.apache.directory.api.ldap.model.exception.LdapOperationErrorException > at org.apache.directory.server.core.partition.impl.btree.AbstractBTreePartition.saveContextCsn(AbstractBTreePartition.java:3364) > at org.apache.directory.server.core.shared.partition.DefaultPartitionNexus.sync(DefaultPartitionNexus.java:319) > at org.apache.directory.server.core.DefaultDirectoryService.shutdown(DefaultDirectoryService.java:1283) > at org.apache.directory.server.ApacheDsService.stop(ApacheDsService.java:600) > at org.apache.directory.server.wrapper.ApacheDsTanukiWrapper.stop(ApacheDsTanukiWrapper.java:97) > at org.tanukisoftware.wrapper.WrapperManager$13.run(WrapperManager.java:3134) > Caused by: java.lang.NullPointerException > at org.apache.directory.server.core.partition.impl.btree.AbstractBTreePartition.saveContextCsn(AbstractBTreePartition.java:3350) > ... 5 more > [16:21:41] ERROR [org.apache.directory.server.wrapper.ApacheDsTanukiWrapper] - Failed to stop the service. > org.apache.directory.api.util.exception.MultiException: ERR_265 Grouping many exceptions on root nexus sync() > at org.apache.directory.server.core.shared.partition.DefaultPartitionNexus.sync(DefaultPartitionNexus.java:328) > at org.apache.directory.server.core.DefaultDirectoryService.shutdown(DefaultDirectoryService.java:1283) > at org.apache.directory.server.ApacheDsService.stop(ApacheDsService.java:600) > at org.apache.directory.server.wrapper.ApacheDsTanukiWrapper.stop(ApacheDsTanukiWrapper.java:97) > at org.tanukisoftware.wrapper.WrapperManager$13.run(WrapperManager.java:3134) > Nested exceptions to follow: > INFO | jvm 1 | 2015/02/02 17:11:06 | [17:11:06] WARN [org.apache.directory.server.ldap.LdapProtocolHandler] - Unexpected exception forcing session to close: sending disconnect notice to client. > INFO | jvm 1 | 2015/02/02 17:11:06 | java.io.IOException: Connection reset by peer > INFO | jvm 1 | 2015/02/02 17:11:06 | at sun.nio.ch.FileDispatcherImpl.read0(Native Method) > INFO | jvm 1 | 2015/02/02 17:11:06 | at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > INFO | jvm 1 | 2015/02/02 17:11:06 | at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > INFO | jvm 1 | 2015/02/02 17:11:06 | at sun.nio.ch.IOUtil.read(IOUtil.java:197) > INFO | jvm 1 | 2015/02/02 17:11:06 | at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) > INFO | jvm 1 | 2015/02/02 17:11:06 | at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:311) > INFO | jvm 1 | 2015/02/02 17:11:06 | at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:45) > INFO | jvm 1 | 2015/02/02 17:11:06 | at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:694) > INFO | jvm 1 | 2015/02/02 17:11:06 | at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:668) > INFO | jvm 1 | 2015/02/02 17:11:06 | at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:657) > INFO | jvm 1 | 2015/02/02 17:11:06 | at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$600(AbstractPollingIoProcessor.java:67) > INFO | jvm 1 | 2015/02/02 17:11:06 | at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:1121) > INFO | jvm 1 | 2015/02/02 17:11:06 | at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64) > INFO | jvm 1 | 2015/02/02 17:11:06 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > INFO | jvm 1 | 2015/02/02 17:11:06 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > INFO | jvm 1 | 2015/02/02 17:11:06 | at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)