[Solution] MySql 5.6 run crash Error

[Solution] MySql 5.6 run crash Error

[Solution] MySql 5.6 run crash Error

Recently, a VM instance is configured with 20 GB disk space and 1 GB memory for Linux servers. Install LAMP (RHEL7.2 + Apache2.4 + MySql5.6 + PHP5.6) on the above and build a wordpress website. However, the website will not be able to connect to the database for a long time. Use ps-aux | grep mysql on the server. I found that the MySql service was not running. I was wondering how to run it well and I stopped it myself. The following error message is displayed:

2016-02-2000:11:032762[Note]InnoDB:Initializingbufferpool,size=128.0MInnoDB:mmap(137363456bytes)failed;errno122016-02-2000:11:032762[ERROR]InnoDB:Cannotallocatememoryforthebufferpool2016-02-2000:11:032762[ERROR]Plugin'InnoDB'initfunctionreturnederror.2016-02-2000:11:032762[ERROR]Plugin'InnoDB'registrationasaSTORAGEENGINEfailed.2016-02-2000:11:032762[ERROR]Unknown/unsupportedstorageengine:InnoDB2016-02-2000:11:032762[ERROR]Aborting

According to the log information, the service is terminated due to insufficient memory in the buffer zone. I used: free-m to check the memory of the server:

totalusedfreesharedbuff/cacheavailableMem:9914704611259423Swap:000

The memory is sufficient. The following error occurs when you try to start the MySql service again:/etc/init. d/mysqld start:

StartingMySQL..ERROR!TheserverquitwithoutupdatingPIDfile(/data/mysql/mysql.pid).

I tried it several times and couldn't start it. I'm wondering.

Try to adjust: The innodb_buffer_pool_size parameter, but it still cannot be started. I remember that this problem has never been encountered in the same environment on the VM. The only difference is that no swap partition is allocated on this VM instance. Is this problem caused? Add 2 GB swap partition for a try.

ddif=/dev/zeroof=/udata/men.swapbs=1kcount=2048000mkswap/udata/men.swapswapon/udata/men.swap

Add/etc/fstab to the swap Partition

Vim/etc/fstab

UUID=24357e34-62a1-4645-b3c1-3305c61176e4swapswapdefaults00

Everything is okay. Try to start the MySQL service again.

/etc/init.d/mysqldstart

Starting MySQL... SUCCESS!

Success .... Is that why .... After observing for a period of time, there is no fault at the moment.

MySQL 5.6 also needs optimization .... Memory consumption...

free-mtotalusedfreesharedbuff/cacheavailableMem:9918577306041Swap:19996701329

Later, I found an article on a foreign website to solve the same problem in the same way. The address is as follows:

Http://www.webtrafficexchange.com/solved-mysql-crash-fatal-error-cannot-allocate-memory-buffer-pool