Application Launcher

Date Published: October 22, 2025

If your Cloud IDE environment disk space is full, you may need to clear out MySQL binary logs. To do so:

Log in to the Cloud IDE terminal.
Run the following command:
```
ls ~/mysql-data/ -lah
```
This displays a list of files, some of which look like binlog.000063. Choose the oldest file you'd like to keep. (You may not want to keep any of them.)
Run the following command to login to MySQL as the root user (you can only do this on a Cloud IDE):
```
mysql -u root # No password needed
```
Run the following MySQL query and substitute the file that you chose from the list in step #3.
```
PURGE BINARY LOGS TO '[NAME OF FILE HERE]';
```
Run the following command to edit the config file:
```
nano vi /home/ide/configs/mysql/settings.cnf
```
Add the following lines in the config file to to turn of binary logging:
```
[mysqld]
skip-log-bin
```
Save and exit.
Restart MySQL on the terminal:
```
acli ide:service-restart mysql
```

To ensure that Binlog is disabled, run the following command:

drush sqlq "SHOW VARIABLES LIKE 'log_bin';"

The following output is displayed::

+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| log_bin       | OFF   |
+---------------+-------+

For information about why binary logs start filling up on Cloud IDE or Cloud Classic, visit Binlogs. Note that you cannot remove them on Cloud Classic environments because that part of of the platform is managed by Acquia. If you believe that is necessary, submit a Support case.

Clear Out MySQL Binary Logs on Your Cloud IDE