After going through 2 days of hell in the last few months, I am sharing my thoughts here:
1) I no longer trust anything to do with WHM's ability to run any type of upgrade or update on MariaDB databases. Within the last few months I've had 2 major crashed database incidents due to:
2) Why are there not more built in options to automatically repair DBs that have issues, or in an emergency dump a DB and re-create the DB within the WHM interface? Certainly you could offer far more tools to fix database issues than what you currently offer, which is nearly nothing. How hard would it be to offer an emergency tool that would try to perform a mysql dump and extraction in to a new DB with a "-copy" name added to the DB name. After it ran, if successful, it could display a simple message saying:
1) I no longer trust anything to do with WHM's ability to run any type of upgrade or update on MariaDB databases. Within the last few months I've had 2 major crashed database incidents due to:
- a) a more major upgrade from MariaDB 10.5 to 10.6 using WHM update mysql app;
- b) a "minor" update to MariaDB 10.6 using the standard yum update command;
2) Why are there not more built in options to automatically repair DBs that have issues, or in an emergency dump a DB and re-create the DB within the WHM interface? Certainly you could offer far more tools to fix database issues than what you currently offer, which is nearly nothing. How hard would it be to offer an emergency tool that would try to perform a mysql dump and extraction in to a new DB with a "-copy" name added to the DB name. After it ran, if successful, it could display a simple message saying:
- "success-a new DB was created that was tested to have no issues with the name of db-name-copy. To test this with your app be sure to change the DB name in the config file of your site,"
Last edited by a moderator: