Upgrade using AMI to v2.6.0 from earlier versions may fail with the Configuration Wizard timing out and "Could not upgrade mysql"
Upgrade using AMI to v2.6.0 from earlier versions may fail with the Configuration Wizard timing out:
The following error may be printed in the "config_shell_commands.log" file:
upgrade_mysql_db(:60) Could not run mysql5.6 on docker, error=409 Client Error: Conflict ("Conflict. The container name "/mysql56" is already in use by container "648d2f1ba3087b4f55566c71dae96d9ad6c930c018362ddedee1af52182261e7". You have to remove (or rename) that container to be able to reuse that name.")
perform_shell_commands(:418) Could not upgrade mysql, returned: 1
...
perform_shell_commands(:444) Failed upgrading or starting databse after 10 retries, giving up
handle_configuration_result_notification(:34) Due to configuration failure = Stopping cpmagent
perform_shell_commands(:418) Could not upgrade mysql, returned: 1
...
perform_shell_commands(:444) Failed upgrading or starting databse after 10 retries, giving up
handle_configuration_result_notification(:34) Due to configuration failure = Stopping cpmagent
If you encounter this error, please use the latest 2.6.X version AMI.
Link to Release Notes and the latest patch – https://support.n2ws.com/portal/kb/articles/release-notes-for-the-latest-v2-6-x-cpm-release
Related Articles
Upgrade using AMI to v2.6.0 from earlier versions may fail with "Configuration Failed" and "Could not migrate database to version 2.6.0 scheme"
Upgrade using AMI to v2.6.0 from earlier versions may fail with "Configuration Failed". The following error may be printed in the "config_shell_commands.log" file: perform_shell_commands(:629) Could not migrate database to version 2.6.0 scheme, ...CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors
CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors: The reason for this failure is using wrong AWS Access Key and Secret Key - maybe they belong to the wrong account.Installation/upgrade to v2.6.0 using the AMI method may fail when using proxy with error 500 displayed
Installation/upgrade to v2.6.0 using the AMI method may fail when using proxy with error 500 displayed: The following errors may be printed in the cpm_config.log file: ERROR: list_aliases(kms.py:42) Failed getting aliases list (region: us-east-1, ...CPM Server may fail to finish configuration when upgrading from v2.1.3 to v2.1.3a using AMI
At the end of configuration, when clicking at the "Click here to start CPM" link, CPM may go back to a page asking to enter instance id. Rebooting the instance and going directly to the /console URL doesn't help. The following error can be found in ...Linux scripts may start failing after upgrading to a new CPM version (using AMI) or migrating CPM to a different account/region
Linux scripts may start failing after upgrading to a new CPM version (using AMI) or migrating CPM to a different account/region. In order to restore scripts' functionality, please run a script from command line, and approve the SSH key by answering ...