Problems with MySQL table optimisation
Example: mysql> optimize table wp_actionscheduler_actions; +——————————————-+———-+———-+——————————————————————-+ | Table
Example: mysql> optimize table wp_actionscheduler_actions; +——————————————-+———-+———-+——————————————————————-+ | Table
Background You might find on a MySQL 8.x or MariaDB 10.4 server that suddenly disk space just evaporates. After using ncdu you see the problem
Background A fairly complex server has been misbehaving. This has been ongoing for a few weeks. The problem was been hard to isolate because the
Background When installing Virtualmin, the system will prompt for small, medium, large and huge. The question is how are these parameters defined? By examining the
Working servers suddenly start giving the error below when restoring a MySQL database that contains datetime fields with 0000-00-00 defaults: user@server:/tmp# mysql -uuser -ppassword database_name
Background On a legacy server with an older version of MariaDB, restoring to a newer Virtualmin server that run MySQL 8 might be problematic. The
WHMCS has a requirement of MySQL Strict Mode. The official documentation provides instructions on how to do this with WHM/cPanel. This article documents the process
How to run a MySQL query using the command line: Use -e to execute the command. Here is what that will look like: mysql -u
Background After installing a new server, or doing a server migration, you find you can’t suddenly can’t log into PHPMyAdmin as root anymore. The errors
Background You might experience the following MySQL error whilst trying to restore a Virtualmin database: #3 – Error writing file ‘./DB_NAME/TABLE_NAME.frm’ (Errcode: 122) Solution Check