[Akonadi] [Bug 366213] akonadi server not starting

Rex Dieter via KDE Bugzilla bugzilla_noreply at kde.org
Mon Aug 22 13:23:40 BST 2016


https://bugs.kde.org/show_bug.cgi?id=366213

--- Comment #8 from Rex Dieter <rdieter at math.unl.edu> ---
In this case, mysql is failing to start, and the output suggests that your db
is possibly corrupt and/or to file a bug with them.

InnoDB: Error: trying to access page number 4160743807 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
160729  9:29:06  InnoDB: Assertion failure in thread 140621652350848 in file
fil0fil.c line 4578
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:29:06 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list