Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-1052

Exception is logged during dsreplication enable when cn=admin user doesn't exist

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.5.0-Xpress1
    • Fix Version/s: 3.0.0
    • Component/s: replication, tools
    • Labels:
    • Sprint:
      Sprint 1, DJ Sustaining Sprint 15, DJ Sustaining Sprint 18, DJ Sustaining Sprint 19, DJ Sustaining Sprint 20, DJ Sustaining Sprint 21, DJ Sustaining Sprint 21

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ian.packer Ian Packer [X] (Inactive)
                Reporter:
                cjr Chris Ridd
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: