On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

Plesk pre-migration check finishes with an error: Set variable innodb_strict_mode to OFF on target to avoid the migration errors

Avatar
Miguel Monteiro
Updated
Follow
Plesk for Windows Plesk for Linux kb: technical ext: migrator

Applicable to:

  • Plesk for Linux
  • Plesk for Windows

Symptoms

  • The following error appears during a migration pre-check on the target server:

    CONFIG_TEXT: In InnoDB 5.6 (both in MySQL 5.6 and MariaDB 10.0/10.1) server has variable innodb_strict_mode=0 by default.
    So you can create table with wrong ROW_FORMAT option and warning will be reported.
    In InnoDB 5.7 (both in MySQL 5.7 and MariaDB 10.2) server has variable innodb_strict_mode=1 by default.
    Migration from source, hosted with previous version of InnoDB will not be possible to target
    with current version of InnoDB and error will be issued if innodb_strict_mode is set to default.
    Set variable innodb_strict_mode to OFF on target to avoid the migration errors.
    Here is the link describing the problem
    https://jira.mariadb.org/browse/MDEV-11305

    Here is a list of affected subscriptions:
    - example.com

Cause

Strict mode is enabled on the newer versions of MySQL/MariaDB by default.

Resolution

Note: Once the migration will finish, it is safe to enable back the innodb_strict_mode option in Plesk Obsidian.

For Linux

  1. Connect to the target server via SSH.

  2. Add innodb_strict_mode to MySQL configuration:
    2.1. Open MySQL configuration file /etc/my.cnf in a text editor, for example, in the vi editor:

    CONFIG_TEXT: vi /etc/my.cnf

Note: For Debian/Ubuntu the path is /etc/mysql/my.cnf

2.2. Add innodb_strict_mode=OFF under the [mysqld] section:

CONFIG_TEXT: [mysqld]
innodb_strict_mode=OFF
<...>

2.3. Save the changes and close the file.

  1. Restart MySQL service:

    # service mysql restart || service mariadb restart || service mysqld restart

  1. Proceed with the migration.
For Windows
  1. Connect to the target server via RDP.
  2. Open MySQL configuration file %plesk_dir%Databases\MySQL\my.ini in a text editor.
    2.1 Add innodb_strict_mode=OFF under the [mysqld] section:

    CONFIG_TEXT: [mysqld]
    innodb_strict_mode=OFF
    <...>

    2.3. Save the changes and close the file

  1. Restart MySQL service via Plesk Services Monitor (it can be found in the system tray).

  2. Proceed with the migration

Comments

2 comments

Sort by Date Votes
  • Avatar
    Eriks Bass (Edited )

    Thanks! It helps me a lot.

    For Linux

    Some comment for - 2.2. Add innodb_strict_mode=OFF under the [mysqld] section

    To edit text, you need to enter the insert mode by pressing i key. Go back to normal mode by pressing Esc key again.

    Some comment for - 2.3. Save the changes and close the file.

    To save the changes and close the file Press the ESC key ---> Type :wq ---> Press the ENTER key

    Exit without saving changes Press the ESC key ---> Type :q! ---> Press the ENTER key

    1
    Comment actions Permalink
  • Avatar
    Miguel Monteiro

    Eriks Bass Hello Erik,

    Thank you for sharing the details. We have this information mentioned in our article How to edit a file using the vi utility

    I made sure to add a link to this article in the resolution for Linux.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles