Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-7633

Upgrade from 3.8.3 to 6.5.3 replication fails with "Cannot change the configuration while a total update is in progress"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Not a defect
    • Affects Version/s: 6.5.3
    • Fix Version/s: Not applicable
    • Component/s: upgrade
    • Labels:
    • Flagged:
      Impediment
    • Story Points:
      0.1

      Description

      We are trying to upgrade our fleet of OpenDJ 3.8.3 servers to 6.5.3. The upgrade itself seems successful, but the data replication is not (the upgrade says it reindexes the data, but after completion, a simple query for a known user returns no matching entries). In attempting to restart replication, we remove the server being upgraded from the config db on another host using ldapmodify, then try to re-configure replication on the host using dsconfig, but that always fails to update one host, which seems to fail the entire operation:

      Error updating replication configuration on base DN cn=admin data of server
      ldap-write-aws-abc123.example.com:4444.
      See /tmp/opendj-replication-6540773237888034430.log for a detailed log of this
      operation.
      Details: org.forgerock.opendj.config.client.OperationRejectedException: The
      operation was rejected for the following reason: Unwilling to Perform: Entry
      cn=cn=admin data,cn=domains,cn=Multimaster Synchronization,cn=Synchronization
      Providers,cn=config cannot be modified because one of the configuration change
      listeners registered for that entry rejected the change: Cannot change the
      configuration while a total update is in progress 

      This has happened each attempt at running the following, regardless what we set host1 to:

      ./dsreplication configure --adminUID "replicationadmin" -j password_file --baseDN dc=example,dc=com --host1 ldap-write-aws-abc123.example.com --port1 4444 --bindDN1 cn=Directory\ Manager --bindPassword1 bind_pass --replicationPort1 8989 --trustAll --no-prompt --secureReplication1 --host2 `hostname -f` --port2 4444 --bindDN2 cn=Directory\ Manager --bindPassword2 bind_pass --noReplicationServer2

      The updates seem to work on the other hosts, its always the same one that fails with the error message.

        Attachments

          Activity

            People

            Assignee:
            lee.trujillo Lee Trujillo
            Reporter:
            mtheral Theral Mackey
            Dev Assignee:
            Lee Trujillo Lee Trujillo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: