• 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.

Urgently: MySQL server has gone away

Azurel

Silver Pleskian
Hi.

I updated just now from plesk 12.0.18 #74 to #80 and now I get all minutes error mails with
"mysqli::query(): MySQL server has gone away" and database is corrupted... not so funny.

Is here a bug in the update software for mysql?

I restart the server but still a CHECK TABLE is not possible, I get always "server has gone away".

autorepair not work. result after few tables:

mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ...


EDIT: Rename damaged table and import backup fixed that problem for me. But that a simple update crash the database is really not nice!
 
Last edited:
MySQL server has gone away
Timeout defined in the my.cnf was exceeded. Increase the wait_timeout value in the MySQL server configuration file, /etc/my.cnf, or /etc/mysql/my.cnf on Debian/Ubuntu.
 
Thanks, but there is not a problem with wait_timeout. The last plesk update to #80 have crash the database.
/var/log/mysql-error.log
InnoDB: Page may be an index page where index id is 4048
InnoDB: (index "PRIMARY" of table "......")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 4565.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.

After delete this table and import a old backup its working all fine, but all datas for half day are lost. That was the second time that a plesk update crash the database. Last time repair working, this time not.
 
Back
Top