Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A5215C78F for ; Thu, 7 Aug 2014 15:48:12 +0000 (UTC) Received: (qmail 34226 invoked by uid 500); 7 Aug 2014 15:48:12 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 34195 invoked by uid 500); 7 Aug 2014 15:48:12 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 34181 invoked by uid 99); 7 Aug 2014 15:48:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Aug 2014 15:48:12 +0000 Date: Thu, 7 Aug 2014 15:48:12 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7585) cassandra sstableloader connection refused with inter_node_encryption MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089358#comment-14089358 ] Jonathan Ellis commented on CASSANDRA-7585: ------------------------------------------- 2.0.5 + 7585 would *be* a custom build. You should plan on running the stable release that this is committed to. > cassandra sstableloader connection refused with inter_node_encryption > --------------------------------------------------------------------- > > Key: CASSANDRA-7585 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7585 > Project: Cassandra > Issue Type: Bug > Components: Core, Tools > Reporter: Samphel Norden > Assignee: Yuki Morishita > Fix For: 2.0.10, 2.1.1 > > Attachments: 7585-2.0.txt > > > cassandra sstableloader connection refused with inter_node_encryption > When using sstableloader to import tables (cassandra 2.0.5) with inter-node encryption and client encryption enabled, I get a connection refused error > I am using > sstableloader -d $myhost -p 9160 -u cassandra -pw cassandra -ciphers TLS_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA -st JKS -tf org.apache.cassandra.thrift.SSLTransportFactory -ts /path/to/truststore -tspw $fullpath/$table > Errors out with > Streaming session ID: 1bc395c0-fbb2-11e3-9812-73da15121373 > WARN 17:13:34,147 Failed attempt 1 to connect to > Similar problem reported in cassandra 2.0.8 by another user > http://stackoverflow.com/questions/24390604/cassandra-sstableloader-connection-refused-with-inter-node-encryption > ================== > Relevant cassandra.yaml snippet (with obfuscation) > server_encryption_options: > internode_encryption: all > keystore:/path/to/keystore > keystore_password: > truststore:/path/to/truststore > truststore_password: > # More advanced defaults below: > protocol: TLS > algorithm: SunX509 > store_type: JKS > cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA] > require_client_auth: true > > # enable or disable client/server encryption. > client_encryption_options: > enabled: true > keystore: /path/to/keystore > keystore_password: > #require_client_auth: true > # Set trustore and truststore_password if require_client_auth is true > truststore:/path/to/truststore > truststore_password: > # More advanced defaults below: > protocol: TLS > algorithm: SunX509 > store_type: JKS > cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA] > ====================== > Note that by setting inter-node encryption to "none" sstableloader works.. but setting it to "all" fails... It seems like sstableloader uses 7000 is my guess instead of using the ssl port 7001 for streaming/gossip. -- This message was sent by Atlassian JIRA (v6.2#6252)