[389-users] Re: One way supplier replication is failing on newly installed instance

2024-04-18 Thread tdarby
Thanks for the help! On the new server, there is nothing related in the errors log. In the access log, I see the successful binds from the old server: [18/Apr/2024:16:10:22.457956096 +] conn=182814 op=0 BIND dn="cn=eds2.iam.arizona.edu:389,ou=Services,dc=eds,dc=arizona,dc=edu" method=128 v

[389-users] Re: One way supplier replication is failing on newly installed instance

2024-04-18 Thread Marc Sauton
try to review the access log for connection events related to those from the errors log file mentioned earlier, and also verify on the remote replica, the errors and access log events corresponding to this connection, as well as file descriptors and LDAP thread use, run some netstat and dsconf mon

[389-users] Re: One way supplier replication is failing on newly installed instance

2024-04-18 Thread tdarby
Just to add: - I can manually make a connection from the old to new using the replication account and password, so connectivity is fine. - The old server is in 2-way replication with another server of the same version and that is all working perfectly. --

[389-users] One way supplier replication is failing on newly installed instance

2024-04-18 Thread tdarby
I'm trying to get one-way replication going between a very old (1.3.7.8) server and a newly built (2.5.0 B2024.017.) server. - The initial one-way full replication works. - Incremental updates from the old to the new work for a time and then start failing with these messages logged on the ol