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] [Updated] (CASSANDRA-10908) bad report: client_encryption seems to prevent startup in 2.2.4 and 3.1
Date Sat, 19 Dec 2015 08:19:46 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Will Hayworth updated CASSANDRA-10908:
--------------------------------------
    Summary: bad report: client_encryption seems to prevent startup in 2.2.4 and 3.1  (was:
INVALID: client_encryption seems to prevent startup in 2.2.4 and 3.1)

> 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.4#6332)

Mime
View raw message