---
title: "Clear Out MySQL Binary Logs on Your Cloud IDE"
date: "2025-10-22T19:43:30+00:00"
summary: "Learn how to clear MySQL binary logs on your Cloud IDE to free up disk space with step-by-step instructions."
image:
type: "article"
url: "/acquia-cloud-platform/add-ons/cloud-ide/help/94716-clear-out-mysql-binary-logs-your-cloud-ide"
id: "134744d8-5883-4036-8da8-cb42851c13d3"
---

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

1.  [Log in to the Cloud IDE terminal.](/acquia-cloud-platform/add-ons/cloud-ide/using-terminal-cloud-ide "Using the terminal in Cloud IDE")
2.  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.)
    
3.  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
    
4.  Run the following MySQL query and substitute the file that you chose from the list in step [#3.](#3.)
    
        PURGE BINARY LOGS TO '[NAME OF FILE HERE]';
    
5.  Run the following command to edit the config file:
    
        nano vi /home/ide/configs/mysql/settings.cnf
    
6.  Add the following lines in the config file to turn off binary logging:
7.      [mysqld]
        skip-log-bin
    
8.  Save and exit.
9.  Restart MySQL on the terminal:
    
        acli ide:service-restart mysql
    
10.  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](/acquia-cloud-platform/binlogs "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](/service-offerings/contacting-acquia-support "Contacting Acquia Support").