Unable to start MYSQL service
Posted: 2018/02/23 11:45:18
Dear all,
I am unable to start MYSQL service in my CENTOS 5.11 server .
Please find the attached logs for your reference.
Your help will be appreciated.
vi /var/log/mysqld.log
180223 16:46:02 mysqld started
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
180223 16:46:02 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: Page directory corruption: supremum not pointed to
180223 16:46:03 InnoDB: Page dump in ascii and hex (16384 bytes):
@
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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...
Cannot determine thread, fp=0xbf848158, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818ec88
0x8432e93
0x83b16fd
0x83bb9fb
0x8369464
0x836ac54
0x83558ee
0x83546e0
0x8261406
0x82503c7
0x818ddc5
0x8191565
0xaeaedc
0x80fc4c1
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using ... trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
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.
180223 16:51:08 mysqld ended
I am unable to start MYSQL service in my CENTOS 5.11 server .
Please find the attached logs for your reference.
Your help will be appreciated.
vi /var/log/mysqld.log
180223 16:46:02 mysqld started
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
180223 16:46:02 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: Page directory corruption: supremum not pointed to
180223 16:46:03 InnoDB: Page dump in ascii and hex (16384 bytes):
@
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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...
Cannot determine thread, fp=0xbf848158, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818ec88
0x8432e93
0x83b16fd
0x83bb9fb
0x8369464
0x836ac54
0x83558ee
0x83546e0
0x8261406
0x82503c7
0x818ddc5
0x8191565
0xaeaedc
0x80fc4c1
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using ... trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
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.
180223 16:51:08 mysqld ended