Tagged: 

This topic has 3 replies, 2 voices, and was last updated 5 years, 2 months ago by Ludo.

  • Author
    Posts
  • #14314
     sixart
    Participant

    Hi,
    I have two server and I want enable replication.

    When I try with command
    /opt/opendj/bin/dsreplication enable --adminUID replicationAdmin --adminPassword passwordrep --baseDN dc=example,dc=it --host1 192.168.10.82 --port1 4444 --bindDN1 "cn=Default" --bindPassword1 passwordDefault --replicationPort1 8989 --host2 192.168.10.83 --port2 4444 --bindDN2 "cn=Default" --bindPassword2 passwordDefault --replicationPort2 8989 --trustAll --no-prompt
    I receive this output

    Establishing connections ..... Done.
    Checking registration information ..... Done.
    Configuring Replication port on server 192.168.10.82:4444 ..... Done.
    Configuring Replication port on server 192.168.10.83:4444 ..... Done.
    Updating replication configuration for baseDN dc=example,dc=it
    on server 192.168.10.82:4444 .....Done.
    Updating replication configuration for baseDN dc=example,dc=it
    on server 192.168.10.83:4444 .....Done.
    Updating registration configuration on server 192.168.10.82:4444 ..... Done.
    Updating registration configuration on server 192.168.10.83:4444 ..... Done.
    Updating replication configuration for baseDN cn=schema on server
    192.168.10.82:4444 .....Done.
    Updating replication configuration for baseDN cn=schema on server
    192.168.10.83:4444 .....Done.
    Initializing registration information on server 192.168.10.83:4444 with the
    contents of server 192.168.10.82:4444 .....
    Error during the initialization with contents from server 192.168.10.82:4444.
    Last log details: [16/Nov/2016:09:49:19 +0100] severity="NOTICE" msgCount=0
    msgID=org.opends.messages.backend-413 message="Initialize From Replica task
    quicksetup-initialize5 started execution". Task state: STOPPED_BY_ERROR. Check
    the error logs of 192.168.10.82:4444 for more information.
    See /tmp/opendj-replication-2114984791843994877.log for a detailed log of this
    operation.

    In the /tmp/opendj-replication-2114984791843994877.log there is:

    [16/11/2016:09:48:09 +0100] category=org.opends seq=0 severity=INFO msg=Application launched 16 November 2016 09:48:09 CET
    [16/11/2016:09:48:14 +0100] category=DSCONFIG seq=1 severity=INFO msg=Loading ended at 0 ms
    [16/11/2016:09:48:14 +0100] category=DSCONFIG seq=2 severity=INFO msg=Loading ended at 0 ms
    [16/11/2016:09:48:15 +0100] category=DSCONFIG seq=3 severity=INFO msg=Loading ended at 184 ms
    [16/11/2016:09:48:15 +0100] category=DSCONFIG seq=4 severity=INFO msg=Handling replica with dn: cn=schema
    [16/11/2016:09:48:15 +0100] category=DSCONFIG seq=5 severity=INFO msg=Handling replica with dn: dc=example,dc=it
    [16/11/2016:09:48:15 +0100] category=DSCONFIG seq=6 severity=INFO msg=Handling replica with dn: cn=admin data
    [16/11/2016:09:48:15 +0100] category=DSCONFIG seq=7 severity=INFO msg=Handling replica with dn: cn=admin data
    [16/11/2016:09:48:15 +0100] category=DSCONFIG seq=8 severity=INFO msg=Handling replica with dn: dc=example,dc=it
    [16/11/2016:09:48:15 +0100] category=DSCONFIG seq=9 severity=INFO msg=Handling replica with dn: cn=schema
    [16/11/2016:09:48:15 +0100] category=DSCONFIG seq=10 severity=INFO msg=Loading ended at 0 ms
    [16/11/2016:09:48:31 +0100] category=TOOLS seq=11 severity=INFO msg=Configuring base DN 'dc=example,dc=it' the replication servers are [192.168.10.82:8989, 192.168.10.83:8989]
    [16/11/2016:09:48:36 +0100] category=TOOLS seq=12 severity=INFO msg=Configuring base DN 'dc=example,dc=it' the replication servers are [192.168.10.82:8989, 192.168.10.83:8989]
    [16/11/2016:09:48:51 +0100] category=TOOLS seq=13 severity=INFO msg=Configuring base DN 'cn=admin data' the replication servers are [192.168.10.82:8989, 192.168.10.83:8989]
    [16/11/2016:09:48:56 +0100] category=TOOLS seq=14 severity=INFO msg=Configuring base DN 'cn=admin data' the replication servers are [192.168.10.82:8989, 192.168.10.83:8989]
    [16/11/2016:09:49:14 +0100] category=TOOLS seq=15 severity=INFO msg=Configuring base DN 'cn=schema' the replication servers are [192.168.10.82:8989, 192.168.10.83:8989]
    [16/11/2016:09:49:19 +0100] category=TOOLS seq=16 severity=INFO msg=Configuring base DN 'cn=schema' the replication servers are [192.168.10.82:8989, 192.168.10.83:8989]
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=17 severity=INFO msg=QuickSetup application launched 16 November 2016 09:49:20 CET
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=18 severity=WARNING msg=A task with dn: ds-task-id=quicksetup-initialize1,cn=Scheduled Tasks,cn=Tasks already existed.
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=19 severity=WARNING msg=A task with dn: ds-task-id=quicksetup-initialize2,cn=Scheduled Tasks,cn=Tasks already existed.
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=20 severity=WARNING msg=A task with dn: ds-task-id=quicksetup-initialize3,cn=Scheduled Tasks,cn=Tasks already existed.
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=21 severity=WARNING msg=A task with dn: ds-task-id=quicksetup-initialize4,cn=Scheduled Tasks,cn=Tasks already existed.
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=22 severity=INFO msg=created task entry: {ds-task-initialize-replica-server-id=ds-task-initialize-replica-server-id: 10214, ds-task-initialize-domain-dn=ds-task-initialize-domain-dn: cn=admin data, objectclass=objectclass: top, ds-task, ds-task-initialize-from-remote-replica, ds-task-class-name=ds-task-class-name: org.opends.server.tasks.InitializeTask, ds-task-id=ds-task-id: quicksetup-initialize5}
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=23 severity=INFO msg=[16/Nov/2016:09:49:19 +0100] severity="NOTICE" msgCount=0 msgID=org.opends.messages.backend-413 message="Initialize From Replica task quicksetup-initialize5 started execution"
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=24 severity=INFO msg=Last task entry: : null:null:{ds-task-unprocessed-entry-count=ds-task-unprocessed-entry-count: 0, ds-task-state=ds-task-state: STOPPED_BY_ERROR, ds-task-log-message=ds-task-log-message: [16/Nov/2016:09:49:19 +0100] severity="NOTICE" msgCount=0 msgID=org.opends.messages.backend-413 message="Initialize From Replica task quicksetup-initialize5 started execution", [16/Nov/2016:09:49:20 +0100] severity="ERROR" msgCount=1 msgID=org.opends.messages.replication-174 message="The initialization failed because the domain cn=admin data is not connected to a replication server", [16/Nov/2016:09:49:20 +0100] severity="NOTICE" msgCount=2 msgID=org.opends.messages.backend-414 message="Initialize From Replica task quicksetup-initialize5 finished execution in the state Stopped by error", ds-task-processed-entry-count=ds-task-processed-entry-count: 0}
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=25 severity=WARNING msg=Processed errorMsg: Error during the initialization with contents from server 192.168.10.82:4444. Last log details: [16/Nov/2016:09:49:19 +0100] severity="NOTICE" msgCount=0 msgID=org.opends.messages.backend-413 message="Initialize From Replica task quicksetup-initialize5 started execution". Task state: STOPPED_BY_ERROR. Check the error logs of 192.168.10.82:4444 for more information.
    [16/11/2016:09:49:20 +0100] category=QUICKSETUP seq=26 severity=SEVERE msg=Throwing ApplicationException.
    [16/11/2016:09:49:20 +0100] category=TOOLS seq=27 severity=SEVERE msg=Complete error stack: exception=ReplicationCliException: Error during the initialization with contents from server 192.168.10.82:4444. Last log details: [16/Nov/2016:09:49:19 +0100] severity="NOTICE" msgCount=0 msgID=org.opends.messages.backend-413 message="Initialize From Replica task quicksetup-initialize5 started execution". Task state: STOPPED_BY_ERROR. Check the error logs of 192.168.10.82:4444 for more information. (ReplicationCliMain.java:7185 ReplicationCliMain.java:5478 ReplicationCliMain.java:4019 ReplicationCliMain.java:749 ReplicationCliMain.java:553 ReplicationCliMain.java:496 ReplicationCliMain.java:367 ReplicationCliMain.java:319)

    In the file log I see:

    [16/Nov/2016:09:48:15 +0100] category=SYNC severity=NOTICE msgID=org.opends.messages.replication.204 msg=Replication server RS(210) started listening for new connections on address 0.0.0.0 port 8989
    [16/Nov/2016:09:48:15 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.6 msg=Replication Server failed to start : could not bind to the listen port : 8989. Error : Address already in use
    [16/Nov/2016:09:48:15 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.6 msg=Replication Server failed to start : could not bind to the listen port : 8989. Error : Address already in use
    [16/Nov/2016:09:48:16 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.181 msg=The connection from this replication server RS(210) to replication server RS(7370) at demo1.example.it/192.168.10.83:54941 for domain "dc=example,dc=it" has failed
    [16/Nov/2016:09:48:20 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.212 msg=Directory server DS(25764) timed out while connecting to replication server 192.168.10.82:8989 for domain "dc=example,dc=it"
    [16/Nov/2016:09:48:20 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.23 msg=Directory server DS(25764) was unable to connect to any of the following replication servers for domain "dc=example,dc=it": 210
    [16/Nov/2016:09:48:20 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3424, dn=cn=schema) with ChangeNumber 000001578ac6c8e124c400000001 error Attribute or Value Exists Entry cn=schema cannot be modified because it would have resulted in one or more duplicate values for attribute objectClasses: ( 1.1.2.2.4.1.12345.30 NAME 'testcompany' ...... X-SCHEMA-FILE '99-user.ldif' )
    [16/Nov/2016:09:48:20 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3441, dn=cn=schema) with ChangeNumber 00000157af04c20f24c400000008 error Unwilling to Perform Unable to remove objectclass testperson from the server schema because it is referenced as the superior class for objectclass testperson
    [16/Nov/2016:09:48:20 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3425, dn=cn=schema) with ChangeNumber 000001578ac79dfc7a3900000002 error Attribute or Value Exists Entry cn=schema cannot be modified because it would have resulted in one or more duplicate values for attribute objectClasses: ( 1.1.2.2.4.1.12345.30 NAME 'testcompany' ...... X-SCHEMA-FILE '99-user.ldif' )
    [16/Nov/2016:09:48:20 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3426, dn=cn=schema) with ChangeNumber 00000157af032a0f7a3900000003 error Attribute or Value Exists Entry cn=schema cannot be modified because it would have resulted in one or more duplicate values for attribute attributeTypes: ( 1.1.2.2.4.1.12345.340 NAME 'numbertest'  ...... X-SCHEMA-FILE '99-user.ldif' )
    [16/Nov/2016:09:48:20 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3427, dn=cn=schema) with ChangeNumber 00000157af034abf7a3900000004 error Unwilling to Perform Unable to remove attribute type numbertest from the server schema because it is referenced as a required or optional attribute type in objectclass testperson
    [16/Nov/2016:09:48:20 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3428, dn=cn=schema) with ChangeNumber 00000157af034abf7a3900000005 error Attribute or Value Exists Entry cn=schema cannot be modified because it would have resulted in one or more duplicate values for attribute attributeTypes: ( 1.1.2.2.4.1.12345.340 NAME 'numbertest'  ...... X-APPROX '1.1.2.2.4.1.26027.1.4.1')
    [16/Nov/2016:09:48:21 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3433, dn=cn=schema) with ChangeNumber 00000157af04522724c400000002 error Attribute or Value Exists Entry cn=schema cannot be modified because it would have resulted in one or more duplicate values for attribute attributeTypes: ( 1.1.2.2.4.1.12345.340 NAME 'numbertest'  ...... X-SCHEMA-FILE '99-user.ldif' )
    [16/Nov/2016:09:48:21 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3434, dn=cn=schema) with ChangeNumber 00000157af04730124c400000003 error Unwilling to Perform Unable to remove attribute type numbertest from the server schema because it is referenced as a required or optional attribute type in objectclass testperson
    [16/Nov/2016:09:48:21 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3435, dn=cn=schema) with ChangeNumber 00000157af04730124c400000004 error Attribute or Value Exists Entry cn=schema cannot be modified because it would have resulted in one or more duplicate values for attribute attributeTypes: ( 1.1.2.2.4.1.12345.340 NAME 'numbertest'  ...... X-APPROX '1.1.2.2.4.1.26027.1.4.1')
    [16/Nov/2016:09:48:21 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.9 msg=Internal Error : Operation AddOperation(connID=-1, opID=3458, dn=cn=user1,dc=example,dc=it) change number 000001586c4b40777d4c00000001 was not found in pending list
    [16/Nov/2016:09:48:21 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.9 msg=Internal Error : Operation AddOperation(connID=-1, opID=3461, dn=cn=user2,dc=example,dc=it) change number 000001586c4b88d85c9700000001 was not found in pending list
    [16/Nov/2016:09:48:21 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.9 msg=Internal Error : Operation AddOperation(connID=-1, opID=3464, dn=cn=user3,dc=example,dc=it) change number 000001586c4c32d37d4c00000002 was not found in pending list
    [16/Nov/2016:09:48:21 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.9 msg=Internal Error : Operation AddOperation(connID=-1, opID=3466, dn=cn=user4,dc=example,dc=it) change number 000001586c4c7d0f7d4c00000003 was not found in pending list
    [16/Nov/2016:09:48:21 +0100] category=SYNC severity=ERROR msgID=org.opends.messages.replication.67 msg=Could not replay operation ModifyOperation(connID=-1, opID=3442, dn=cn=schema) with ChangeNumber 00000157af04c20f24c400000009 error Attribute or Value Exists Entry cn=schema cannot be modified because it would have resulted in one or more duplicate values for attribute objectClasses: ( 1.1.2.2.4.1.12345.20 NAME 'testperson' ...)  
    [16/Nov/2016:09:48:25 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.208 msg=Directory server DS(25764) was unable to connect to any replication servers for domain "dc=example,dc=it"
    [16/Nov/2016:09:48:30 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.208 msg=Directory server DS(25764) was unable to connect to any replication servers for domain "dc=example,dc=it"
    [16/Nov/2016:09:48:41 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.208 msg=Directory server DS(10214) was unable to connect to any replication servers for domain "cn=admin data"
    [16/Nov/2016:09:48:46 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.208 msg=Directory server DS(10214) was unable to connect to any replication servers for domain "cn=admin data"
    [16/Nov/2016:09:48:51 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.208 msg=Directory server DS(10214) was unable to connect to any replication servers for domain "cn=admin data"
    [16/Nov/2016:09:49:01 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.208 msg=Directory server DS(11599) was unable to connect to any replication servers for domain "cn=schema"
    [16/Nov/2016:09:49:06 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.208 msg=Directory server DS(11599) was unable to connect to any replication servers for domain "cn=schema"
    [16/Nov/2016:09:49:14 +0100] category=SYNC severity=WARNING msgID=org.opends.messages.replication.208 msg=Directory server DS(11599) was unable to connect to any replication servers for domain "cn=schema"

    How to fix it, and what’s the better way to enable replication??

    Can anyone help me??

    Thanks in advance
    Dario

    #14330
     Ludo
    Moderator

    I think the error is quite explicit:

    Replication Server failed to start : could not bind to the listen port : 8989. Error : Address already in use

    #14331
     sixart
    Participant

    I Ludo,

    but in my server there aren’t connections in 8989 port, I see it with “netstat”.

    #14346
     Ludo
    Moderator

    I understand, but we also use these commands every day for hundreds of tests on various OS and machines (bare metals and VMs).
    There is an error, it’s logged. This is the only evidence we have so far.
    It would be science fiction to try to think of other reasons.

Viewing 4 posts - 1 through 4 (of 4 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?