Skip to end of metadata
Go to start of metadata

Symptom

When trying to restore a MySQL DB with InnoDB tables in CDP, you receive the following error:

[2010-Dec-28 22:06:35],[ WARN],Could not stop the mysqld instance [2010-Dec-28 22:06:35],[ERROR],An exception occurred during the request. Could not ping the secondary mysql instance (after starting the instance) [2010-Dec-28 22:06:35],[DEBUG],failed to prepare mysql instance

Cause

When initiating a DB restore, the CDP Server will transfer MySQL data (InnoDB tablespace) to the Agent, that will write the data into the cdp-agent's tmp directory (/var/lib/r1soft/tmp). The CDP Agent will also create a temporary instance of MySQL to conduct the restore to. This is where the problem is occurring. The agent is unable to start the temporary instance. Common causes for this failure are security mechanisms such as SELinux and Apparmor.

Resolution

If caused by SELinux, put SELinux in permissive mode while doing the restore. If running Apparmor, run "service apparmor teardown", simply running 'aa-complain' for mysqld and "service apparmor stop" will not resolve the issue. Once a tmp MySQL instance is created, the Connector/J will connect to both instances and migrate the InnoDB database from the tmp instance to the primary instance.

Related Articles

Page: Error - InnoDB Restore Fails to Prepare MySQL Instance (Knowledge Base) Labels: mysql_3, innodb_3, apparmor_3, teardown_3, file_restore_3, troubleshoot_3
Page: Error - InnoDB Restore Fails to Prepare MySQL Instance (Knowledge Base) Labels: mysql_3, innodb_3, apparmor_3, teardown_3, file_restore_3, troubleshoot_3
Page: Error - InnoDB Restore Fails to Prepare MySQL Instance (Knowledge Base) Labels: mysql_3, innodb_3, apparmor_3, teardown_3, file_restore_3, troubleshoot_3
Page: Error - InnoDB Restore Fails to Prepare MySQL Instance (Knowledge Base) Labels: mysql_3, innodb_3, apparmor_3, teardown_3, file_restore_3, troubleshoot_3
Page: Restoring File Permissions (Knowledge Base) Labels: file_restore_3, bare-metal_restore_3, permission_3
Page: File Restore Speed (Knowledge Base) Labels: file_restore_3
Page: Error - InnoDB Restore Fails to Prepare MySQL Instance (Knowledge Base) Labels: mysql_3, innodb_3, apparmor_3, teardown_3, file_restore_3, troubleshoot_3
Page: Error - Restore with Overwrite Files on Drops the Network (Knowledge Base) Labels: file_restore_3, troubleshoot_3
Page: Error - InnoDB Restore Fails to Prepare MySQL Instance (Knowledge Base) Labels: mysql_3, innodb_3, apparmor_3, teardown_3, file_restore_3, troubleshoot_3
Page: Setting Permissions on SSHFS File System (Knowledge Base) Labels: disk_safe_3, troubleshoot_3
Page: Error - Restore with Overwrite Files on Drops the Network (Knowledge Base) Labels: file_restore_3, troubleshoot_3
Page: Error - AGENT Unable to Set Default Name Check Option (Knowledge Base) Labels: randmmap_3, troubleshoot_3, agent_3
Page: Error - Caused by Java SQL SQLException Database Is Locked (Knowledge Base) Labels: nfs_3, disk_safe_3, troubleshoot_3
Page: Error - Could Not Create Disk Safe Directory (Knowledge Base) Labels: disk_safe_3, troubleshoot_3, cdp_server_3
Page: Error - Could Not Start Snapshot (Knowledge Base) Labels: troubleshoot_3, agent_3
Page: Error - Java Heap Space out of Memory (Knowledge Base) Labels: troubleshoot_3
Page: Error - Location Does Not Contain a Valid Disk Safe (Knowledge Base) Labels: disk_safe_3, troubleshoot_3
Page: Using Two Policies per Agent (Knowledge Base) Labels: disk_safe_3, policy_3, agent_3, troubleshoot_3, volumes_3
Page: Error - Linux cdp agent fails with "Floating Point Exception" (Knowledge Base) Labels: nfs_3, disk_safe_3, troubleshoot_3
Labels:
mysql_3 mysql_3 Delete
innodb_3 innodb_3 Delete
apparmor_3 apparmor_3 Delete
teardown_3 teardown_3 Delete
file_restore_3 file_restore_3 Delete
troubleshoot_3 troubleshoot_3 Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.