[OPENDJ-1052] Exception is logged during dsreplication enable when cn=admin user doesn't exist Created: 04/Jul/13  Updated: 08/Nov/19  Resolved: 07/Mar/16

Status: Done
Project: OpenDJ
Component/s: replication, tools
Affects Version/s: 2.5.0-Xpress1
Fix Version/s: 3.0.0

Type: Bug Priority: Minor
Reporter: Chris Ridd Assignee: Ian Packer [X] (Inactive)
Resolution: Fixed Votes: 0
Labels: release-notes

Issue Links:
Relates
relates to OPENDJ-2436 OpenDJ: Need a command tools switch t... Done
Dev Assignee: Ian Packer [X] (Inactive)

 Description   

The "dsreplication enable" step when adding a new server to an existing topology appears to work correctly, but it will always log an exception to its "details" log:

Jul 04, 2013 9:41:28 AM org.opends.guitools.controlpanel.util.ControlPanelLog initLogFileHandler
INFO: Application launched 04 July 2013 09:41:28 BST
Jul 04, 2013 9:41:30 AM org.opends.admin.ads.TopologyCache joinThreadSet
INFO: Loading ended at 99 ms
Jul 04, 2013 9:41:30 AM org.opends.admin.ads.TopologyCache reloadTopology
INFO: Handling replica with dn: dc=example,dc=com
Jul 04, 2013 9:41:30 AM org.opends.admin.ads.TopologyCache reloadTopology
INFO: Handling replica with dn: dc=example,dc=com
Jul 04, 2013 9:41:30 AM org.opends.admin.ads.util.ServerLoader run
WARNING: Authentication exception: ldaps://rih.local:6444
javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
	at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3087)
	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033)
	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2835)
	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)
	at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
	at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
	at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
	at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
	at javax.naming.InitialContext.init(InitialContext.java:242)
	at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
	at org.opends.admin.ads.util.ConnectionUtils$2.run(ConnectionUtils.java:224)
	at java.lang.Thread.run(Thread.java:724)

Jul 04, 2013 9:41:30 AM org.opends.admin.ads.TopologyCache joinThreadSet
INFO: Loading ended at 51 ms
[etc etc]

The exception is quite harmless: it is only trying to bind as the admin user to the new server before the admin user has been created, and dsreplication just switches to using the appropriate bindDN[12] instead.



 Comments   
Comment by Fabio Pistolesi [ 26/Nov/15 ]

Is this bug still valid after fix for OPENDJ-2467 ?

Comment by Chris Ridd [ 06/Jan/16 ]

Does this still occur after the fix for OPENDJ-1805? It is worth re-testing in DJ 3.0.0.

Comment by Ian Packer [X] (Inactive) [ 07/Mar/16 ]

This exception no longer occurs during normal dsreplication enable commands in 3.0.0, possibly due to OPENDJ-2467.

Furthermore, a successful dsreplication enable command no longer leaves this log file hanging around in the first place (see: OPENDJ-2436)

Therefore I believe this issue can be closed as fixed.

Comment by Matthew Swift [ 07/Nov/19 ]

Moved to closed state because the fixVersion has already been released.

Generated at Tue Nov 24 00:11:58 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.