My Oracle Support Banner

Step 2 of Mammoth Upgrade Fails with "Miscsetup::Patch_fimage/Exec[post_upgrade_script]/returns) change from notrun to 0 failed: Command exceeded timeout" (Doc ID 2284567.1)

Last updated on JANUARY 22, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.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.

Step 2 of Mammoth upgrade fails when patching the factory image due to one or more nodes timing out installing/upgrading packages:

 

Changes

 None. Issue is seen during upgrade

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
 Diagnose
 Troubleshoot
 When /etc/yum.conf is Incorrect
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.