My Oracle Support Banner

Step 5 of Mammoth Upgrade Fails at "Hadoop::Startclouderamanager/Exec[start_scm_server]" Because the Cloudera Manager Server Will Not Start (Doc ID 2303052.1)

Last updated on JANUARY 15, 2020

Applies to:

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


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. 

Step 5 of a Mammoth upgrade fails at "Hadoop::Startclouderamanager/Exec[start_scm_server]" because the Cloudera Manager server will not start.

The failing output from "./mammoth -p" looks like:

INFO: Step 5: Installing Hadoop Parcel
INFO: Making sure all puppet agents can be accessed.
INFO: Pinging puppet agents .

ERROR: Puppet agent run on node bda6node03 had errors. List of errors follows

Error [26399]: (//[main]/Hadoop::Startclouderamanager/Exec[start_scm_server]/returns) Starting cloudera-scm-server: [FAILED]#015
Error [26399]: (//[main]/Hadoop::Startclouderamanager/Exec[start_scm_server]/returns) change from notrun to 0 failed: /sbin/service cloudera-scm-server stop ; /sbin/service cloudera-scm-server start returned 1 instead of one of [0]

1. On Node 3 or the node with Cloudera Manager (CM) role, trying to manually start the cloudera-scm-server fails as below: 



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

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