My Oracle Support Banner

Node Migration of the Host with MySQL Slave Role (Node 2 by Default) Fails with "Importing data into database" Due to Puppet Agent Errors (Doc ID 2516116.1)

Last updated on APRIL 17, 2023

Applies to:

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


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.

Migration of the host with MySQL Slave role, Node 2 by default, fails during the step to setup MySQL, "SetupMySQL". This may be Step 2.

The failure can be observed as a Mammoth failure when importing the MySQL database from the Master MySQL database (on Node 3 by default) into the MySQL Slave on the node being migrated to.

The Mammoth failure looks like below where <HOSTNAME5> represents Node 5 where the node with MySQL Slave role is being migrated to. Note that the node being migrated to may vary depending on cluster layout. The example here uses Node 5.

1. The Mammoth migration fails importing the MySQL Master database into the new MySQL slave due to puppet agent errors.

INFO: Step 2 SetupMySQL
INFO: Setting up MySQL databases. This will take some time ...
INFO: Puppet script successfully sent to node <HOSTNAME1>
INFO: Puppet script successfully sent to node <HOSTNAME5>
INFO: Importing data into database. This will take some time ...
INFO: Puppet script successfully sent to node <HOSTNAME5>
INFO: Pinging puppet agents ..............................................................
ERROR: Some puppet agents are not reachable
ERROR: Puppet agent on node <HOSTNAME5> is not reachable
ERROR: Cannot continue with install #Step 2#
INFO: Time spent in step 2 SetupMySQL is 947 seconds.
INFO: Running bdadiagcluster...
INFO: Please run "setup-root-ssh -C" to setup passwordless SSH to all cluster hosts

2. Running a puppet kick from Node 1 to Node 5 repeatedly fails and succeeds.

Puppet kick failures from Node 1 to Node 5 look like:



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.