How to Fix: The MySQL Server is Running with the --read-only Option So It Cannot Execute This Statement

When you encounter the message “The MySQL server is running with the —read-only option so it cannot execute this statement,” it typically means the server has been set to a read-only state, preventing write operations. This guide is designed for engineers looking to resolve this issue in a MySQL environment.

Understanding the —read-only option

The --read-only option in MySQL restricts write operations (like INSERT, UPDATE, DELETE) for all users except those with the SUPER privilege. This setting is often used in replication setups or for maintenance tasks.

Check if MySQL is in read-only mode

To confirm if your MySQL server is running in read-only mode, execute the following SQL command:

SHOW VARIABLES LIKE 'read_only';

If the value is ON, then the server is in read-only mode.

Disabling read-only mode

To disable read-only mode, you need the SUPER privilege. Execute the following command:

SET GLOBAL read_only = OFF;

Alternatively, if you have access to the server’s configuration file (my.cnf or my.ini), locate the line read-only = 1 and change it to read-only = 0 or remove the line. Then, restart the MySQL server.

Checking user privileges

If the server is not in read-only mode, but you still get the error, check your user privileges. Run:

SHOW GRANTS FOR 'your_username'@'your_host';

Ensure you have the necessary privileges to perform the operation you’re attempting.

Consider replication configurations

In replication setups, the slave is often set to read-only. If you’re working on a slave server, consider if you should be writing to this server or redirecting the write operations to the master server.

Handling cloud-managed databases

If your MySQL server is managed by a cloud service provider, the read-only settings might be controlled through their management console. Check the database configuration in your cloud provider’s dashboard.

Automate checks and alerts

To avoid this issue in the future, consider setting up monitoring and alerting for the read-only status of your MySQL servers. This can be done through custom scripts or monitoring tools.

Using third-party tools for data management

During troubleshooting, Basedash helps teams move faster by combining AI-assisted analysis with direct SQL access, so you can validate fixes, monitor results, and share clear dashboards after incidents are resolved.

By following these steps, you should be able to identify and resolve the issue of MySQL running in read-only mode. Remember to check the MySQL server settings, user privileges, and consider the replication setup and cloud service configurations in your troubleshooting process.