Today, the database has been upgraded, and it has risen to half. It seems that all the data will be imported into the table after the upgrade. As a result, due to the lack of disk space on the server, the server is down, showing a deadlock; restarting the server can not restart successfully;
View logs
[ERROR] The server quit without updating PID file
Go to the data file directory
Internet search results:
Let me delete the mysql-bin.index file and ib -- logfile0 and other related files, I simply delete the mysql-bin.~rec~ file;
Restart to no avail;
Check whether the process is occupied, PS -ef|grep mysqld found that there is no mysqld process
Then it said on the Internet https://blog.csdn.net/u010098331/article/details/50752640
Follow his routine step by step, and found that it is meaningless; it has no effect; it may be because his solution is the solution to the error after modifying the configuration, but mine is down;
Someone asked me to modify the configuration file later
When I restarted with this, I found that there was no log file, which was a bit desperate.
One more count:
It doesn't work either, the result still keeps prompting that the pid file has not been updated
At this time, my friend asked me to use df -h to check the disk space, and I found that the disk of my database was already 100% used.
At this time, I deleted some table data that had no effect and cleaned it up, about 24G of memory
Continue to open the mysql service; however, it does not seem to be of any use;
At this time, I saw Daniel speak again https://www.cnblogs.com/glon/p/6728380.htmlClick to open the link
innodb_force_recovery; the value set in my configuration file itself is 0, and some people say it should be set to 4; I tried 4, but it still doesn't work, it has collapsed after this, and I can't bear it anymore, so I started to restart the server computer. But after thinking about it, restarting the computer should still be a result; urgency makes wisdom; I replaced this with 3 and tried it; the result was OK; the server restarted successfully; but there was a problem with master-slave replication; master-slave replication failed due to InnoDB forced recovery blocking 1881 error;
I deleted my failed table and damaged table; because I made a backup; I changed it back to InnoDB_force_recovery=0 to restart the server, and the master-slave replication is no problem;
You can only upgrade from scratch later;
Working overtime is hard work, but working overtime requires some gains, although