"Fix" MYSQL 5.6 Run Crash error
Recently made a cloud host, configured to be 20G disk space, 1G running memory of the Linux server. In the above installed lamp (rhel7.2+apache2.4+mysql5.6+php5.6), and then set up the WordPress site, but the site runs not long, there is no connection to the database. To the server using: Ps-aux |grep MySQL, found that the MySQL service did not run, very puzzled how to run well, they stopped. The following error message is viewed in the next log:
2016-02-20 00:11:03 2762 [Note] innodb:initializing buffer pool, size = 128.0minnodb:mmap (137363456 bytes) failed; errno 122016-02-20 00:11:03 2762 [ERROR] Innodb:cannot allocate memory for the buffer pool2016-02-20 00:11:03 2762 [Error ] Plugin ' InnoDB ' init function returned error.2016-02-20 00:11:03 2762 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.2016-02-20 00:11:03 2762 [ERROR] unknown/unsupported storage engine:innodb2016-02-20 00:11:03 2762 [ERROR] Aborting
From the log information, it is said that the buffer memory is insufficient to cause the service to terminate, I use: free-m view the server memory situation:
Total used free shared Buff/cache availablemem:991 470 461 12 59 423swap:0 0 0
The memory is sufficient to try to start the MySQL service again: /etc/init.d/mysqld The start result has the following error:
Starting MySQL. error! The server quit without updating PID file (/data/mysql/mysql.pid).
Tried several times, can not start, very puzzled.
Try to adjust: the size of the Innodb_buffer_pool_size parameter, but still can not start. Remember before on the virtual machine is also the same environment has not experienced such a problem, the only difference is that the cloud host is not allocated swap partition, is not this problem caused? Then try adding 2G of swap partition.
DD If=/dev/zero Of=/udata/men.swap bs=1k Count=2048000mkswap/udata/men.swapswapon/udata/men.swap
/etc/fstab to join the swap partition
Vim/etc/fstab
Uuid=24357e34-62a1-4645-b3c1-3305c61176e4 swap swap defaults 0 0
Everything is OK, try to start the MySQL service again.
/etc/init.d/mysqld start
Starting MySQL .... success!
It worked.... Is that really the reason .... Observed for a period of time, the failure is not occurring temporarily.
MySQL 5.6 also needs to be optimized .... Also eat memory ah ...
Free-m total used free shared Buff/cache availablemem:991 857 73 0 41swap:1999 670 1329
Later on the foreign site found an article to solve the same problem, the method is the same, the address is as follows:
Http://www.webtrafficexchange.com/solved-mysql-crash-fatal-error-cannot-allocate-memory-buffer-pool
This article is from the "Balich" blog, make sure to keep this source http://balich.blog.51cto.com/6641781/1743622
"Fix" MYSQL 5.6 Run Crash error