Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Won't Fix
-
5.5.35
-
None
-
None
-
RHEL7.0 on Power8(BigEndian)
mariadb-server-5.5.35-3.el7
Description
As mariadb err log described, the worst case come from "140812 1:15:39":
mariadb crashed, might due to a SQL clause.
Then mariadb auto-restart->recover innodb->failure->crash again.
Full mariadb start-crash log as below:
================================================================================
|
140812 01:18:35 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
|
140812 1:18:35 [Warning] option 'old_passwords': boolean value 'y' wasn't recognized. Set to OFF.
|
140812 1:18:35 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
|
140812 1:18:35 InnoDB: The InnoDB memory heap is disabled
|
140812 1:18:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
140812 1:18:35 InnoDB: Compressed tables use zlib 1.2.7
|
140812 1:18:35 InnoDB: Using Linux native AIO
|
140812 1:18:35 InnoDB: Initializing buffer pool, size = 60.9G
|
140812 1:18:39 InnoDB: Completed initialization of buffer pool
|
140812 1:18:39 InnoDB: highest supported file format is Barracuda.
|
InnoDB: Log scan progressed past the checkpoint lsn 496728560
|
140812 1:18:39 InnoDB: Database was not shut down normally!
|
InnoDB: Starting crash recovery.
|
InnoDB: Reading tablespace information from the .ibd files...
|
InnoDB: Restoring possible half-written data pages from the doublewrite
|
InnoDB: buffer...
|
InnoDB: Doing recovery: scanned up to log sequence number 501970944
|
InnoDB: Doing recovery: scanned up to log sequence number 507213824
|
InnoDB: Doing recovery: scanned up to log sequence number 512456704
|
InnoDB: Doing recovery: scanned up to log sequence number 517699584
|
InnoDB: Doing recovery: scanned up to log sequence number 522942464
|
InnoDB: Doing recovery: scanned up to log sequence number 528185344
|
InnoDB: Doing recovery: scanned up to log sequence number 533428224
|
InnoDB: Doing recovery: scanned up to log sequence number 538671104
|
InnoDB: Doing recovery: scanned up to log sequence number 539354177
|
140812 1:18:43 InnoDB: Starting an apply batch of log records to the database...
|
InnoDB: Progress in percents: 140812 1:18:43 InnoDB: Assertion failure in thread 70297494876336 in file data0type.ic line 488
|
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.5/en/forcing-innodb-recovery.html
|
InnoDB: about forcing recovery.
|
140812 1:18:43 [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: 5.5.35-MariaDB-log
|
key_buffer_size=268435456
|
read_buffer_size=2097152
|
max_used_connections=0
|
max_threads=302
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1504516 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
|
/usr/libexec/mysqld(my_print_stacktrace-0x4bfca8)[0x40cd0398]
|
/usr/libexec/mysqld(handle_fatal_signal-0x983f20)[0x407e02a0]
|
[0x3fff81d50478]
|
/lib64/power8/libc.so.6(abort-0x182984)[0x3fff81470084]
|
/usr/libexec/mysqld(+0x898008)[0x40a98008]
|
/usr/libexec/mysqld(+0x916184)[0x40b16184]
|
/usr/libexec/mysqld(+0x903f7c)[0x40b03f7c]
|
/usr/libexec/mysqld(+0x90699c)[0x40b0699c]
|
/usr/libexec/mysqld(+0x86c5bc)[0x40a6c5bc]
|
/usr/libexec/mysqld(+0x8bc1b8)[0x40abc1b8]
|
/usr/libexec/mysqld(+0x808bc8)[0x40a08bc8]
|
/lib64/power8/libpthread.so.0(+0xc460)[0x3fff81d0c460]
|
/lib64/power8/libc.so.6(clone-0xb9448)[0x3fff8153ebf0]
|
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.
|
140812 01:18:43 mysqld_safe mysqld from pid file /var/lib/mysql/c931f07p10.pid ended
|