• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Mysql could not start

ThanhN

Basic Pleskian
Hello to day i have this problem. I can't start MYSQL. How can i fix this? :(

Thank you
 

Attachments

  • Untitled.png
    Untitled.png
    5.8 KB · Views: 7
  • My-Server.zip
    1.3 KB · Views: 1
Last edited:
Looks like InnoDB database is corrupted. Try to use MySQL methods for fixing this problem. You can find it on page mentioned in error log or other mysql documentation. This article http://kb.parallels.com/en/6586 also may be useful. Contact Support Team if you are not familiar with MySQL recovering.
 
Looks like InnoDB database is corrupted. Try to use MySQL methods for fixing this problem. You can find it on page mentioned in error log or other mysql documentation. This article http://kb.parallels.com/en/6586 also may be useful. Contact Support Team if you are not familiar with MySQL recovering.

Thank you for your quick answer

i have some new information in CMD when start MYSQL

"C:\Program Files (x86)\Parallels\Plesk\Databases\MySQL51\bin>mysqld start
140324 14:47:15 [Warning] Can't create test file C:\Program Files (x86)\Parallels\Plesk\Databases\MySQL51\data\TND-SV1.lower-test
140324 14:47:15 [Warning] Can't create test file C:\Program Files (x86)\Parallels\Plesk\Databases\MySQL51\data\TND-SV1.lower-test
mysqld: Can't change dir to 'C:\Program Files (x86)\Parallels\Plesk\Databases\MySQL51\data\' (Errcode: 2)
140324 14:47:15 [ERROR] Aborting

140324 14:47:15 [Note] mysqld: Shutdown complete"


In http://kb.parallels.com/en/6586

i have set "innodb_force_recovery = 4" for dump database but MySQL Server still same error. Do you have any idea ?
 
Last edited:
Back
Top