My Oracle Support Banner

Step 8 of Upgrade to BDA 4.13 Fails Setting Up BDM with No Agents Heartbeating into the Cluster Due to "SSLError: certificate verify failed" and Server Logs Reporting "unknown_ca" (Doc ID 2471800.1)

Last updated on JANUARY 29, 2020

Applies to:

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

Symptoms

NOTE: In the examples that follow, user details, table name, company name, email, hostnames, 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.

 

Step 8 of upgrade to BDA 4.13 fails setting up BDM with no agents heartbeating into the cluster due to "SSLError: certificate verify failed" and server logs reporting "unknown_ca".

Detailed symptoms are:

1. Earlier a Step 5 error is encountered which looks like:

************************************
Error [23196]: (//bdanode03.example.com/Stage[init]/Hadoop::Cm_changes_upgrade/Exec[review_certs_script]/returns) change from notrun to 0 failed: /opt/oracle/bda/compmon/renewcerts $"<identifier>" &> /opt/oracle/BDAMammoth/bdaconfig/tmp/renew_certs_script_<id>.out returned 1 instead of one of [0]
************************************

But this is resolved and upgrade proceeds.

2. Then Step 8, "Cleaning up install" fails setting up BDM with errors like:

************************************
Error [23196]: (//bdanode03.example.com//Stage[pre]/Bdm::Removebdm/Exec[remove_bdm]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/removebdm.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/removebdm_<#>.out returned 1 instead of one of [0]
************************************

Reviewing the /opt/oracle/BDAMammoth/bdaconfig/tmp/removebdm_<#>.out file and checking in Cloudera Manager shows that the failure is due to the mgmt service being unable to start.

3. Once the problem is identified to be that the mgmt service can not start the following error conditions are seen:

a) No agents are heartbeating into the cluster. (In Cloudera Manager navigate: Hosts > All Hosts > Check: "Last Heartbeat" column.)

b) The agent logs, /var/log/cloudera-scm-agent/cloudera-scm-agent.log, report:

SSLError: certificate verify failed

c) The server log, /var/log/cloudera-scm-server/cloudera-scm-server.log, on Node 3 reports:

unknown_ca

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
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.