Debug Your Infrastructure
Get Instant Solutions for Kubernetes, Databases, Docker and more
MySQL 1236: Cannot access partition.
When encountering the error 1236: Cannot access partition in MySQL, follow these steps:
- Verify MySQL server's running status:
systemctl status mysql
- Check MySQL error logs for specifics about the partition access issue. The location can vary, but commonly:
tail -100 /var/log/mysql/error.log
- Ensure that the MySQL user has the necessary permissions to access the partition. Check permissions with:
SHOW GRANTS FOR 'yourmysqluser'@'your_host';
- If the error is related to MySQL replication and the partition refers to a binary log partition, investigate the binary log status:
SHOW BINARY LOGS;
and check the last successfully executed binary log file and position:SHOW SLAVE STATUS\G
- If necessary, reset the master to the correct binary log file and position on the slave (replace `logfile` and `logpos` with the actual values):
STOP SLAVE;
CHANGE MASTER TO MASTERLOGFILE='logfile', MASTERLOGPOS=logpos;
START SLAVE;
- Check disk space and permissions on the partition where MySQL stores its data files, typically `/var/lib/mysql`:
df -h
ls -ld /var/lib/mysql
- If the partition is full, free up space or expand the partition. If permissions are incorrect, adjust them (replace `mysql` with the actual MySQL user and group):
chown mysql:mysql /var/lib/mysql -R
chmod 755 /var/lib/mysql
- Restart MySQL service to apply any changes:
systemctl restart mysql
- Finally, check MySQL's status to ensure it's running without errors:
systemctl status mysql
Only proceed with actions you are comfortable executing and understand the implications of, especially when adjusting file permissions or manipulating binary logs.
Master
MySQL
debugging in Minutes
— Grab the Ultimate Cheatsheet
(Perfect for DevOps & SREs)
MySQL
Cheatsheet
(Perfect for DevOps & SREs)
MORE ISSUES
Backed by
