My Oracle Support Banner

Rerunning "./mammoth -p" too Soon After Previous Update Failure Raises: "ERROR: Sending puppet script to node bdanode0x returned error 3" (Doc ID 1983856.1)

Last updated on APRIL 21, 2018

Applies to:

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

Symptoms

Rerunning the upgrade to BDA V4.1 raises: ERROR: Sending puppet script to node bdanode0x returned error 3.  The BDA node can vary as can the step this happens at.

# ./mammoth -p
...
.ERROR: Sending puppet script to node bdanode0x returned error 3
Warning: Setting manifestdir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1095:in `issue_deprecations')
Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1095:in `issue_deprecations')
Warning: Puppet kick is deprecated. See http://links.puppetlabs.com/puppet-kick-deprecation
Warning: Failed to load ruby LDAP library. LDAP functionality will not be available
Triggering bdanode0x.example.com
Getting status
status is running
Host bdanode0x.example.com is already running
bdanode0x.example.com finished with exit code 3
Failed: bdanode0x.example.com
INFO: Puppet script successfully sent to node bdanode0y
...
INFO: Puppet script successfully sent to node bdanode0n
ERROR: Script could not be sent to some nodes Cannot continue with install #Step X#

 

Changes

 A previous upgrade failure causing the upgrade with "./mammoth -p" to be rerun.

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


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