My Oracle Support Banner

On a BDA 5.2 Cluster with Self-Signed Certificates A Node Fails to Start with "SSLError: sslv3 alert certificate unknown" (Doc ID 2990768.1)

Last updated on JULY 20, 2024

Applies to:

Big Data Appliance Integrated Software - Version 5.2.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

On a BDA 5.2 cluster with self-signed certificates a node fails to start. Note that one or more nodes could experience the same issue.

1. Checking in Cloudera Manager, Hosts > All Hosts, shows that the node is not heart-beating into the cluster.

2. Cloudera Manager also reports:

Changes

This can happen after BDA default self-signed certificates are renewed following, How to Renew the Default Self-Signed Certificates on BDA V4.3 and Higher (Doc ID 2365807.1).

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.