Migration error: Cannot stat: No such file or directory Exiting with failure status due to previous errors

Created:

2016-11-16 13:04:54 UTC

Modified:

2017-06-09 04:38:19 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Migration error: Cannot stat: No such file or directory Exiting with failure status due to previous errors

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk Onyx for Linux

Symptoms

  • Migration of several or all domains fails with the following error:

    [ERROR] Failed to fetch configuration data from Plesk servers
    Cause: Command execution failed on the source server 'source' (www.example.com) with non-zero exit code.
    command: cd /tmp/panel_migrator/pmm_agent; tar rf migration_dump.tar backup_info*
    exit code: 2
    stdout:
    stderr: tar: backup_info*: Cannot stat: No such file or directory
    tar: Exiting with failure status due to previous errors
  • In /usr/local/psa/var/modules/panel-migrator/sessions/<session_id>/pmm-agent_<id>/dump.log file on the destination server the following error can be found:

    DBD::mysql::st execute failed: Lost connection to MySQL server during query at Db/MysqlDbiBackend.pm line 69.
    WARN Unable to execute SQL: Lost connection to MySQL server during query.
    DBD::mysql::st execute failed: MySQL server has gone away at Db/MysqlDbiBackend.pm line 69.
    DEBUG Timeout occured during mysql query. Reconnecting.
    DBI connect('dbname=example_db;host=localhost;port=3306','admin',...) failed: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111) at Db/DbiBackend.pm line 47
    Database example_db, type mysql is skipped from backup due to error: Died at Db/MysqlDbiBackend.pm line 83.
  • When trying to access example_db on the source server the following error appears:

    # 2006 - MySQL server has gone away

    or

    Error processing the request
    Error Code: 500
    Error text: PleskDBException

Cause

Database example_db is corrupted.

Resolution

  1. Restore example_db from the last valid database dump.

  2. Start the migration again

Have more questions? Submit a request
Please sign in to leave a comment.