Bug #90658 Mysql failed to start
Submitted: 27 Apr 2018 6:12 Modified: 27 Apr 2018 7:59
Reporter: Tejas Gandhi Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:Ver 14.14 Distrib 5.1.73 OS:Linux
Assigned to: CPU Architecture:x86
Tags: Mysql server failed to start

[27 Apr 2018 6:12] Tejas Gandhi
Description:
Configuration file output:-

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
max_allowed_packet=100M

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

Log file output:- ;InnoDB: End of page dump
180427 11:38:31  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
180427 11:38:31InnoDB: Error: trying to access a stray pointer 0x80007f4d0d41bff8
InnoDB: buf pool start is at 0x7f4d0d40c000, end at 0x7f4d0dc0c000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: how to force recovery.
180427 11:38:31  InnoDB: Assertion failure in thread 139968994772960 in file ../../storage/innobase/include/buf0buf.ic line 264
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:08:31 UTC - 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.
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.

key_buffer_size=8384512
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338336 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x29) [0x850ca9]
/usr/libexec/mysqld(handle_fatal_signal+0x483) [0x6a4143]
/lib64/libpthread.so.0(+0xf7e0) [0x7f4d11f4d7e0]
/lib64/libc.so.6(gsignal+0x35) [0x7f4d10581495]
/lib64/libc.so.6(abort+0x175) [0x7f4d10582c75]
/usr/libexec/mysqld(page_cur_search_with_match+0x77b) [0x79855b]
/usr/libexec/mysqld(btr_cur_search_to_nth_level+0x6ea) [0x73bd9a]
/usr/libexec/mysqld(btr_pcur_open_on_user_rec+0x64) [0x7eab34]
/usr/libexec/mysqld() [0x75a46f]
/usr/libexec/mysqld(dict_load_sys_table+0x59) [0x7602d9]
/usr/libexec/mysqld(dict_boot+0x91c) [0x7ebf6c]
/usr/libexec/mysqld(innobase_start_or_create_for_mysql+0x11f6) [0x7c8466]
/usr/libexec/mysqld() [0x72f84b]
/usr/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x697b91]
/usr/libexec/mysqld() [0x7177db]
/usr/libexec/mysqld(plugin_init(int*, char**, int)+0x6e4) [0x719ad4]
/usr/libexec/mysqld() [0x5bf242]
/usr/libexec/mysqld(main+0x1b3) [0x5c1bb3]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7f4d1056dd1d]
/usr/libexec/mysqld() [0x509939]
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.
180427 11:38:31 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

How to repeat:
No idea.
[27 Apr 2018 7:59] Miguel Solorzano
Thank you for taking the time to report a problem.  Unfortunately you
are not using a current version of the product you reported a problem
with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/.

Also, there is no test case provided in the bug report and hence there
is nothing we can verify here.  If you are able to reproduce the bug
with one of the latest versions, please attach the exact reproducible
test case and change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for your
continued support of MySQL.