Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

MySQL not starting - InnoDB: Assertion failure
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

MySQL not starting - InnoDB: Assertion failure

JunklessJunkless Member
edited February 2017 in Help


Mysql on this VPS (cpanel) crashed suddenly last night and is refusing to start back up since then. Here is what the log file says :

2017-02-07 07:02:10 5219 [Note] Plugin 'FEDERATED' is disabled.
2017-02-07 07:02:10 5219 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-02-07 07:02:10 5219 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-07 07:02:10 5219 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-02-07 07:02:10 5219 [Note] InnoDB: Memory barrier is not used
2017-02-07 07:02:10 5219 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-07 07:02:10 5219 [Note] InnoDB: Using Linux native AIO
2017-02-07 07:02:10 5219 [Note] InnoDB: Using CPU crc32 instructions
2017-02-07 07:02:10 5219 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-02-07 07:02:10 5219 [Note] InnoDB: Completed initialization of buffer pool
2017-02-07 07:02:10 5219 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-07 07:02:10 5219 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 5852545548 in the ib_logfiles!
2017-02-07 07:02:10 5219 [Note] InnoDB: Database was not shutdown normally!
2017-02-07 07:02:10 5219 [Note] InnoDB: Starting crash recovery.
2017-02-07 07:02:10 5219 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-07 07:02:11 5219 [Note] InnoDB: Restoring possible half-written data pages
2017-02-07 07:02:11 5219 [Note] InnoDB: from the doublewrite buffer...
2017-02-07 07:02:11 7fafe4252720 InnoDB: Assertion failure in thread 140393423644448 in file line 1868
InnoDB: Failing assertion: inode
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.
05:02:11 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 = 68108 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
The manual page at contains
information that should help you find out what is causing the crash

Any pointers on how to get it sorted ?


  • Sounds like some kind of file corruption. Do you have important data in it that you want to recover?

  • @willie said:
    Sounds like some kind of file corruption. Do you have important data in it that you want to recover?

    Depends, will everything be gone ?

  • Google gives quite a few results regarding this error message, can you try this: ?

  • Junkless said: Depends, will everything be gone ?

    If you have good backups or are just screwing around with the db, it's simplest to just blow away everything and start over. Otherwise you get to start clicking around and trying stuff. Make a copy of everything before doing anything potentially destructive. I've never dealt with innodb at that level but have done stuff like this with other db's etc. It's partly a matter of determination.

  • To play it very safe, take a copy of the datadir + innodb log and ibdata files while mysqld is off.

    Run the recovery as per instructions. The log files should contain enough information so that MySQL can backtrack transactions and walk back through them. It can take a while for large (tens of GB) databases.

Sign In or Register to comment.