Check the MySQL log file
NOTE: We are in the process of modifying the file structure and configuration for many Bitnami stacks. On account of these changes, the file paths stated in this guide may change depending on whether your Bitnami stack uses native Linux system packages (Approach A), or if it is a self-contained installation (Approach B). To identify your Bitnami installation type and what approach to follow, run the command below:
$ test ! -f "/opt/bitnami/common/bin/openssl" && echo "Approach A: Using system packages." || echo "Approach B: Self-contained installation."
The output of the command indicates which approach (A or B) is used by the installation, and will allow you to identify the paths, configuration and commands to use in this guide. Refer to the FAQ for more information on these changes.
NOTE: We are in the process of modifying the configuration for many Bitnami stacks. 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. To identify which database server is used in your stack, run the command below:
$ test -d /opt/bitnami/mariadb && echo "MariaDB" || echo "MySQL"
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.
The main MySQL log file is located at one of the following locations, on the MySQL database server host:
- For Bitnami installations following Approach A (using Linux system packages): /opt/bitnami/mysql/logs/mysqld.log
- For Bitnami installations following Approach B (self-contained installations): /opt/bitnami/mysql/data/mysqld.log
MySQL database performance and connectivity can be affected by low disk space and/or low available memory. These resources can be checked using the df and free commands, as described in the server performance troubleshooting guide.