InnoDB: ###### Diagnostic info printed to the standard error stream InnoDB: Error: semaphore wait has lasted > 600 seconds InnoDB: We intentionally crash the server, because it appears to be hung. 070912 16:41:01InnoDB: Assertion failure in thread 680463280 in file srv0srv.c line 2093 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/forcing-recovery.html InnoDB: about forcing recovery. 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=33554432 read_buffer_size=2093056 max_used_connections=92 max_connections=100 threads_connected=84 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1056367 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=0x288f00fc, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x817e950 0x829484d 0x5c2371 0x52cffe New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trac e. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 070912 16:41:01 mysqld restarted 070912 16:41: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... 070912 16:41:03 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 912 2696540359. InnoDB: Doing recovery: scanned up to log sequence number 912 2701783040 InnoDB: Doing recovery: scanned up to log sequence number 912 2707025920 InnoDB: Doing recovery: scanned up to log sequence number 912 2712268800 InnoDB: Doing recovery: scanned up to log sequence number 912 2717511680 InnoDB: Doing recovery: scanned up to log sequence number 912 2722754560 InnoDB: Doing recovery: scanned up to log sequence number 912 2727997440 InnoDB: Doing recovery: scanned up to log sequence number 912 2733240320 InnoDB: Doing recovery: scanned up to log sequence number 912 2738483200 InnoDB: Doing recovery: scanned up to log sequence number 912 2743726080 InnoDB: Doing recovery: scanned up to log sequence number 912 2748968960 InnoDB: Doing recovery: scanned up to log sequence number 912 2754211840 InnoDB: Doing recovery: scanned up to log sequence number 912 2759454720 InnoDB: Doing recovery: scanned up to log sequence number 912 2764697600 InnoDB: Doing recovery: scanned up to log sequence number 912 2769940480 InnoDB: Doing recovery: scanned up to log sequence number 912 2775183360 InnoDB: Doing recovery: scanned up to log sequence number 912 2780426240 InnoDB: Doing recovery: scanned up to log sequence number 912 2785669120 InnoDB: Doing recovery: scanned up to log sequence number 912 2790912000 InnoDB: Doing recovery: scanned up to log sequence number 912 2796154880 InnoDB: Doing recovery: scanned up to log sequence number 912 2801397760 InnoDB: Doing recovery: scanned up to log sequence number 912 2806640640 InnoDB: Doing recovery: scanned up to log sequence number 912 2811883520 InnoDB: Doing recovery: scanned up to log sequence number 912 2817126400 InnoDB: Doing recovery: scanned up to log sequence number 912 2822369280 InnoDB: Doing recovery: scanned up to log sequence number 912 2827612160 InnoDB: Doing recovery: scanned up to log sequence number 912 2832855040 InnoDB: Doing recovery: scanned up to log sequence number 912 2838097920 InnoDB: Doing recovery: scanned up to log sequence number 912 2843340800 InnoDB: Doing recovery: scanned up to log sequence number 912 2848583680 InnoDB: Doing recovery: scanned up to log sequence number 912 2853826560 InnoDB: Doing recovery: scanned up to log sequence number 912 2859069440 InnoDB: Doing recovery: scanned up to log sequence number 912 2864312320 InnoDB: Doing recovery: scanned up to log sequence number 912 2869555200 InnoDB: Doing recovery: scanned up to log sequence number 912 2874798080 InnoDB: Doing recovery: scanned up to log sequence number 912 2880040960 InnoDB: Doing recovery: scanned up to log sequence number 912 2885283840 InnoDB: Doing recovery: scanned up to log sequence number 912 2890526720 InnoDB: Doing recovery: scanned up to log sequence number 912 2895769600 InnoDB: Doing recovery: scanned up to log sequence number 912 2901012480 InnoDB: Doing recovery: scanned up to log sequence number 912 2906255360 InnoDB: Doing recovery: scanned up to log sequence number 912 2911498240 InnoDB: Doing recovery: scanned up to log sequence number 912 2916741120 InnoDB: Doing recovery: scanned up to log sequence number 912 2921984000 InnoDB: Doing recovery: scanned up to log sequence number 912 2927226880 InnoDB: Doing recovery: scanned up to log sequence number 912 2932469760 InnoDB: Doing recovery: scanned up to log sequence number 912 2937712640 InnoDB: Doing recovery: scanned up to log sequence number 912 2942955520 InnoDB: Doing recovery: scanned up to log sequence number 912 2948198400 InnoDB: Doing recovery: scanned up to log sequence number 912 2953441280 InnoDB: Doing recovery: scanned up to log sequence number 912 2958684160 InnoDB: Doing recovery: scanned up to log sequence number 912 2963927040 InnoDB: Doing recovery: scanned up to log sequence number 912 2969169920 InnoDB: Doing recovery: scanned up to log sequence number 912 2974412800 InnoDB: Doing recovery: scanned up to log sequence number 912 2979655680 InnoDB: Doing recovery: scanned up to log sequence number 912 2984898560 InnoDB: Doing recovery: scanned up to log sequence number 912 2990141440 InnoDB: Doing recovery: scanned up to log sequence number 912 2995384320 InnoDB: Doing recovery: scanned up to log sequence number 912 3000627200 InnoDB: Doing recovery: scanned up to log sequence number 912 3005870080 InnoDB: Doing recovery: scanned up to log sequence number 912 3011112960 InnoDB: Doing recovery: scanned up to log sequence number 912 3016355840 InnoDB: Doing recovery: scanned up to log sequence number 912 3021598720 InnoDB: Doing recovery: scanned up to log sequence number 912 3026841600 InnoDB: Doing recovery: scanned up to log sequence number 912 3032084480 InnoDB: Doing recovery: scanned up to log sequence number 912 3037327360 InnoDB: Doing recovery: scanned up to log sequence number 912 3042570240 InnoDB: Doing recovery: scanned up to log sequence number 912 3047813120 InnoDB: Doing recovery: scanned up to log sequence number 912 3053056000 InnoDB: Doing recovery: scanned up to log sequence number 912 3058298880 InnoDB: Doing recovery: scanned up to log sequence number 912 3063541760 InnoDB: Doing recovery: scanned up to log sequence number 912 3068784640 InnoDB: Doing recovery: scanned up to log sequence number 912 3074027520 InnoDB: Doing recovery: scanned up to log sequence number 912 3079270400 InnoDB: Doing recovery: scanned up to log sequence number 912 3084513280 InnoDB: Doing recovery: scanned up to log sequence number 912 3089756160 InnoDB: Doing recovery: scanned up to log sequence number 912 3094999040 InnoDB: Doing recovery: scanned up to log sequence number 912 3100241920 InnoDB: Doing recovery: scanned up to log sequence number 912 3105484800 InnoDB: Doing recovery: scanned up to log sequence number 912 3110727680 InnoDB: Doing recovery: scanned up to log sequence number 912 3115970560 InnoDB: Doing recovery: scanned up to log sequence number 912 3121213440 InnoDB: Doing recovery: scanned up to log sequence number 912 3126456320 InnoDB: Doing recovery: scanned up to log sequence number 912 3131699200 InnoDB: Doing recovery: scanned up to log sequence number 912 3136942080 InnoDB: Doing recovery: scanned up to log sequence number 912 3142184960 InnoDB: Doing recovery: scanned up to log sequence number 912 3147427840 InnoDB: Doing recovery: scanned up to log sequence number 912 3152670720 InnoDB: Doing recovery: scanned up to log sequence number 912 3157913600 InnoDB: Doing recovery: scanned up to log sequence number 912 3163156480 InnoDB: Doing recovery: scanned up to log sequence number 912 3168399360 InnoDB: Doing recovery: scanned up to log sequence number 912 3173642240 InnoDB: Doing recovery: scanned up to log sequence number 912 3178885120 InnoDB: Doing recovery: scanned up to log sequence number 912 3184128000 InnoDB: Doing recovery: scanned up to log sequence number 912 3189370880 InnoDB: Doing recovery: scanned up to log sequence number 912 3194613760 InnoDB: Doing recovery: scanned up to log sequence number 912 3199856640 InnoDB: Doing recovery: scanned up to log sequence number 912 3205099520 InnoDB: Doing recovery: scanned up to log sequence number 912 3210342400 InnoDB: Doing recovery: scanned up to log sequence number 912 3215585280 InnoDB: Doing recovery: scanned up to log sequence number 912 3220828160 InnoDB: Doing recovery: scanned up to log sequence number 912 3226071040 InnoDB: Doing recovery: scanned up to log sequence number 912 3231313920 InnoDB: Doing recovery: scanned up to log sequence number 912 3236556800 InnoDB: Doing recovery: scanned up to log sequence number 912 3241799680 InnoDB: Doing recovery: scanned up to log sequence number 912 3247042560 InnoDB: Doing recovery: scanned up to log sequence number 912 3252285440 InnoDB: Doing recovery: scanned up to log sequence number 912 3257528320 InnoDB: Doing recovery: scanned up to log sequence number 912 3260144100 070912 16:42:19 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 070912 16:49:54 InnoDB: Started; log sequence number 912 3260144100