Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-48427

Error creating link: Internal Server Error 500

    XMLWordPrintable

Details

    • 1
    • Yes
    • CX Sprint 263

    Attachments

      Issue Links

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          The issue here is that the link servlet is being called from the UI which uses cb-on-behalf-of for authorization rather than an explicit user/pass. Since the UI is being accessed from non-CC node, the request needs to be proxied to the CC and therefore we ask cbauth for the credentials to use to access the CC. However, we are providing a wrong IP address to cbauth which results in:

          org.apache.hyracks.api.exceptions.HyracksDataException: Unable to find given hostport in cbauth database: `ec2-52-25-209-2.us-west-2.compute.amazonaws.com:9111'
          

          As a workaround do one of the following:
          1. Use the UI from the Analytics CC node (ec2-44-234-226-44.us-west-2.compute.amazonaws.com).
          2. Call the Analytics Link API directly (e.g. using curl) and provide username/password.

          murtadha.hubail Murtadha Hubail added a comment - The issue here is that the link servlet is being called from the UI which uses cb-on-behalf-of for authorization rather than an explicit user/pass. Since the UI is being accessed from non-CC node, the request needs to be proxied to the CC and therefore we ask cbauth for the credentials to use to access the CC. However, we are providing a wrong IP address to cbauth which results in: org.apache.hyracks.api.exceptions.HyracksDataException: Unable to find given hostport in cbauth database: `ec2-52-25-209-2.us-west-2.compute.amazonaws.com:9111' As a workaround do one of the following: 1. Use the UI from the Analytics CC node (ec2-44-234-226-44.us-west-2.compute.amazonaws.com). 2. Call the Analytics Link API directly (e.g. using curl) and provide username/password.

          Umang,
          The verification steps for this issue are the same as MB-45905. Please make sure that you use nodes with different IP addresses. Maybe that's why this issue wasn't caught during the last verification.

          murtadha.hubail Murtadha Hubail added a comment - Umang , The verification steps for this issue are the same as MB-45905 . Please make sure that you use nodes with different IP addresses. Maybe that's why this issue wasn't caught during the last verification.

          Build couchbase-server-7.0.2-6678 contains cbas-core commit b6b6c9b with commit message:
          MB-48427: Fix CC proxy address

          build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.2-6678 contains cbas-core commit b6b6c9b with commit message: MB-48427 : Fix CC proxy address

          Build couchbase-server-7.1.0-1299 contains cbas-core commit b6b6c9b with commit message:
          MB-48427: Fix CC proxy address

          build-team Couchbase Build Team added a comment - Build couchbase-server-7.1.0-1299 contains cbas-core commit b6b6c9b with commit message: MB-48427 : Fix CC proxy address
          umang.agrawal Umang added a comment -

          Verified with Enterprise Edition 7.0.2 build 6678

          Combinations verified -
          1. Mixed mode cluster with following config -
          Node 1 - KV, N1QL, CBAS - 6.6.3-9809
          Node 2 - KV, N1QL, CBAS - 6.6.3-9809
          Node 3 - CBAS - 7.0.2-6678

          Observation - Able to create S3 link from all three nodes.

          2. Mixed mode cluster with following config -
          Node 1 - KV, N1QL, CBAS - 7.0.2-6668
          Node 2 - KV, N1QL, CBAS - 7.0.2-6668
          Node 3 - CBAS - 7.0.2-6678

          Observation - Able to create S3 link from Node 1 and Node 3, Node 2 throws error.

          3. Cluster with following config -
          Node 1 - KV, N1QL, CBAS - 7.0.2-6678
          Node 2 - KV, N1QL, CBAS - 7.0.2-6678

          Observation - Able to create S3 link from Node 1 and Node 2

           

          4. Mixed mode cluster with following config -
          Node 1 - KV, N1QL, CBAS - 7.0.1-5996
          Node 2 - KV, N1QL, CBAS - 7.0.1-5996
          Node 3 - CBAS - 7.0.2-6678

          Observation - Able to create S3 link from Node 1 and Node 3, Node 2 throws error.

          umang.agrawal Umang added a comment - Verified with Enterprise Edition 7.0.2 build 6678 Combinations verified - 1. Mixed mode cluster with following config - Node 1 - KV, N1QL, CBAS - 6.6.3-9809 Node 2 - KV, N1QL, CBAS - 6.6.3-9809 Node 3 - CBAS - 7.0.2-6678 Observation - Able to create S3 link from all three nodes. 2. Mixed mode cluster with following config - Node 1 - KV, N1QL, CBAS - 7.0.2-6668 Node 2 - KV, N1QL, CBAS - 7.0.2-6668 Node 3 - CBAS - 7.0.2-6678 Observation - Able to create S3 link from Node 1 and Node 3, Node 2 throws error. 3. Cluster with following config - Node 1 - KV, N1QL, CBAS - 7.0.2-6678 Node 2 - KV, N1QL, CBAS - 7.0.2-6678 Observation - Able to create S3 link from Node 1 and Node 2   4. Mixed mode cluster with following config - Node 1 - KV, N1QL, CBAS - 7.0.1-5996 Node 2 - KV, N1QL, CBAS - 7.0.1-5996 Node 3 - CBAS - 7.0.2-6678 Observation - Able to create S3 link from Node 1 and Node 3, Node 2 throws error.

          People

            umang.agrawal Umang
            ron.graham Ron Graham
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty