cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Hayworth (JIRA)" <j...@apache.org>
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

    [ https://issues.apache.org/jira/browse/CASSANDRA-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065294#comment-15065294
] 

Will Hayworth commented on CASSANDRA-10908:
-------------------------------------------

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

{quote}
ERROR [main] 2015-12-19 08:15:55,528 CassandraDaemon.java:651 - Exception encountered during
startup
java.lang.RuntimeException: Unable to create thrift socket to /0.0.0.0:9160
	at org.apache.cassandra.thrift.CustomTThreadPoolServer$Factory.buildTServer(CustomTThreadPoolServer.java:267)
~[apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.thrift.TServerCustomFactory.buildTServer(TServerCustomFactory.java:46)
~[apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.thrift.ThriftServer$ThriftServerThread.<init>(ThriftServer.java:131)
~[apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.thrift.ThriftServer.start(ThriftServer.java:58) ~[apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.service.CassandraDaemon.start(CassandraDaemon.java:450) [apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:544) [apache-cassandra-2.2.4.jar:2.2.4]
	at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:638) [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(TSSLTransportFactory.java:120)
~[libthrift-0.9.2.jar:0.9.2]
	at org.apache.thrift.transport.TSSLTransportFactory.getServerSocket(TSSLTransportFactory.java:105)
~[libthrift-0.9.2.jar:0.9.2]
	at org.apache.cassandra.thrift.CustomTThreadPoolServer$Factory.buildTServer(CustomTThreadPoolServer.java:255)
~[apache-cassandra-2.2.4.jar:2.2.4]
	... 6 common frames omitted
Caused by: java.lang.IllegalArgumentException: Cannot support TLS_RSA_WITH_AES_256_CBC_SHA
with currently installed providers
	at sun.security.ssl.CipherSuiteList.<init>(CipherSuiteList.java:92) ~[na:1.8.0_65]
	at sun.security.ssl.SSLServerSocketImpl.setEnabledCipherSuites(SSLServerSocketImpl.java:200)
~[na:1.8.0_65]
	at org.apache.thrift.transport.TSSLTransportFactory.createServer(TSSLTransportFactory.java:115)
~[libthrift-0.9.2.jar:0.9.2]
	... 8 common frames omitted
{quote}

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: https://issues.apache.org/jira/browse/CASSANDRA-10908
>             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
(v6.3.4#6332)

Mime
View raw message