When encountering the error 1179: Transaction is read-only in MySQL, follow these steps:
SHOW VARIABLES LIKE 'transactionreadonly';
If the value is `ON`, your transaction is set to read-only. To change it for the current session, execute:SET SESSION transactionreadonly = OFF;
SELECT @@GLOBAL.txisolation, @@txisolation;
If necessary, adjust the isolation level for your session. For example, to set it to READ-COMMITTED, use:SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED;
SHOW GRANTS FOR CURRENT_USER;
If write permissions are missing, you might need to contact someone with administrative privileges or, if you have the necessary credentials, grant the permissions yourself (ensure you understand the security implications):GRANT INSERT, UPDATE, DELETE ON yourdatabasename.* TO 'yourusername'@'yourhost';
Replace `yourdatabasename`, `yourusername`, and `yourhost` with the actual database name, your MySQL username, and host, respectively.
SHOW GLOBAL VARIABLES LIKE 'read_only';
If it’s set to `ON` and you have the necessary privileges, you can turn it off with:SET GLOBAL read_only = OFF;
Be cautious with this step as it affects the entire database server.
SHOW VARIABLES LIKE 'log_error';
Then, check the contents of the log file for relevant messages.
Proceed with caution and ensure you understand the implications of each action, especially when modifying global variables or granting permissions.
(Perfect for DevOps & SREs)
(Perfect for DevOps & SREs)
