TROUBLESHOOT: ERRO PARA INICIAR MYSQLD (Error: trying to access a stray pointer)

Um dia tive problema para iniciar o mysqld no centos6.9 obtendo o erro abaixo.
Resolvi renomeando para old os arquivos ibdat_1 e ib_logfile0 que se encontram na pasta /var/lib/mysql e tentando iniciar novamente o serviço.

180921  8:26:13  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
180921  8:26:13InnoDB: Error: trying to access a stray pointer 0x80007fd24fc0bff8
InnoDB: buf pool start is at 0x7fd24fbfc000, end at 0x7fd28fffc000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: how to force recovery.
180921  8:26:13  InnoDB: Assertion failure in thread 140542509713376 in file ../../storage/innobase/include/buf0buf.ic line 264
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
11:26:13 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.

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/ [0x7fd29a1c57e0]
/lib64/ [0x7fd2987f9495]
/lib64/ [0x7fd2987fac75]
/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/ [0x7fd2987e5d1d]
/usr/libexec/mysqld() [0x509939]
The manual page at contains
information that should help you find out what is causing the crash.
180921 08:26:13 mysqld_safe mysqld from pid file /var/run/mysqld/ ended


Marcado com , ,

Deixe um comentário

O seu endereço de e-mail não será publicado. Campos obrigatórios são marcados com *