Results 1 to 10 of 11

Thread: mysql crash (stack trace) - corrupt backup

Threaded View

  1. #1
    Join Date
    Jul 2008
    Posts
    27
    Rep Power
    7

    Default SOLVED: mysql crash (stack trace) - corrupt backup

    Hey

    I was able to recover my Zimbra installation from a dying harddisk (RAID1 - both disks were affected and they were not sync).

    I did a fresh install of Zimbra GA 8.03 on a new machine just to be sure everything is ok - it worked.
    Then I replace /opt/zimbra with my restored backup from the failing RAID system. Of course it didn't work immediately so I ran install.sh again just to be sure.
    Now I hit following error in log/mysql_error.log:


    130526 1:36:00 InnoDB: Waiting for the background threads to start
    130526 1:36:01 InnoDB: 1.1.8 started; log sequence number 2268250335
    130526 1:36:01 [Note] Server hostname (bind-address): 'localhost'; port: 7306
    130526 1:36:01 [Note] - 'localhost' resolves to '127.0.0.1';
    130526 1:36:01 [Note] Server socket created on IP: '127.0.0.1'.
    130526 1:36:01 InnoDB: Error: page 1 log sequence number 2368742154
    InnoDB: is in the future! Current system log sequence number 2268250335.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.3.7.2 Forcing InnoDB Recovery
    InnoDB: for more information.
    130526 1:36:02 InnoDB: Error: page 3 log sequence number 2373218620
    InnoDB: is in the future! Current system log sequence number 2268250335.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.3.7.2 Forcing InnoDB Recovery
    InnoDB: for more information.
    130526 1:36:02 InnoDB: Error: page 16 log sequence number 2378797448
    InnoDB: is in the future! Current system log sequence number 2268250335.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.3.7.2 Forcing InnoDB Recovery
    InnoDB: for more information.
    tcmalloc: large alloc 18446744073709543424 bytes == (nil) @
    23:36:02 UTC - 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=8388608
    read_buffer_size=1048576
    max_used_connections=0
    max_threads=110
    thread_count=0
    connection_count=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 234725 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
    /opt/zimbra/mysql/bin/mysqld(my_print_stacktrace+0x29)[0x7a3cd9]
    /opt/zimbra/mysql/bin/mysqld(handle_fatal_signal+0x367)[0x681127]
    /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fb6b2173cb0]
    /opt/zimbra/mysql/bin/mysqld[0x89fe0d]
    /opt/zimbra/mysql/bin/mysqld[0x89ff21]
    /opt/zimbra/mysql/bin/mysqld[0x8a02ad]
    /opt/zimbra/mysql/bin/mysqld[0x7fa491]
    /opt/zimbra/mysql/bin/mysqld[0x7fa509]
    /opt/zimbra/mysql/bin/mysqld[0x7fa71b]
    /opt/zimbra/mysql/bin/mysqld[0x7e4763]
    /opt/zimbra/mysql/bin/mysqld[0x8c5d15]
    /opt/zimbra/mysql/bin/mysqld[0x819b71]
    /opt/zimbra/mysql/bin/mysqld[0x7d7403]
    /opt/zimbra/mysql/bin/mysqld[0x8c5e44]
    /opt/zimbra/mysql/bin/mysqld[0x8c63ce]
    /opt/zimbra/mysql/bin/mysqld[0x8c6b78]
    /opt/zimbra/mysql/bin/mysqld[0x8bc6ed]
    /opt/zimbra/mysql/bin/mysqld[0x7f5367]
    /opt/zimbra/mysql/bin/mysqld[0x7e5cd2]
    /opt/zimbra/mysql/bin/mysqld[0x7ea960]
    /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7fb6b216be9a]
    /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fb6b07e8ccd]
    The manual page at MySQL :: MySQL 5.6 Reference Manual :: C.5.4.2 What to Do If MySQL Keeps Crashing contains
    information that should help you find out what is causing the crash.
    130526 01:36:02 mysqld_safe mysqld from pid file /opt/zimbra/db/mysql.pid ended


    Any ideas? Thanks in advance.


    EDIT: of course I tried to raise the innodb_force_recovery in my.cnf - it did not help, just more (detailed) errors occured in the log file...
    Last edited by juergenmw; 05-27-2013 at 12:23 PM.

Similar Threads

  1. Replies: 13
    Last Post: 03-25-2010, 06:37 AM
  2. Disable hidden stack trace on failed login
    By rhouston in forum Administrators
    Replies: 0
    Last Post: 03-12-2010, 02:15 PM
  3. HTC Magic sync ==> stack trace
    By perbu in forum Zimbra Mobile
    Replies: 12
    Last Post: 08-12-2009, 02:34 AM
  4. [SOLVED] Crash disk and mboxgroup corrupt
    By elibre in forum Administrators
    Replies: 2
    Last Post: 04-12-2009, 01:42 AM
  5. MySQL DB corrupt
    By Urs in forum Installation
    Replies: 3
    Last Post: 11-03-2008, 04:43 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •