You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Manoj (JIRA)" <ji...@apache.org> on 2017/02/01 05:22:52 UTC
[jira] [Commented] (CASSANDRA-10908) bad report: client_encryption
seems to prevent startup in 2.2.4 and 3.1
[ https://issues.apache.org/jira/browse/CASSANDRA-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848027#comment-15848027 ]
Manoj commented on CASSANDRA-10908:
-----------------------------------
[~yukim] - Hi [~yukim], I am getting same exception/error after enabling client encryption. May i know how to resolve/get away from the exception. Please let me know can i copy the logs here??
> bad report: 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.15#6346)