• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Migration with MySQL 5.5 installed do not migrate databases

jcgalvez

Basic Pleskian
Plesk Linux Centos 6.7 + upgrade mysql to version 5.5 according to the instructions on the following Link
https://kb.plesk.com/en/125589

I have 2 servers with 12.5 patched and upgraded to the top, one is a vps and the other running on hardware.

The problem is that when I put migrate from server a(vps) to server b (hardware) migrates everything BUT the mysql databases.

I have to mention that I "upgraded" mysql to 5.5 using https://kb.plesk.com/en/125589

I'm getting the following error

`- Subscription 'test.com'
|
|- error: Failed to copy content of database 'test1'
| Migration tools tried to perform operation in 3 attempts: Command execution failed on the source server 'source' (h42.test.com) with non-zero exit code.
| command: mysqldump -h localhost -P 3306 -uadmin --quick --quote-names --add-drop-table --default-character-set=utf8 --set-charset imexportsrl1 -p'***hidden***' --routines > /tmp/panel_migrator/db-dumps/test1.sql
| exit code: 2
| stdout:
| stderr: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'test1'': Cannot load from mysql.proc. The table is probably corrupted (1548)

however while testing that database on the vps server says that it's ok and no need to fix it
 
Back
Top