Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3549

Unable to start slave mode after authentication failure on a previous startSlave attempt

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.4.1.3, 10.5.1.1
    • 10.4.1.3, 10.5.1.1
    • Replication
    • None

    Description

      Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
      saying that the database has already been booted

      vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
      ij version 10.5
      ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
      ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
      ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
      ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
      ij>

      Attachments

        1. derby-3549-1b.stat
          0.2 kB
          Jorgen Loland
        2. derby-3549-1b.diff
          5 kB
          Jorgen Loland
        3. derby-3549-1a.diff
          1 kB
          Jorgen Loland
        4. derby-3549-1a.stat
          0.1 kB
          Jorgen Loland

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jorgenlo Jorgen Loland
            narayanan V.Narayanan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment