• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Plesk update corrupt PleskDBServer database trying to upgrade Mysql.

Luiz_Gustavo

Basic Pleskian
Hello,

My Plesk is presenting ERROR 500 when try to access, all site is working OK, but the Plesk interface dont.
This problem occurs during a plesk daily update and now cant even start plesk db.

[2019-09-18 02:17:56.586999] MSI (04): Action 'Set files permissions of Plesk MySQL Server...' finished successfully
[2019-09-18 02:17:56.586999] MSI (04): Plesk custom action ended 02:17:56: Set files permissions of Plesk MySQL Server...
[2019-09-18 02:17:56.586999] MSI (04): Plesk custom action start 02:17:56: Upgrade data of MySQL Server...
[2019-09-18 02:17:56.586999] MSI (04): Execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mysqlmng_adm.exe" --upgrade-server-data "--initial-ver=5.5" "--target-ver=5.7.27"
[2019-09-18 02:17:56.586999] MSI (04): Output:
[2019-09-18 02:17:59.836997] MSI (04): Stop service...
[2019-09-18 02:17:59.836997] MSI (04): Removing InnoDB log files...
[2019-09-18 02:17:59.836997] MSI (04): Start service...
[2019-09-18 02:17:59.836997] MSI (04): Incorrect function. (Error code 1) at Start service PleskSQLServer
[2019-09-18 02:17:59.836997] MSI (04): at (service::startStopService line 997)
[2019-09-18 02:17:59.836997] MSI (04): at execute console command --upgrade-server-data(vconsoleapp::start line 93)
[2019-09-18 02:17:59.836997] MSI (04): at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mysqlmng_adm.exe" --upgrade-server-data "--initial-ver=5.5" "--target-ver=5.7.27"(vconsoleapp::run line 110)
[2019-09-18 02:17:59.836997] MSI (04): Critical action 'Upgrade data of MySQL Server...' failed:
Command "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mysqlmng_adm.exe" --upgrade-server-data "--initial-ver=5.5" "--target-ver=5.7.27" failed with code 1. Output: Stop service...
Removing InnoDB log files...
Start service...
Incorrect function. (Error code 1) at Start service PleskSQLServer
at (service::startStopService line 997)
at execute console command --upgrade-server-data(vconsoleapp::start line 93)
at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mysqlmng_adm.exe" --upgrade-server-data "--initial-ver=5.5" "--target-ver=5.7.27"(vconsoleapp::run line 110)

at (CmdAction::Commit line 391)
at Execute action Upgrade data of MySQL Server...(executeList line 268)
[2019-09-18 02:17:59.836997] MSI: Error! Critical action 'Upgrade data of MySQL Server...' failed:
Command "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mysqlmng_adm.exe" --upgrade-server-data "--initial-ver=5.5" "--target-ver=5.7.27" failed with code 1. Output: Stop service...
Removing InnoDB log files...
Start service...
Incorrect function. (Error code 1) at Start service PleskSQLServer
at (service::startStopService line 997)
at execute console command --upgrade-server-data(vconsoleapp::start line 93)
at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mysqlmng_adm.exe" --upgrade-server-data "--initial-ver=5.5" "--target-ver=5.7.27"(vconsoleapp::run line 110)

at (CmdAction::Commit line 391)
at Execute action Upgrade data of MySQL Server...(executeList line 268)
MSI (01): Critical action 'Upgrade data of MySQL Server...' failed:
Command "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mysqlmng_adm.exe" --upgrade-server-data "--initial-ver=5.5" "--target-ver=5.7.27" failed with code 1. Output: Stop service...
Removing InnoDB log files...
Start service...
Incorrect function. (Error code 1) at Start service PleskSQLServer
at (service::startStopService line 997)
at execute console command --upgrade-server-data(vconsoleapp::start line 93)
at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin\mysqlmng_adm.exe" --upgrade-server-data "--initial-ver=5.5" "--target-ver=5.7.27"(vconsoleapp::run line 110)

at (CmdAction::Commit line 391)
at Execute action Upgrade data of MySQL Server...(executeList line 268)


Now I cant start PLESKDB


190918 2:18:00 [Note] Plugin 'FEDERATED' is disabled.
190918 2:18:00 InnoDB: The InnoDB memory heap is disabled
190918 2:18:00 InnoDB: Mutexes and rw_locks use Windows interlocked functions
190918 2:18:00 InnoDB: Compressed tables use zlib 1.2.11
190918 2:18:00 InnoDB: Initializing buffer pool, size = 16.0M
190918 2:18:00 InnoDB: Completed initialization of buffer pool
InnoDB: Error: checksum mismatch in data file .\ibdata1
190918 2:18:00 InnoDB: Could not open or create data files.
190918 2:18:00 InnoDB: If you tried to add new data files, and it failed here,
190918 2:18:00 InnoDB: you should now edit innodb_data_file_path in my.cnf back
190918 2:18:00 InnoDB: to what it was, and remove the new ibdata files InnoDB created
190918 2:18:00 InnoDB: in this failed attempt. InnoDB only wrote those files full of
190918 2:18:00 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
190918 2:18:00 InnoDB: remove old data files which contain your precious data!
190918 2:18:00 [ERROR] Plugin 'InnoDB' init function returned error.
190918 2:18:00 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
190918 2:18:00 [ERROR] Unknown/unsupported storage engine: INNODB
190918 2:18:00 [ERROR] Aborting
 
Anyone can help?

I found a solution about NUL in Windows, but do no solve, also try innodb recovery and nothing.
This is caused by an auto-update from Plesk, I have many servers with exact same configuration and I am very worried about this same situation could affect other servers.
 
I'd suggest you ask the assistance of Plesk Support Team. They will check the issue directly on your server.
 
Back
Top