Rebuild indexes in OpenDJ 3.0 is failing.

Tagged: 

This topic has 7 replies, 6 voices, and was last updated 5 years, 11 months ago by Bill Nelson.

  • Author
    Posts
  • #10194
     barandeepsingh
    Participant

    Hello,

    Under transformation of ODSEE indexes to OpenDJ, we are required to rebuild indexes which we have recreated to be imported in OpenDJ. During rebuilding, we are facing following issues. Can you please help in fixing this issue?

    Rebuild Index task 20160503092623007 scheduled to start immediately
    [03/May/2016:09:26:22 +0200] severity=”NOTICE” msgCount=0 msgID=org.opends.messages.backend-413 message=”Rebuild Index task 20160503092623007 started execution”
    [03/May/2016:09:26:22 +0200] severity=”NOTICE” msgCount=1 msgID=org.opends.messages.backend-370 message=”The backend userRoot is now taken offline”
    [03/May/2016:09:26:23 +0200] severity=”ERROR” msgCount=2 msgID=org.opends.messages.config-646 message=”org.opends.server.admin.server.ConfigChangeListenerAdaptor$1.applyConfigurationChange failed for entry ds-cfg-backend-id=userRoot,cn=Backends,cn=config: result code=Other, admin action required=false, messages=”NullPointerException (JEStorage.java:821 JEStorage.java:797 TracedStorage.java:547 AttributeIndex.java:819 AttributeIndex.java:74 ServerManagedObjectChangeListenerAdaptor.java:66 ConfigChangeListenerAdaptor.java:327 ConfigChangeListenerAdaptor.java:240 ConfigFileHandler.java:1211 LocalBackendModifyOperation.java:501 LocalBackendModifyOperation.java:287 LocalBackendWorkflowElement.java:745 LocalBackendWorkflowElement.java:1024 LocalBackendWorkflowElement.java:895 ModifyOperationBasis.java:354 InternalClientConnection.java:1573 InternalClientConnection.java:1544 TaskUtils.java:288 RebuildTask.java:202 Task.java:974 TaskThread.java:189)””
    [03/May/2016:09:26:23 +0200] severity=”ERROR” msgCount=3 msgID=org.opends.messages.task-2 message=”The task could not disable a backend: ds-cfg-backend-id=userRoot,cn=Backends,cn=config”
    [03/May/2016:09:26:23 +0200] severity=”NOTICE” msgCount=4 msgID=org.opends.messages.backend-414 message=”Rebuild Index task 20160503092623007 finished execution in the state Stopped by error”
    Rebuild Index task 20160503092623007 did not complete successfully.

    Regards,
    -Manisha

    #10196
     Ludo
    Moderator

    Could you provide some details on the settings of your server and the rebuild-index command that you’ve run ?
    Without further information, it’s almost impossible to troubleshoot such issues.

    #10197
     JnRouvignac
    Participant

    Hi Manisha,

    Weird.
    What EXACT steps are you taking to get there?

    Cheers,
    Jean-Noel

    #10200
     barandeepsingh
    Participant

    Hello all,

    Thanks for replying back.
    The command we are using is as belows:
    ./rebuild-index -h localhost -p 636 –bindDN “cn=Directory Manager” –baseDN “o=xxxxxxx” –rebuildAll

    During transformation, we imported Schema, followed by Data dump and then imported recreated indexes. After server restart, restart box started complaining about indexes, hence we rebuild using above command.

    I am not sure if the sequence is what i need to work upon?
    Regards,
    -Manisha

    #10201
     Ludo
    Moderator

    Hi,
    Thanks. That command is probably the last one you’ve executed. But we need more data to understand what happened and try to reproduce.

    Can you provide the extract of the logs, that show which indexes the server complained about ?
    Can you provide more information about the indexes that you have recreated ? Did you use dsconfig to create them ?

    #10514
     marccbr
    Participant

    Here is the build command I use;
    bin/rebuild-index –port 4444 –hostname opendj.example.com \
    –bindDN “cn=Directory Manager” –bindPassword ???????? \
    –baseDN dc=opendj,dc=example,dc=com –rebuildAll \
    –start 0

    #13311

    I think you cannot rebuild all indexes. There are some indexes that needs to be excluded from rebuilding e.g. dn2id, id2childrencount.

    #13622
     Bill Nelson
    Participant

    You can definitely rebuild all indexes. Here is a copy of script that I wrote as part of an autodeployment process (I have stripped out non-relevant items). This works fine. If you don’t want to rebuild all indexes, simply change the “–rebuildAll” with “–index cn” (where “cn” is the name of the index you would like to rebuild).

    #!/bin/bash
    BINDIR="/opt/forgerock/opendj-user/bin"
    BASEDN="dc=example,dc=com"
    ADMINHOST="localhost"
    ADMINPORT="4444"
    ADMINUSER="cn=Directory Manager"
    ADMINPASS="SuperSecretPassword"
    
    echo "Rebuilding ALL Indexes..."
    $BINDIR/rebuild-index --port $ADMINPORT --hostname $ADMINHOST --bindDN "$ADMINUSER" --bindPassword $ADMINPASS --baseDN $BASEDN --rebuildAll --start 0 --trustAll
Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?