My Oracle Support Banner

ODSEE - dsconf Replication Commands Return "Failed to bind to remote" After Expired DefaultCert Was Deleted And Replication Is Broken (Doc ID 2358502.1)

Last updated on FEBRUARY 12, 2018

Applies to:

Oracle Directory Server Enterprise Edition - Version 11.1.1.7.1 and later
Information in this document applies to any platform.

Symptoms

Replication commands using dsconf fail with bind errors.

For example -

root@host1:/shared/certs# dsconf show-repl-agmt-status ou=Unix,o=Enterprise,dc=xxx,dc=com host1.xxx.com:636
Enter "cn=Directory Manager" password:
Unable to bind on "host1.xxx.com:636".

Configuration Status : Unknown
Authentication Status : Unknown
Initialization Status : Unknown

Status : Error Sending Updates
Last Message : Replication error updating replica: Could not bind to replica : transient error - Failed to bind to remote
Pending Changes :

root@host0:/shared/certs# dsconf init-repl-dest ou=Unix,o=Enterprise,dc=xxx,dc=com host1.xxx.com:636
Enter "cn=Directory Manager" password:
Initialization of "host1.xxx.com:636" failed
Server exit code: "900"
Server exit message: "Replication error initializing replica: Total update failed : Unable to bind consumer - Failed to bind to remote"
The "init-repl-dest" operation failed on "localhost:389".



Changes

 The server certificate with the alias defaultCert expired and then was deleted. After the deletion of that server certificate, when running dsconf replication commands, bind errors.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.