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

cluster-wide collectinfo failed to upload files to server using https protocol

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Test Blocker
    • 3.0
    • 3.0
    • build
    • Security Level: Public
    • None
    • ubuntu 12.04 64-bit

    Description

      Install couchbase server 3.0.0-820 on 2 ubuntu 12.04 64-bit nodes
      Create a cluster
      Create 2 buckets
      Do cluster-wide collectinfo which upload files to S3.
      At the end of process, upload files failed with error

      192.168.171.148: curl: (1) Protocol https not supported or disabled in libcurl
      192.168.171.149: curl: (1) Protocol https not supported or disabled in libcurl

      Login to vm 192.168.171.148, I could upload files to S3

      • SSLv3, TLS alert, Client hello (1):
        root@ubuntu:~# curl -v --upload-file /opt/couchbase/var/lib/couchbase/tmp/collectinfo-2014-06-17T230610-ns_1@192.168.171.148.zip https://s3.../collect_info/3_0_0/2014_06/
      • About to connect() to s3.amazonaws.com port 443 (#0)
      • Trying 207.171.185.200... connected
      • successfully set certificate verify locations:
      • CAfile: none
        CApath: /etc/ssl/certs
      • SSLv3, TLS handshake, Client hello (1):
      • SSLv3, TLS handshake, Server hello (2):
      • SSLv3, TLS handshake, CERT (11):
      • SSLv3, TLS handshake, Server finished (14):
      • SSLv3, TLS handshake, Client key exchange (16):
      • SSLv3, TLS change cipher, Client hello (1):
      • SSLv3, TLS handshake, Finished (20):
      • SSLv3, TLS change cipher, Client hello (1):
      • SSLv3, TLS handshake, Finished (20):
      • SSL connection using AES256-SHA
      • Server certificate:
      • subject: C=US; ST=Washington; L=Seattle; O=Amazon.com Inc.; CN=s3.amazonaws.com
      • start date: 2014-04-12 00:00:00 GMT
      • expire date: 2015-04-13 23:59:59 GMT
      • subjectAltName: s3.amazonaws.com matched
      • issuer: C=US; O=VeriSign, Inc.; OU=VeriSign Trust Network; OU=Terms of use at https://www.verisign.com/rpa (c)10; CN=VeriSign Class 3 Secure Server CA - G3
      • SSL certificate verify ok.
        > PUT /packages.couchbase/collect_info/3_0_0/2014_06/collectinfo-2014-06-17T230610-ns_1%40192.168.171.148.zip HTTP/1.1
        > User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
        > Host: s3.amazonaws.com
        > Accept: /
        > Content-Length: 2193473
        > Expect: 100-continue
        >
        < HTTP/1.1 100 Continue
      • We are completely uploaded and fine
        < HTTP/1.1 200 OK
        < x-amz-id-2: X7uBb4PFv4sM9ud7MCoN2X6M/HnSWroFrhQaWC+3Yur7WnmJXXy50nxtuMTZxh3m
        < x-amz-request-id: B2BDFD56D961E092
        < Date: Tue, 17 Jun 2014 23:24:13 GMT
        < ETag: "09138fd46ff01c8139f704f6f97a0b41"
        < Content-Length: 0
        < Server: AmazonS3
        <
      • Connection #0 to host s3.amazonaws.com left intact
      • Closing connection #0
      • SSLv3, TLS alert, Client hello (1):

      Attachments

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

        Activity

          People

            thuan Thuan Nguyen
            thuan Thuan Nguyen
            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