Database storage troubleshooter on Adobe Commerce

This can be indicated by a range of symptoms including:

• /tmp mount being full
• Site down or outage
• Unable to SSH into a node
• Errors like No space left on device (28)

For a list of errors resulting from /tmp being full, review /tmp mount full.

Or do you have a /data/mysql issue caused by a lack of space? Symptoms include:

• Site outage
• Customers unable to add products to cart
• Database connection failure
• Galera errors like SQLSTATE[ 08S01] : Communication link failure: 1047 WSREP

For a list of errors resulting from low MySQL disk space, refer to MySQL disk space is low on Adobe Commerce on cloud infrastructure.

If you are unsure if you have a disk space issue and you have a New Relic account, go to the New Relic Infrastructure monitoring Hosts page. From there:

• Click on the Storage tab
• Change the Chart Shows dropdown from 5 to 20 results
• Look in the table for high disk use in the Disk Used % chart or table

For more detailed steps, refer to New Relic Infrastructure Monitoring > Storage tab.

If you have any of the symptoms described above, check the state of your inodes to make sure this is not being caused by a file number issue. Run in the CLI/Terminal:

df -ih

Is IUse% > 90%?

• YES – Too many files. Review steps to remove files safely in Safely delete files when out of disk space. Proceed to Step 2 after completing these steps. If you want to request more space, submit a support ticket.

• NO – Check disk space usage in /tmp and /data/mysql directories. Run in the CLI/Terminal:

  code language-none
  df -h | grep mysql df -h | grep tmp

Then proceed to Step 3.

After reducing the number of files, run the following command in the CLI/Terminal to check disk space usage in /tmp and /data/mysql.

df -h | grep mysql
df -h | grep tmp

Is greater than 70% used for /tmp or /data/mysql?

• YES – Proceed to Step 3.

• NO – Queries may be exhausting available storage. This could crash the node, killing the query and removing the tmp files. Log in to the MySQL command-line client and run:

  code language-none
  SHOW PROCESSLIST;

Examine the output for problematic queries. If unresolved, submit a support ticket requesting more space.

• /tmp – Proceed to Step 4.
• /data/mysql – Proceed to Step 5.

Note: By default, database tmpdir writes to /tmp. To check your database configuration, log in to the MySQL command-line client and run:

SHOW VARIABLES LIKE "TMPDIR";

If tmpdir is still writing to /tmp, you will see /tmp in the Value column.

Follow Troubleshoot /tmp mount full for Adobe Commerce. After applying solutions, run in the CLI/Terminal:

df -h | grep mysql
df -h | grep tmp

Is usage < 70%?

• YES – Issue resolved.
• NO – Submit a support ticket requesting more space.

Note: The solutions in Troubleshoot /tmp mount full are designed for merchants who have not changed the variables for database tmpdir, which by default writes to /tmp. If you have changed the tmpdir value, the instructions in Troubleshoot /tmp mount full will not help.

Your database configuration may no longer be at the original default. Find the database tmpdir config by running in the MySQL command-line client: SELECT @@DATADIR;

If /data/mysql/ is outputted, tmpdir is writing to /data/mysql/. Increase space by following the steps in the MySQL disk space is low on Adobe Commerce on cloud infrastructure. Then run in the CLI/Terminal:

df -h | grep mysql
df -h | grep tmp

Is usage < 70%?

• YES – Issue resolved.
• NO – Submit a support ticket requesting more space.