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

UI logs showing a Client-side error on XDCR system test (no xdcr/node failures however)

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0.1
    • Component/s: UI
    • Security Level: Public
    • Labels:
      None
    • Environment:

      Description

      Cluster setup: c1:c2::10:10
      biXDCR_bucket: c1 <---> c2
      uniXDCR_src: c1 ---> c2 :uniXDCR_dest
      Front end loads on c1 and c2 for biXDCR_bucket, and on c1 for uniXDCR_src.

      Live clusters at:
      c1: http://ec2-177-71-230-72.sa-east-1.compute.amazonaws.com:8091/
      c2: http://ec2-175-41-186-167.ap-southeast-1.compute.amazonaws.com:8091/

      The UI Log:

      Client-side error-report for user "Administrator" on node 'ns_1@ec2-177-71-230-72.sa-east-1.compute.amazonaws.com':
      User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4
      Got unhandled error: Uncaught RangeError: Maximum call stack size exceeded
      At: http://ec2-177-71-230-72.sa-east-1.compute.amazonaws.com:8091/js/jquery.js:4029
      Backtrace:
      Function: collectBacktraceViaCaller
      Args:

      ---------
      Function: appOnError
      Args:
      "Uncaught RangeError: Maximum call stack size exceeded"
      "http://ec2-177-71-230-72.sa-east-1.compute.amazonaws.com:8091/js/jquery.js"
      4029

      Access:

      ssh -i SanPauloQAKey.pem ubuntu@ec2-177-71-230-72.sa-east-1.compute.amazonaws.com
      ssh -i SingaporeQAKey.pem ubuntu@ec2-175-41-186-167.ap-southeast-1.compute.amazonaws.com

      1. SanPauloQAKey.pem
        2 kB
        Abhinav Dangeti
      2. SingaporeQAkey.pem
        2 kB
        Abhinav Dangeti
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        Logs are usually not useful here. Ideally you will be able to reproduce or at least specify what steps you did or where this problem occurred.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - Logs are usually not useful here. Ideally you will be able to reproduce or at least specify what steps you did or where this problem occurred.
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Abhinav,

        can you describe the steps that lead to this error in the UI

        Show
        farshid Farshid Ghods (Inactive) added a comment - Abhinav, can you describe the steps that lead to this error in the UI
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        possibly side effects o timeouts . system test will rerun with 2.0.1 +A16 and update the ticket

        Show
        farshid Farshid Ghods (Inactive) added a comment - possibly side effects o timeouts . system test will rerun with 2.0.1 +A16 and update the ticket
        Hide
        ketaki Ketaki Gangal added a comment -

        Hi Tony,

        Can you check for similar timeouts when running the
        "KV _ XDCR" system test workload.

        -Ketaki

        Show
        ketaki Ketaki Gangal added a comment - Hi Tony, Can you check for similar timeouts when running the "KV _ XDCR" system test workload. -Ketaki
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Chisheng,

        please confirm if you see this bug in xdcr testing.

        Show
        farshid Farshid Ghods (Inactive) added a comment - Chisheng, please confirm if you see this bug in xdcr testing.
        Hide
        jin Jin Lim (Inactive) added a comment -

        see above comment, thanks.

        Show
        jin Jin Lim (Inactive) added a comment - see above comment, thanks.
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        are you seeing these errors when running xdcr tests ?

        Show
        farshid Farshid Ghods (Inactive) added a comment - are you seeing these errors when running xdcr tests ?
        Hide
        ketaki Ketaki Gangal added a comment -

        Not seeing these errors on current testing; build 144.

        Show
        ketaki Ketaki Gangal added a comment - Not seeing these errors on current testing; build 144.

          People

          • Assignee:
            ketaki Ketaki Gangal
            Reporter:
            abhinav Abhinav Dangeti
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes