S
S
Shing2016-01-05 21:37:20
linux
Shing, 2016-01-05 21:37:20

What is this innodb error?

Once a day or more often the muscle lies down.
There is a lot of memory, 32 GB, the load is minuscule on the server.

160105 18:12:19 mysqld_safe Number of processes running now: 0
160105 18:12:19 mysqld_safe mysqld restarted
160105 18:12:19 [Note] /usr/libexec/mysqld (mysqld 5.5.47) starting as process 7375 ...
160105 18:12:19 [Note] Plugin 'FEDERATED' is disabled.
160105 18:12:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160105 18:12:19 InnoDB: Compressed tables use zlib 1.2.3
160105 18:12:19 InnoDB: Using Linux native AIO
160105 18:12:19 InnoDB: Initializing buffer pool, size = 24.0G
InnoDB: mmap(26373783552 bytes) failed; errno 12
160105 18:12:19 InnoDB: Completed initialization of buffer pool
160105 18:12:19 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160105 18:12:19 [ERROR] Plugin 'InnoDB' init function returned error.
160105 18:12:19 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160105 18:12:19 [ERROR] Unknown/unsupported storage engine: innodb
160105 18:12:19 [ERROR] Aborting
160105 18:12:19 [Note] /usr/libexec/mysqld: Shutdown complete
160105 18:12:20 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

my.cnf
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
symbolic-links=0
max_connections=200
max_user_connections=30
key_buffer_size=8G
myisam_sort_buffer_size = 3G
open_files_limit = 100000
wait_timeout=30
interactive_timeout=50
long_query_time=5
skip-name-resolve
#log-queries-not-using-indexes
#log-slow-queries=/var/log/mysql/log-slow-queries.log

#innodb_use_native_aio = 0
innodb_file_per_table
#was added by me, down mysql
innodb=ON 
default-storage-engine=innodb 
innodb_use_sys_malloc=0
innodb_buffer_pool_size=24G

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

Answer the question

In order to leave comments, you need to log in

3 answer(s)
R
romy4, 2016-01-05
@romy4

24 + 8 + 3 is clearly more than 32 gig. reduce the pool to 16.

V
Vlad Zhivotnev, 2016-01-05
@inkvizitor68sl

> 160105 18:12:19 InnoDB: Fatal error: cannot allocate memory for the buffer pool
Not enough memory.
Get mysqltuner.pl and see what it says.

S
Shing, 2016-01-09
@Shing

Nothing works so far... I make some mysqltuner recommendations, but there are no results,
How to defeat cannot allocate memory for the buffer pool in MYSQL?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question