During Mammoth Upgrade the KMS Service Goes Into Bad Health at Step 2
(Doc ID 2428379.1)
Last updated on JANUARY 29, 2020
Applies to:Big Data Cloud Service - Version 1.0 and later
At Step 2 of a Mammoth upgrade the KMS services goes into bad health. In the case here the upgrade was from 4.9.1 to 4.11.4.
Additional symptoms look like:
1. Navigating to All Recent Commands in Cloudera Manager (CM) shows that the KMS service does not start as below:
Failed to start service.
Key Trustee KMS
Starting 2 roles on service
Service did not start successfully; not all of the required roles started: only 0/2 roles started. Reasons : Service has only 0 Key Management Server Proxy roles running instead of minimum required 1.
2. Trying to restart the cluster in CM fails with:
Key Management Server Proxy (<proxy node>) Process Status Suppress...
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