OpenDJ : [LDAP: error code 53 – Replication server error]

This topic has 4 replies, 3 voices, and was last updated 3 months, 4 weeks ago by Rob Matthews.

  • Author
    Posts
  • #22488
     srinath.m
    Participant

    Hi All,

    Iam getting the below error on reconciliation from OpenIDM to OpenDJ.

    Here is the error from audit/recon.csv

    Caused by: javax.naming.OperationNotSupportedException: [LDAP: error code 53 – The Replication is configured for suffix dc=test,dc=group but was not able to connect to any Replication Server]; remaining name ‘[email protected],ou=external,ou=users,dc=test,dc=group’
    at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3160)
    at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
    at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840)
    at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:811)
    at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:337)
    at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:266)
    at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:202)
    at org.identityconnectors.ldap.modify.LdapCreate.doCreate(LdapCreate.java:212)
    … 79 more
    “,”default”,”managedUser_sourceLdapopendjAccount”,”Operation CREATE failed with ConnectorException on system object: [email protected],ou=external,ou=users,dc=test,dc=group. Root cause: [LDAP: error code 53 – The Replication is configured for suffix dc=test,dc=group but was not able to connect to any Replication Server]”,”{“”code””:500,””reason””:””Internal Server Error””,””message””:””Operation CREATE failed with ConnectorException on system object: [email protected],ou=external,ou=users,dc=test,dc=group””}”,”ABSENT”,”managed/user/7df2c56e-5a9d-42ad-81bf-5ec9a50e9e5f”,”FAILURE”,”system/LDAPOpenDJ/account/null”,”source”,,,”entry”,”fbd36ba3-d9f7-4b6e-80e9-e7abfb282fa9-3104″

    Here is the error from opendj replication logs

    [10/Jul/2018:16:04:33 +0800] category=SYNC severity=INFORMATION msgID=org.opends.messages.replication.105 msg=Replication server accepted a connection from opendj2.example.com./10.201.16.101:53250 to local address 0.0.0.0/0.0.0.0:8989 but the SSL handshake failed. This is probably benign, but may indicate a transient network outage or a misconfigured client application connecting to this replication server. The error was: Remote host closed connection during handshake

    Env details:
    OpenDJ – 3.0
    OpenIDM – 4.0
    Any help on this would be appreciated.

    Thanks,
    Srinath

    #22514
     Rob Matthews
    Participant

    Hi Srinath,

    By default DJ will not accept writes if it cannot connect to an RS. This is defined in the isolation-policy and is set this way to avoid a replicated environment having data divergence (directory entries being changed on one node and not being replicated or recorded in the local changelog). This suggests that your DJ instance is having issues, are there any errors in your error log relating to the changelog?

    Thanks,
    Rob

    #22546
     srinath.m
    Participant

    Thanks for the quick reply @robert-matthews. I have removed the changelogDb files and restarted both OpenDJ instances. With this the issue is resolved.

    Thanks,
    Srinath

    #27222
     Anonymous
    Inactive

    @srinath-m
    Removing the changelog, is the right way to solve the problem?, we also faced similar issue, and replication status entry level is also not same in one of 3 instances.

    #27228
     Rob Matthews
    Participant

    Only if you are seeing errors relating to reading files in the changelogDB, if your entry count is different on one instance this could be caused by a number of different issues, most commonly that instance was offline for longer than the purge delay so changes are not auto replayed, if that is the case then you can simply initialize from another instance. If the DS is failing to connect to any RS (including its own if it is a DS/RS) then you need to check for errors to see why it isn’t connecting, could it be disk space issues?

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

©2020 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?