Skip to main content

Troubleshooting — MariaDB

The cluster stays in "Creating" status​

Cause: the nodes and their volumes are being provisioned. This can take several minutes, longer with 3 or 5 replicas.

Solution:

  1. Wait a few minutes and refresh the cluster page.
  2. If the status does not change after about fifteen minutes, or changes to Error or Failed, contact support, providing the project and the cluster name.

Connection refused or timed out​

Cause: external access is disabled, the IP address has not been assigned yet, or the client is using the wrong address or port.

Solution:

  1. In the Connection and network card, check that External Access is Enabled and that the Host field contains an address.
  2. Use port 3306 and test connectivity: 
    mysqladmin -h <host> -P 3306 -u <user> -p ping
  3. Check that no outbound firewall on your network blocks port 3306.

Access denied for user​

Cause: wrong password or password revoked by a rotation, or user without rights on the specified database.

Solution:

  1. In the user list, check the Databases column: the user must have access to the database in use.
  2. Add the access via Actions → Manage Access if necessary.
  3. If in doubt about the password, generate a new one via Actions → Change Password and update your applications.

Error when adding an access or a user​

Cause: the database name or username does not follow the naming rules.

Solution: use only lowercase letters, digits and hyphens, starting with a letter and ending with a letter or a digit. Underscores (_) and uppercase letters are not accepted. See MariaDB concepts.

Disk space full​

Cause: the data volume (including binary logs) has reached the Allocated Size.

Solution:

  1. Measure the space used per database: 
    SELECT table_schema, ROUND(SUM(data_length + index_length) / 1024 / 1024, 1) AS size_mb
    FROM information_schema.tables
    GROUP BY table_schema;
  2. Increase the Disk size (GB) via Edit, within the project's storage quota. See Scale resources.
  3. Delete obsolete data, then optimize the tables concerned (OPTIMIZE TABLE).

Replication out of sync​

Cause: a replica can no longer keep up with the primary (high write load, insufficient resources, infrastructure incident).

Solution: resynchronizing a replica is not offered in the console. Contact support, providing the project and the cluster name.