cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Hayworth (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10908) client_encryption seems to prevent startup in 2.2.4 and 3.1
Date Sat, 19 Dec 2015 08:18:46 GMT


Will Hayworth commented on CASSANDRA-10908:

I'm so sorry--I've screwed up here.

ERROR [main] 2015-12-19 08:15:55,528 - Exception encountered during
java.lang.RuntimeException: Unable to create thrift socket to /
	at org.apache.cassandra.thrift.CustomTThreadPoolServer$Factory.buildTServer(
	at org.apache.cassandra.thrift.TServerCustomFactory.buildTServer(
	at org.apache.cassandra.thrift.ThriftServer$ThriftServerThread.<init>(
	at org.apache.cassandra.thrift.ThriftServer.start( ~[apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.service.CassandraDaemon.start( [apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.service.CassandraDaemon.activate( [apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.service.CassandraDaemon.main( [apache-cassandra-2.2.4.jar:2.2.4]
Caused by: org.apache.thrift.transport.TTransportException: Could not bind to port 9160
	at org.apache.thrift.transport.TSSLTransportFactory.createServer(
	at org.apache.thrift.transport.TSSLTransportFactory.getServerSocket(
	at org.apache.cassandra.thrift.CustomTThreadPoolServer$Factory.buildTServer(
	... 6 common frames omitted
Caused by: java.lang.IllegalArgumentException: Cannot support TLS_RSA_WITH_AES_256_CBC_SHA
with currently installed providers
	at<init>( ~[na:1.8.0_65]
	at org.apache.thrift.transport.TSSLTransportFactory.createServer(
	... 8 common frames omitted

Found in {{system.log}}. Enough said. Sorry for the noise.

> client_encryption seems to prevent startup in 2.2.4 and 3.1
> -----------------------------------------------------------
>                 Key: CASSANDRA-10908
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Amazon Linux 2015.09
>            Reporter: Will Hayworth
>         Attachments: 2.2.4-client-log-trace.log, client_encryption.log
> Hi there! I'm a total Cassandra novice, so please forgive me if this report is lacking
or malformed. I've been setting up a new cluster and trying to use 3.1 but I've noticed that
so much as *enabling* client-to-node encryption causes the node to shut down after determining
there's no gossip backlog. Notably, I set up node-to-node encryption beforehand and that was
working just fine. I thought they might be interfering with each other, but that seems not
to be the case. Logs attached. (Please let me know how I can be of further help!)
> Thanks for looking at this,
> Will

This message was sent by Atlassian JIRA

View raw message