Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1.5
-
None
-
10.1.7-1
Description
Create database using file-key-management plugin, shutdown, and restart with example-key-management plugin and you will get following crash:
BROKEN: block: 3400 checkpoint: 5 4227c7bc c45826ac
|
BROKEN: block: 3400 checkpoint: 5 4227c7bc c45826ac
|
InnoDB: Log block no 3400 at lsn 1740288 has
|
InnoDB: ok header, but checksum field contains 3294111404, should be 1109903292
|
InnoDB: Set innodb_force_recovery to ignore this error.
|
2015-07-02 10:06:35 7fa8eae9b780 InnoDB: Assertion failure in thread 140363472418688 in file log0recv.cc line 2833
|
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.
|
150702 10:06:35 [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.6-MariaDB-debug
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=153
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467186 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
|
addr2line: 'sql/mysqld': No such file
|
sql/mysqld(my_print_stacktrace+0x38)[0x7fa8ebc025be]
|
sql/mysqld(handle_fatal_signal+0x34c)[0x7fa8eb5ea603]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fa8e93bf340]
|
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7fa8e8a16cc9]
|
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa8e8a1a0d8]
|
sql/mysqld(+0xa92add)[0x7fa8eb96aadd]
|
sql/mysqld(+0xa93045)[0x7fa8eb96b045]
|
sql/mysqld(+0xa93839)[0x7fa8eb96b839]
|
sql/mysqld(+0xb74289)[0x7fa8eba4c289]
|
sql/mysqld(+0xa0c21f)[0x7fa8eb8e421f]
|
sql/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0xf3)[0x7fa8eb5ec55a]
|
sql/mysqld(+0x4fec05)[0x7fa8eb3d6c05]
|
sql/mysqld(_Z11plugin_initPiPPci+0x8e5)[0x7fa8eb3d77c8]
|
sql/mysqld(+0x3e37ba)[0x7fa8eb2bb7ba]
|
sql/mysqld(_Z11mysqld_mainiPPc+0x5f3)[0x7fa8eb2bc750]
|
sql/mysqld(main+0x20)[0x7fa8eb2b21d5]
|
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fa8e8a01ec5]
|
sql/mysqld(+0x3da0c8)[0x7fa8eb2b20c8]
|
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.
|
Attachments
Issue Links
- blocks
-
-
- Closed
-
Activity
Note that creating database using example-key-management plugin, shutdown and restart with file-key-management plugin does print error message and InnoDB refuses to start. This is naturally because used key_id (timestamp) is not found from used keys. If it would, you would see similar crashes as above.
If you have innodb-encrypt-log=OFF you will have different kind of crash:
InnoDB: Database page corruption on disk or a failedInnoDB: space 0 file ./ibdata1 read of page 7.InnoDB: You may have to recover from a backup.2015-07-02 10:11:29 7f026eeaf780 InnoDB: Page dump in ascii and hex (16384 bytes):len 16384; hex 455013d400000007000000000000000000000000001a8....InnoDB: End of page dump2015-07-02 10:11:29 7f026eeaf780 InnoDB: uncompressed page, stored checksum in field1 1162875860, calculated checksums for field1: crc32 2554652115, innodb 1484047458, none 3735928559, stored checksum in field2 624286960, calculated checksums for field2: crc32 2554652115, innodb 624286960, none 3735928559, page LSN 0 1739463, low 4 bytes of LSN at page end 1739463, page number (if stored to page already) 7, space id (if created with >= MySQL-4.1.1 and stored already) 0InnoDB: page type 393216 meaning PAGE TYPE CORRUPTEDInnoDB: Page may be a system pageInnoDB: Database page corruption on disk or a failedInnoDB: file read of page 7.InnoDB: You may have to recover from a backup.InnoDB: It is also possible that your operatingInnoDB: system has corrupted its own file cacheInnoDB: and rebooting your computer removes theInnoDB: error.InnoDB: If the corrupt page is an index pageInnoDB: you can also try to fix the corruptionInnoDB: by dumping, dropping, and reimportingInnoDB: the corrupt table. You can use CHECKInnoDB: TABLE to scan your table for corruption.InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.htmlInnoDB: about forcing recovery.InnoDB: Ending processing because of a corrupt database page.2015-07-02 10:11:29 7f026eeaf780 InnoDB: Assertion failure in thread 139648427554688 in file buf0buf.cc line 4513InnoDB: 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, evenInnoDB: immediately after the mysqld startup, there may beInnoDB: corruption in the InnoDB tablespace. Please refer toInnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.htmlInnoDB: about forcing recovery.150702 10:11:29 [ERROR] mysqld got signal 6 ;This could be because you hit a bug. It is also possible that this binaryor 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-bugsWe will try our best to scrape up some info that will hopefully helpdiagnose the problem, but since we have already crashed,something is definitely wrong and this may fail.