Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.1.9
-
Linux, Ubuntu 14.04
Description
free
|
total used free shared buffers cached
|
Mem: 11989892 11562816 427076 468028 260304 4216848
|
-/+ buffers/cache: 7085664 4904228
|
Swap: 12261372 901968 11359404
|
my.cnf
innodb_buffer_pool_size = 128G
|
2015-12-03 17:16:59 139995792902080 [Note] InnoDB: Initializing buffer pool, size = 128.0G
|
InnoDB: mmap(17716740096 bytes) failed; errno 12
|
2015-12-03 17:17:01 7f534f8187c0 InnoDB: Assertion failure in thread 139995792902080 in file buf0lru.cc line 2240
|
InnoDB: We intentionally generate a memory trap.
|
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
|
InnoDB: If you get repeated assertion failures or crashes, even
|
InnoDB: immediately after the mysqld startup, there may be
|
InnoDB: corruption in the InnoDB tablespace. Please refer to
|
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
|
InnoDB: about forcing recovery.
|
151203 17:17:01 [ERROR] mysqld got signal 6 ;
|
This could be because you hit a bug. It is also possible that this binary
|
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
|
|
We will try our best to scrape up some info that will hopefully help
|
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail.
|
|
Server version: 10.1.9-MariaDB-log
|
key_buffer_size=8388608
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=507
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1121757 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x0x0
|
Attempting backtrace. You can use the following information to find out
|
where mysqld died. If you see no messages after this, something went
|
terribly wrong...
|
stack_bottom = 0x0 thread_stack 0x48000
|
(my_addr_resolve failure: fork)
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld(my_print_stacktrace+0x2e) [0xbf822e]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld(handle_fatal_signal+0x464) [0x760e24]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f534f414340]
|
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7f534dfe1cc9]
|
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f534dfe50d8]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0xa42f7a]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0x95552b]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0xa307aa]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0xa3094d]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0x9d0a59]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0x8fca10]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x5e) [0x766eae]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0x5c0a70]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld(plugin_init(int*, char**, int)+0xbd2) [0x5c27e2]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0x51e5ae]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld(mysqld_main(int, char**)+0x864) [0x51f894]
|
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f534dfccec5]
|
/home/mysql/product/mariadb-10.1.9/bin/mysqld() [0x514879]
|
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
information that should help you find out what is causing the crash.
|
151203 17:17:01 mysqld_safe mysqld from pid file /home/mysql/data/mariadb-10.1.9/laptop4.pid ended
|
Attachments
Issue Links
- relates to
-
MDEV-29445 reorganise innodb buffer pool (and remove buffer pool chunks)
-
- In Review
-
Error 12 does indicate that the memory could not be allocated.
I suppose InnoDB could refuse to startup more nicely, although it's rather usual behavior for InnoDB to go down with assertion failures (not quite crash).
I'll leave it to jplindst to decide if it can and should be fixed somehow.