Unable to start MYSQL service

Issues related to software problems.
Post Reply
tejas5555
Posts: 8
Joined: 2018/02/23 11:33:42

Unable to start MYSQL service

Post by tejas5555 » 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

aks
Posts: 2526
Joined: 2014/09/20 11:22:14

Re: Unable to start MYSQL service

Post by aks » 2018/02/25 14:54:53

Full disk?

tejas5555
Posts: 8
Joined: 2018/02/23 11:33:42

Re: Unable to start MYSQL service

Post by tejas5555 » 2018/02/26 06:10:21

No, Lots of space is left in the disk.
df -lh

Filesystem Size Used Avail Use% Mounted on
/dev/hda1 66G 5.6G 57G 9% /
/dev/hda2 16G 4.2G 11G 29% /var
tmpfs 2.0G 0 2.0G 0% /dev/shm

Devourer
Posts: 12
Joined: 2018/01/29 10:15:59

Re: Unable to start MYSQL service

Post by Devourer » 2018/02/26 20:28:27

You have corrupted database, if it is using innoDB you should try using innodb_recovery
Please take not that you shouldn't go beyond 4 or 5 in recovery, whenever database will be able to start, dump database, see what databases/tables corrupted. Avoid using them and make as much dumps as you can.

Do not perform repairs while you are in recovery mode, just read only actions

tejas5555
Posts: 8
Joined: 2018/02/23 11:33:42

Re: Unable to start MYSQL service

Post by tejas5555 » 2018/02/27 09:12:08

Hi Devourer,
Database is not starting even after using innodb_recovery to level 5. Any other solutions?

Devourer
Posts: 12
Joined: 2018/01/29 10:15:59

Re: Unable to start MYSQL service

Post by Devourer » 2018/02/27 20:28:22

make file-level copy of database data directory and keep increasing, beyond this it is uncertain what outcome there will be, try to scrape as much as you can, can you post logs when starting in recovery ?

User avatar
TrevorH
Forum Moderator
Posts: 23001
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Unable to start MYSQL service

Post by TrevorH » 2018/02/27 21:44:49

Or give up and restore your latest database backup. And if you're doing that, redo it on a supported CentOS release not one that's 1 year past its EOL date and getting steadily less and less secure.
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

tejas5555
Posts: 8
Joined: 2018/02/23 11:33:42

Re: Unable to start MYSQL service

Post by tejas5555 » 2018/02/28 05:10:38

MYSQL Log:-


;InnoDB: End of page dump
180228 10:28:06 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
180228 10:28:06InnoDB: Error: trying to access a stray pointer 0x36b73ff8
InnoDB: buf pool start is at 0xb6b64000, end at 0xb7364000
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.0/en/ ... overy.html
InnoDB: how to force recovery.
180228 10:28:06InnoDB: Assertion failure in thread 3086113024 in file ./../include/buf0buf.ic line 268
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.0/en/ ... overy.html
InnoDB: about forcing recovery.
180228 10:28:06 - mysqld got signal 11 ;
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=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=0xbfdaf278, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x818ec88
0x8432e93
0x83b16fd
0x83bb9fb
0x8369464
Stack trace seems successful - bottom reached
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.
180228 10:28:06 mysqld ended

Devourer
Posts: 12
Joined: 2018/01/29 10:15:59

Re: Unable to start MYSQL service

Post by Devourer » 2018/03/01 09:58:34

Strange thing I can't see mysql whining about starting in recovery mode, maybe variable is wrong, or inserted in wrong config file ?
Make sure directive is in correct field
[mysqld]
innodb_force_recovery = 1

(Try to search for older versions, maybe it was called different, can't remember)

tejas5555
Posts: 8
Joined: 2018/02/23 11:33:42

Re: Unable to start MYSQL service

Post by tejas5555 » 2018/04/03 05:57:51

innodb_force_recovery = 1

It is the exact line which is there in /etc/my.cnf.

Post Reply