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

[Backup Service] 'Communication error' when trying to create a repository.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Cannot Reproduce
    • Cheshire-Cat
    • 7.0.0
    • tools
    • 7.0.0-3435

    Description

      Description

      I have observed the following error a few times (on older builds as well), however I cannot determine if this is a user error or bug in the service. Once the issue triggers you can observe it happening repeatedly.

      Could not add repository: location not accessible by all nodes - node db0e41a2f032717e636a90e37b8aacaa cannot access location /tmp/entbackup_10.112.210.101: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: x509: certificate is valid for 127.0.0.1, not 10.112.210.101"
      

       

       

      Additional commentary:

      I cannot provide the steps to reproduce the issue. But here's a general idea of the steps I took today.

      1. Used vagrant to create VMs with couchbase-server 7.0.0-3435.

      2. During one of the two tests I was writing today, I provisioned 3 nodes into a cluster which succeeded and attempted to add a repository which failed.

      The shared directory is working as intended, the shared directory has been succesfully shared between all of the clients.

       

      Attachments

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

        Activity

          Hey Carlos Gonzalez Betancort,

           

          I later noticed that perhaps communication to nodes 2 and 3 have been lost so this could be a side effect of that in which case it's probably not a bug in the backup service.

          asad.zaidi Asad Zaidi (Inactive) added a comment - Hey  Carlos Gonzalez Betancort ,   I later noticed that perhaps communication to nodes 2 and 3 have been lost so this could be a side effect of that in which case it's probably not a bug in the backup service.
          asad.zaidi Asad Zaidi (Inactive) added a comment - - edited

          Carlos Gonzalez Betancort

           

          I observed the issue again on a new install on build 3466. The node was simply rebalanced into a cluster and I attempted to add a repository with a shared directory and observed the same error.  The logs are quite short this time so it may be easier to determine what happened happened.

          asad.zaidi Asad Zaidi (Inactive) added a comment - - edited Carlos Gonzalez Betancort   I observed the issue again on a new install on build 3466. The node was simply rebalanced into a cluster and I attempted to add a repository with a shared directory and observed the same error.  The logs are quite short this time so it may be easier to determine what happened happened.

          As this bug hasn't been observed on my end for several weeks now, it's most likely a result of a user error where the vagrant nodes lose the ability to communicate between each other due to the network interface dying. Hence, I'll close as 'Cannot Reproduce' until I encounter the issue again.

          asad.zaidi Asad Zaidi (Inactive) added a comment - As this bug hasn't been observed on my end for several weeks now, it's most likely a result of a user error where the vagrant nodes lose the ability to communicate between each other due to the network interface dying. Hence, I'll close as 'Cannot Reproduce' until I encounter the issue again.

          People

            asad.zaidi Asad Zaidi (Inactive)
            asad.zaidi Asad Zaidi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty