[CASSANDRA-10908] bad report: client_encryption seems to prevent startup in 2.2.4 and 3.1

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Not A Problem

Environment

Amazon Linux 2015.09

• Severity: Normal
• Assignee: Unassigned
• Reporter: Will Hayworth
• Created: 19/Dec/15 07:11
• Updated: 16/Apr/19 09:30
• Resolved: 19/Dec/15 08:24

Description

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