![]() ![]() $ sudo /opt/bitnami/ctlscript.sh restart mariadb Do not forget to remove the innodb_force_recovery option from the my.cnf file and restart the MariaDB server again. If the table is recovered, you should see “OK” in the er status table. In this case, the error was related to the er table. Open a new console and try to log in to the database: $ mysql -u root -p Start the MariaDB database with the following command: $ mysqld -skip-grant-tables -user=mysql -skip-external-locking -port=3306 -sock=/opt/bitnami/mariadb/tmp/mysql.sock ![]() You can add the innodb_force_recovery=1 option in the main MariaDB configuration file at /opt/bitnami/mariadb/my.cnf to try and fix the database: The MariaDB database is configured to use InnoDB engine by default. To check the latest entries in the MariaDB log file, run the command below: $ sudo tail -n 100 /opt/bitnami/mariadb/logs/mysqld.logĪssume the following error in the log file: 110108 10:37:45 Fatal error: Can't open and lock privilege tables: Table 'user' is marked as crashed Check logsīefore trying to recover a MariaDB database, you should check the exact error in the log file. The output of the command indicates which database server (MySQL or MariaDB) is used by the installation, and will allow you to identify which guides to follow in our documentation for common database-related operations. To identify which database server is used in your stack, run the command below: $ test -d /opt/bitnami/mariadb & echo "MariaDB" || echo "MySQL" On account of these changes, the file paths and commands stated in this guide may change depending on whether your Bitnami stack uses MySQL or MariaDB. NOTE: We are in the process of modifying the configuration for many Bitnami stacks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |