This topic contains 21 replies, has 3 voices, and was last updated by  Ludo 10 minutes ago.

  • Author
    Posts
  • #23181
     Rob Matthews 
    Participant

    There isn’t a way to force it to re increment. You’ve tried one of the possible “fixes” to get it running again which hasn’t worked. Do the most recent changenumbers match on each instance? You could try using the dsreplication reset-change-number command to sync the changenumber from one instance to the other, although to be honest I would expect that is more a fix for if one of the instances has stopped incrementing, not both.

    The other fix I have seen used is to disable replication, remove the contents of the changelogDB directory on both instances and then re-enable replication and re-initialize. This will recreate the changelog directories on both instances, the only concern here is if you have either, changes that have not been replayed to the other instance (your dsrep status shows the same entry count so this is probably ok) or if you have another application that uses the DJ changelog to update itself (IDM for example).

    #23183
     user1234 
    Participant

    Hi,
    I use OpenIDM to send info of a user from OpenIDM to OpenDJ. I try to do that:
    The other fix I have seen used is to disable replication, remove the contents of the changelogDB directory
    and changeNumber starts running but replication not work again, I modify an user and in the other server not been modified and changenNumber neither update. Any other options or commands to work replication again?
    Thaks a lot!!!

    #23211
     Rob Matthews 
    Participant

    Did you reinitialize replication after you re-enabled it? Do you see any errors in your replication logs?

    #23224
     user1234 
    Participant

    Coult It be because exists a little data and schema differences between nodes?
    Thanks.

    #23237
     Ludo 
    Moderator

    Hi,
    Troubleshooting this kind of errors without proper data is almost impossible.
    We’ve given ideas on what to look for, alternatives to recover and resume the service.
    You’re not even sure of the version, you are using (you can run start-ds -V, and send the output).

    If you are a ForgeRock customer, please raise a support ticket.
    If you’re not, you will need to provide more data including the configuration of your servers, the content of the admin-backend.ldif, and the log files (under /logs).

    Kind regards,
    Ludo

    #23257
     user1234 
    Participant

    But I realize that I have diferences in data and schema between nodes. Could it be why it can not replicate nodes?
    Thanks.

    #23261
     Ludo 
    Moderator

    Replication is about making sure data and schema are identical across nodes. There is a mandatory initialisation phase, and then things will be kept synchronised.
    If the server cannot replicate due to these differences, there will be explicit error messages at the start of the replication service (at server startup).

Viewing 7 posts - 16 through 22 (of 22 total)

You must be logged in to reply to this topic.

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