OUD Proxy 12c - Error: "The load balancing workflow element has no operational route" is Reported when Attempting to use the "ldapsearch" Command to Search for a User (Doc ID 2711567.1)

Last updated on JUNE 07, 2022

Applies to:

Symptoms

On : 12.2.1.3.200623 version, Proxy & Load-Balancing

When attempting to search for a user, the following error occurs.

$ ldapsearch -h HOSTNAME -p LDAPS_PORT -T --useSSL --trustALL -D cn='DS_ADMIN' -b SUFFIX_DN -j PATH_TO_PWDFILE '(&(objectclass=person)(uid=UID*))' dn

-----------------------
SEARCH operation failed
Result Code: 52 (Unavailable)
Additional Information: The load balancing workflow element has no operational route. This may happen when no route has been configured or all the configured routes are down

The following errors are reported:

/2020:11:28:08 -0400] category=CORE severity=NOTICE msgID=$ID msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887):  The Directory Server has started successfully
[01/Sep/2020:11:28:09 -0400] category=PROXY_LDAP severity=NOTICE msgID=28770308 msg=LDAPserver '$PROXY_1' is down
[01/Sep/2020:11:28:09 -0400] category=CORE severity=NOTICE msgID=$ID msg=The Directory Server has sent an alert notification generated by class com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension (alert type com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension.LDAPServerExtensionDown, alert ID XXXX):  The LDAP server extension $PROXY_1 is down
[01/Sep/2020:11:28:09 -0400] category=PROXY_LDAP severity=NOTICE msgID=28770308 msg=LDAPserver '$PROXY_2' is down
[01/Sep/2020:11:28:09 -0400] category=CORE severity=NOTICE msgID=$ID msg=The Directory Server has sent an alert notification generated by class com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension (alert type com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension.LDAPServerExtensionDown, alert ID XXXX):  The LDAP server extension $PROXY_2 is down
[01/Sep/2020:11:28:10 -0400] category=LOADBALANCING severity=SEVERE_WARNING msgID=$ID msg=The failover load balancing active route for ADD operations is now '$PROXY-WE-1' (was 'NULL')
[01/Sep
[01/Sep/2020:11:28:10 -0400] category=LOADBALANCING severity=SEVERE_WARNING msgID=$ID msg=The failover load balancing active route for MODIFYDN operations is now '$PROXY-WE-1' (was 'NULL')
[01/Sep/2020:11:28:10 -0400] category=CORE severity=NOTICE msgID=$ID msg=The Directory Server has sent an alert notification generated by class com.sun.dps.server.workflowelement.loadbalancing.FailoverLoadBalancingAlgorithm (alert type com.sun.dps.server.FailoverLoadBalancer, alert ID $ID):  The failover load balancing active route for MODIFYDN operations is now '$PROXY-WE-1' (was 'NULL')
[01/Sep/2020:11:28:10 -0400] category=LOADBALANCING severity=SEVERE_WARNING msgID=$ID msg=The failover load balancing active route for SEARCH operations is now '$PROXY-WE-1' (was 'NULL')
[01/Sep/2020:11:28:10 -0400] category=CORE severity=NOTICE msgID=$ID msg=The Directory Server has sent an alert notification generated by class com.sun.dps.server.workflowelement.loadbalancing.FailoverLoadBalancingAlgorithm (alert type com.sun.dps.server.FailoverLoadBalancer, alert ID $ID):  The failover load balancing active route for SEARCH operations is now '$PROXY-WE-1' (was 'NULL')
[01/Sep/2020:11:28:10 -0400] category=PROXY_LDAP severity=NOTICE msgID=$ID msg=Monitoring thread has detected a failure on remote server $PROXY_1
[01/Sep/2020:11:28:10 -0400] category=PROXY_LDAP severity=NOTICE msgID=$ID msg=Monitoring thread has detected a failure on remote server $PROXY_2

Debug logging reports the following errors;

[16/Sep/2020:12:39:19 -0400] 17 caught error thread={LDAP Proxy Monitoring Thread(187)} threadDetail={parentThread=LDAP Request Handler 0 for connection handler LDAP Administration Connector 0.0.0.0 port $ADMIN_PORT(26) isDaemon=false } method={connectToHost(LDAP Connection.java:510)} caught={org.opends.server.tools.ClientException: Cannot send the simple bind request:  SSLHandshakeException(sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target)}
Stack Trace:
  at com.sun.dps.server.workflowelement.proxyldap.LDAPAuthenticationHandler.doSimpleBind(LDAPAuthenticationHandler.java:296)
  at com.sun.dps.server.workflowelement.proxyldap.LDAPConnection.connectToHost(LDAPConnection.java:388)
  at com.sun.dps.server.workflowelement.proxyldap.Connection.connect(Connection.java:189)
  at com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension.createAndConnectDedicatedConnection(LDAPServerExtension.java:1262)
  at com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension.sendPing(LDAPServerExtension.java:1296)
  at com.sun.dps.server.workflowelement.proxyldap.LDAPServerExtension.checkServer(LDAPServerExtension.java:1185)
  at com.sun.dps.server.workflowelement.proxyldap.MonitoringThread.checkServer(MonitoringThread.java:204)
  at com.sun.dps.server.workflowelement.proxyldap.MonitoringThread.run(MonitoringThread.java:145)
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)

Cause

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