121017 13:22:25 [Warning] Aborted connection 44656588 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got timeout reading communication packets)
121017 13:22:25 [Warning] Aborted connection 44655081 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got timeout reading communication packets)
121017 13:22:46 [Warning] Aborted connection 44657664 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got timeout reading communication packets)
121017 13:22:51 [Warning] Aborted connection 44658031 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:22:51 [Warning] Aborted connection 44657992 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:22:51 [Warning] Aborted connection 44658030 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:22:51 [Warning] Aborted connection 44658022 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:22:51 [Warning] Aborted connection 44658010 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:22:51 [Warning] Aborted connection 44657998 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:22:51 [Warning] Aborted connection 44658000 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:05 [Warning] Aborted connection 44655082 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got timeout reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44657997 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658082 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658049 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658067 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658048 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658066 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658051 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658052 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658055 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:19 [Warning] Aborted connection 44658053 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:37 [Warning] Aborted connection 44658104 to db: 'quadrant' user: 'writer' host: '172.16.78.47' (Got an error reading communication packets)
121017 13:23:46 [Warning] Aborted connection 44658092 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:46 [Warning] Aborted connection 44658105 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:46 [Warning] Aborted connection 44658094 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:46 [Warning] Aborted connection 44658093 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:23:49 [Warning] Aborted connection 44657945 to db: 'quadrant' user: 'writer' host: '172.16.78.46' (Got an error reading communication packets)
121017 13:23:49 [Warning] Aborted connection 44658024 to db: 'quadrant' user: 'writer' host: '172.16.78.46' (Got an error reading communication packets)
121017 13:23:49 [Warning] Aborted connection 44658054 to db: 'quadrant' user: 'writer' host: '172.16.78.46' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658113 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658215 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658214 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658107 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658213 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658181 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658180 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658179 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658176 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658175 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658177 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658174 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658173 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:22 [Warning] Aborted connection 44658119 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:24:51 [Warning] Aborted connection 44657848 to db: 'quadrant' user: 'writer' host: '172.16.78.46' (Got timeout reading communication packets)
121017 13:25:00 [Warning] Aborted connection 44658220 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:25:00 [Warning] Aborted connection 44658293 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:25:00 [Warning] Aborted connection 44658292 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:25:00 [Warning] Aborted connection 44658295 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:25:00 [Warning] Aborted connection 44658270 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:25:00 [Warning] Aborted connection 44658252 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:25:00 [Warning] Aborted connection 44658275 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:25:00 [Warning] Aborted connection 44658268 to db: 'quadrant' user: 'writer' host: '172.16.78.48' (Got an error reading communication packets)
121017 13:25:10 [Warning] Aborted connection 44658106 to db: 'quadrant' user: 'writer' host: '172.16.78.46' (Got an error reading communication packets)
121017 13:25:10 [Warning] Aborted connection 44658223 to db: 'quadrant' user: 'writer' host: '172.16.78.46' (Got an error reading communication packets)
121017 13:25:10 [Warning] Aborted connection 44658297 to db: 'quadrant' user: 'writer' host: '172.16.78.46' (Got an error reading communication packets)
121017 13:25:20  InnoDB: Assertion failure in thread 1566763360 in file /export/home/pb2/build/sb_0-3159149-1301580870.56/mysql-5.5.11/storage/innobase/ibuf/ibuf0ibuf.c line 4130
InnoDB: Failing assertion: page_get_n_recs(page) > 1
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.
121017 13:25:20 - 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.

key_buffer_size=1073741824
read_buffer_size=4194304
max_used_connections=643
max_threads=500
thread_count=304
connection_count=304
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5155958 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 = (nil) thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x39)[0x795f29]
/usr/local/mysql/bin/mysqld(handle_segfault+0x380)[0x4fce00]
/lib64/tls/libpthread.so.0[0x32df10c5b0]
/lib64/tls/libc.so.6(gsignal+0x3d)[0x32de62e26d]
/lib64/tls/libc.so.6(abort+0xfe)[0x32de62fa6e]
/usr/local/mysql/bin/mysqld[0x86cd2d]
/usr/local/mysql/bin/mysqld[0x8224c1]
/usr/local/mysql/bin/mysqld[0x83163e]
/usr/local/mysql/bin/mysqld[0x831b37]
/usr/local/mysql/bin/mysqld[0x823540]
/usr/local/mysql/bin/mysqld[0x80cd3c]
/usr/local/mysql/bin/mysqld[0x80f4e4]
/usr/local/mysql/bin/mysqld[0x7ca5c7]
/usr/local/mysql/bin/mysqld[0x8b00e6]
/usr/local/mysql/bin/mysqld[0x8b058e]
/usr/local/mysql/bin/mysqld[0x8b0dbd]
/usr/local/mysql/bin/mysqld[0x8a6b4d]
/usr/local/mysql/bin/mysqld[0x7e8e35]
/usr/local/mysql/bin/mysqld[0x7def9c]
/lib64/tls/libpthread.so.0[0x32df106137]
/lib64/tls/libc.so.6(__clone+0x73)[0x32de6c9883]
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.
mysqld: /export/home/pb2/build/sb_0-3159149-1301580870.56/mysql-5.5.11/mysys/my_new.cc:51: int __cxa_pure_virtual(): Assertion `! "Aborted: pure virtual method called."' failed.
mysqld: /export/home/pb2/build/sb_0-3159149-1301580870.56/mysql-5.5.11/mysys/my_new.cc:51: int __cxa_pure_virtual(): Assertion `! "Aborted: pure virtual method called."' failed.
121017 13:25:25 mysqld_safe Number of processes running now: 0
121017 13:25:25 mysqld_safe mysqld restarted
121017 13:25:26 [Note] Plugin 'FEDERATED' is disabled.
121017 13:25:26 InnoDB: The InnoDB memory heap is disabled
121017 13:25:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121017 13:25:26 InnoDB: Compressed tables use zlib 1.2.3
121017 13:25:26 InnoDB: Using Linux native AIO
121017 13:25:26 InnoDB: Initializing buffer pool, size = 13.0G
121017 13:25:27 InnoDB: Completed initialization of buffer pool
121017 13:25:27 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 16191973909557
121017 13:25:27  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: Doing recovery: scanned up to log sequence number 16191979152384
InnoDB: Doing recovery: scanned up to log sequence number 16191984395264
InnoDB: Doing recovery: scanned up to log sequence number 16191989638144
InnoDB: Doing recovery: scanned up to log sequence number 16191994881024
InnoDB: Doing recovery: scanned up to log sequence number 16192000123904
InnoDB: Doing recovery: scanned up to log sequence number 16192005366784
InnoDB: Doing recovery: scanned up to log sequence number 16192010609664
InnoDB: Doing recovery: scanned up to log sequence number 16192015852544
InnoDB: Doing recovery: scanned up to log sequence number 16192021095424
InnoDB: Doing recovery: scanned up to log sequence number 16192026338304
InnoDB: Doing recovery: scanned up to log sequence number 16192031581184
InnoDB: Doing recovery: scanned up to log sequence number 16192036824064
InnoDB: Doing recovery: scanned up to log sequence number 16192042066944
InnoDB: Doing recovery: scanned up to log sequence number 16192047309824
InnoDB: Doing recovery: scanned up to log sequence number 16192052552704
InnoDB: Doing recovery: scanned up to log sequence number 16192057795584
InnoDB: Doing recovery: scanned up to log sequence number 16192063038464
InnoDB: Doing recovery: scanned up to log sequence number 16192068281344
InnoDB: Doing recovery: scanned up to log sequence number 16192073524224
InnoDB: Doing recovery: scanned up to log sequence number 16192078767104
InnoDB: Doing recovery: scanned up to log sequence number 16192084009984
InnoDB: Doing recovery: scanned up to log sequence number 16192089252864
InnoDB: Doing recovery: scanned up to log sequence number 16192094495744
InnoDB: Doing recovery: scanned up to log sequence number 16192099738624
InnoDB: Doing recovery: scanned up to log sequence number 16192104981504
InnoDB: Doing recovery: scanned up to log sequence number 16192110224384
InnoDB: Doing recovery: scanned up to log sequence number 16192115467264
InnoDB: Doing recovery: scanned up to log sequence number 16192120710144
InnoDB: Doing recovery: scanned up to log sequence number 16192125953024
InnoDB: Doing recovery: scanned up to log sequence number 16192131195904
InnoDB: Doing recovery: scanned up to log sequence number 16192136438784
InnoDB: Doing recovery: scanned up to log sequence number 16192141681664
InnoDB: Doing recovery: scanned up to log sequence number 16192146924544
InnoDB: Doing recovery: scanned up to log sequence number 16192152167424
InnoDB: Doing recovery: scanned up to log sequence number 16192157410304
InnoDB: Doing recovery: scanned up to log sequence number 16192162653184
InnoDB: Doing recovery: scanned up to log sequence number 16192167896064
InnoDB: Doing recovery: scanned up to log sequence number 16192173138944
InnoDB: Doing recovery: scanned up to log sequence number 16192178381824
InnoDB: Doing recovery: scanned up to log sequence number 16192183624704
InnoDB: Doing recovery: scanned up to log sequence number 16192188867584
InnoDB: Doing recovery: scanned up to log sequence number 16192194110464
InnoDB: Doing recovery: scanned up to log sequence number 16192199353344
InnoDB: Doing recovery: scanned up to log sequence number 16192204596224
InnoDB: Doing recovery: scanned up to log sequence number 16192209839104
InnoDB: Doing recovery: scanned up to log sequence number 16192215081984
InnoDB: Doing recovery: scanned up to log sequence number 16192220324864
InnoDB: Doing recovery: scanned up to log sequence number 16192225567744
InnoDB: Doing recovery: scanned up to log sequence number 16192230810624
InnoDB: Doing recovery: scanned up to log sequence number 16192236053504
InnoDB: Doing recovery: scanned up to log sequence number 16192241296384
InnoDB: Doing recovery: scanned up to log sequence number 16192246539264
InnoDB: Doing recovery: scanned up to log sequence number 16192251782144
InnoDB: Doing recovery: scanned up to log sequence number 16192257025024
InnoDB: Doing recovery: scanned up to log sequence number 16192262267904
InnoDB: Doing recovery: scanned up to log sequence number 16192267510784
InnoDB: Doing recovery: scanned up to log sequence number 16192272753664
InnoDB: Doing recovery: scanned up to log sequence number 16192277996544
InnoDB: Doing recovery: scanned up to log sequence number 16192283239424
InnoDB: Doing recovery: scanned up to log sequence number 16192288482304
InnoDB: Doing recovery: scanned up to log sequence number 16192293725184
InnoDB: Doing recovery: scanned up to log sequence number 16192298968064
InnoDB: Doing recovery: scanned up to log sequence number 16192304210944
InnoDB: Doing recovery: scanned up to log sequence number 16192309453824
InnoDB: Doing recovery: scanned up to log sequence number 16192314696704
InnoDB: Doing recovery: scanned up to log sequence number 16192319939584
InnoDB: Doing recovery: scanned up to log sequence number 16192325182464
InnoDB: Doing recovery: scanned up to log sequence number 16192330425344
InnoDB: Doing recovery: scanned up to log sequence number 16192335668224
InnoDB: Doing recovery: scanned up to log sequence number 16192340911104
InnoDB: Doing recovery: scanned up to log sequence number 16192346153984
InnoDB: Doing recovery: scanned up to log sequence number 16192351396864
InnoDB: Doing recovery: scanned up to log sequence number 16192356639744
InnoDB: Doing recovery: scanned up to log sequence number 16192361882624
InnoDB: Doing recovery: scanned up to log sequence number 16192367125504
InnoDB: Doing recovery: scanned up to log sequence number 16192372368384
InnoDB: Doing recovery: scanned up to log sequence number 16192377611264
InnoDB: Doing recovery: scanned up to log sequence number 16192382854144
InnoDB: Doing recovery: scanned up to log sequence number 16192388097024
InnoDB: Doing recovery: scanned up to log sequence number 16192393339904
InnoDB: Doing recovery: scanned up to log sequence number 16192398582784
InnoDB: Doing recovery: scanned up to log sequence number 16192403825664
InnoDB: Doing recovery: scanned up to log sequence number 16192409068544
InnoDB: Doing recovery: scanned up to log sequence number 16192414311424
InnoDB: Doing recovery: scanned up to log sequence number 16192419554304
InnoDB: Doing recovery: scanned up to log sequence number 16192424797184
InnoDB: Doing recovery: scanned up to log sequence number 16192430040064
InnoDB: Doing recovery: scanned up to log sequence number 16192435282944
InnoDB: Doing recovery: scanned up to log sequence number 16192440525824
InnoDB: Doing recovery: scanned up to log sequence number 16192445768704
InnoDB: Doing recovery: scanned up to log sequence number 16192451011584
InnoDB: Doing recovery: scanned up to log sequence number 16192456254464
InnoDB: Doing recovery: scanned up to log sequence number 16192461497344
InnoDB: Doing recovery: scanned up to log sequence number 16192466740224
InnoDB: Doing recovery: scanned up to log sequence number 16192471983104
InnoDB: Doing recovery: scanned up to log sequence number 16192477225984
InnoDB: Doing recovery: scanned up to log sequence number 16192482468864
InnoDB: Doing recovery: scanned up to log sequence number 16192487711744
InnoDB: Doing recovery: scanned up to log sequence number 16192492954624
InnoDB: Doing recovery: scanned up to log sequence number 16192498197504
InnoDB: Doing recovery: scanned up to log sequence number 16192503440384
InnoDB: Doing recovery: scanned up to log sequence number 16192508683264
InnoDB: Doing recovery: scanned up to log sequence number 16192513926144
InnoDB: Doing recovery: scanned up to log sequence number 16192519169024
InnoDB: Doing recovery: scanned up to log sequence number 16192524411904
InnoDB: Doing recovery: scanned up to log sequence number 16192529654784
InnoDB: Doing recovery: scanned up to log sequence number 16192534897664
InnoDB: Doing recovery: scanned up to log sequence number 16192540140544
InnoDB: Doing recovery: scanned up to log sequence number 16192545383424
InnoDB: Doing recovery: scanned up to log sequence number 16192550626304
InnoDB: Doing recovery: scanned up to log sequence number 16192555869184
InnoDB: Doing recovery: scanned up to log sequence number 16192561112064
InnoDB: Doing recovery: scanned up to log sequence number 16192566354944
InnoDB: Doing recovery: scanned up to log sequence number 16192571597824
InnoDB: Doing recovery: scanned up to log sequence number 16192576840704
InnoDB: Doing recovery: scanned up to log sequence number 16192582083584
InnoDB: Doing recovery: scanned up to log sequence number 16192587326464
InnoDB: Doing recovery: scanned up to log sequence number 16192592569344
InnoDB: Doing recovery: scanned up to log sequence number 16192597812224
InnoDB: Doing recovery: scanned up to log sequence number 16192603055104
InnoDB: Doing recovery: scanned up to log sequence number 16192608297984
InnoDB: Doing recovery: scanned up to log sequence number 16192613540864
InnoDB: Doing recovery: scanned up to log sequence number 16192618783744
InnoDB: Doing recovery: scanned up to log sequence number 16192624026624
InnoDB: Doing recovery: scanned up to log sequence number 16192629269504
InnoDB: Doing recovery: scanned up to log sequence number 16192634512384
InnoDB: Doing recovery: scanned up to log sequence number 16192639755264
InnoDB: Doing recovery: scanned up to log sequence number 16192644998144
InnoDB: Doing recovery: scanned up to log sequence number 16192650241024
InnoDB: Doing recovery: scanned up to log sequence number 16192655483904
InnoDB: Doing recovery: scanned up to log sequence number 16192660726784
InnoDB: Doing recovery: scanned up to log sequence number 16192665969664
InnoDB: Doing recovery: scanned up to log sequence number 16192671212544
InnoDB: Doing recovery: scanned up to log sequence number 16192676455424
InnoDB: Doing recovery: scanned up to log sequence number 16192681698304
InnoDB: Doing recovery: scanned up to log sequence number 16192686941184
InnoDB: Doing recovery: scanned up to log sequence number 16192692184064
InnoDB: Doing recovery: scanned up to log sequence number 16192697426944
InnoDB: Doing recovery: scanned up to log sequence number 16192702669824
InnoDB: Doing recovery: scanned up to log sequence number 16192707912704
InnoDB: Doing recovery: scanned up to log sequence number 16192713155584
InnoDB: Doing recovery: scanned up to log sequence number 16192718398464
InnoDB: Doing recovery: scanned up to log sequence number 16192723641344
InnoDB: Doing recovery: scanned up to log sequence number 16192728884224
InnoDB: Doing recovery: scanned up to log sequence number 16192734127104
InnoDB: Doing recovery: scanned up to log sequence number 16192739369984
InnoDB: Doing recovery: scanned up to log sequence number 16192744612864
InnoDB: Doing recovery: scanned up to log sequence number 16192749855744
InnoDB: Doing recovery: scanned up to log sequence number 16192755098624
InnoDB: Doing recovery: scanned up to log sequence number 16192760341504
InnoDB: Doing recovery: scanned up to log sequence number 16192765584384
InnoDB: Doing recovery: scanned up to log sequence number 16192770827264
InnoDB: Doing recovery: scanned up to log sequence number 16192776070144
InnoDB: Doing recovery: scanned up to log sequence number 16192781313024
InnoDB: Doing recovery: scanned up to log sequence number 16192786555904
InnoDB: Doing recovery: scanned up to log sequence number 16192791798784
InnoDB: Doing recovery: scanned up to log sequence number 16192797041664
InnoDB: Doing recovery: scanned up to log sequence number 16192802284544
InnoDB: Doing recovery: scanned up to log sequence number 16192807527424
InnoDB: Doing recovery: scanned up to log sequence number 16192812770304
InnoDB: Doing recovery: scanned up to log sequence number 16192818013184
InnoDB: Doing recovery: scanned up to log sequence number 16192823256064
InnoDB: Doing recovery: scanned up to log sequence number 16192828498944
InnoDB: Doing recovery: scanned up to log sequence number 16192833741824
InnoDB: Doing recovery: scanned up to log sequence number 16192838984704
InnoDB: Doing recovery: scanned up to log sequence number 16192844227584
InnoDB: Doing recovery: scanned up to log sequence number 16192849470464
InnoDB: Doing recovery: scanned up to log sequence number 16192854713344
InnoDB: Doing recovery: scanned up to log sequence number 16192859956224
InnoDB: Doing recovery: scanned up to log sequence number 16192865199104
InnoDB: Doing recovery: scanned up to log sequence number 16192870441984
InnoDB: Doing recovery: scanned up to log sequence number 16192875684864
InnoDB: Doing recovery: scanned up to log sequence number 16192880927744
InnoDB: Doing recovery: scanned up to log sequence number 16192886170624
InnoDB: Doing recovery: scanned up to log sequence number 16192891413504
InnoDB: Doing recovery: scanned up to log sequence number 16192896656384
InnoDB: Doing recovery: scanned up to log sequence number 16192901899264
InnoDB: Doing recovery: scanned up to log sequence number 16192907142144
InnoDB: Doing recovery: scanned up to log sequence number 16192912385024
InnoDB: Doing recovery: scanned up to log sequence number 16192917627904
InnoDB: Doing recovery: scanned up to log sequence number 16192922870784
InnoDB: Doing recovery: scanned up to log sequence number 16192928113664
InnoDB: Doing recovery: scanned up to log sequence number 16192933356544
InnoDB: Doing recovery: scanned up to log sequence number 16192938599424
InnoDB: Doing recovery: scanned up to log sequence number 16192943842304
InnoDB: Doing recovery: scanned up to log sequence number 16192949085184
InnoDB: Doing recovery: scanned up to log sequence number 16192954328064
InnoDB: Doing recovery: scanned up to log sequence number 16192959570944
InnoDB: Doing recovery: scanned up to log sequence number 16192964813824
InnoDB: Doing recovery: scanned up to log sequence number 16192970056704
InnoDB: Doing recovery: scanned up to log sequence number 16192975299584
InnoDB: Doing recovery: scanned up to log sequence number 16192980542464
InnoDB: Doing recovery: scanned up to log sequence number 16192985785344
InnoDB: Doing recovery: scanned up to log sequence number 16192991028224
InnoDB: Doing recovery: scanned up to log sequence number 16192996271104
InnoDB: Doing recovery: scanned up to log sequence number 16193001513984
InnoDB: Doing recovery: scanned up to log sequence number 16193006756864
InnoDB: Doing recovery: scanned up to log sequence number 16193011999744
InnoDB: Doing recovery: scanned up to log sequence number 16193017242624
InnoDB: Doing recovery: scanned up to log sequence number 16193022485504
InnoDB: Doing recovery: scanned up to log sequence number 16193027728384
InnoDB: Doing recovery: scanned up to log sequence number 16193032971264
InnoDB: Doing recovery: scanned up to log sequence number 16193038214144
InnoDB: Doing recovery: scanned up to log sequence number 16193043457024
InnoDB: Doing recovery: scanned up to log sequence number 16193048699904
InnoDB: Doing recovery: scanned up to log sequence number 16193053942784
InnoDB: Doing recovery: scanned up to log sequence number 16193059185664
InnoDB: Doing recovery: scanned up to log sequence number 16193064428544
InnoDB: Doing recovery: scanned up to log sequence number 16193069671424
InnoDB: Doing recovery: scanned up to log sequence number 16193074914304
InnoDB: Doing recovery: scanned up to log sequence number 16193080157184
InnoDB: Doing recovery: scanned up to log sequence number 16193085400064
InnoDB: Doing recovery: scanned up to log sequence number 16193090642944
InnoDB: Doing recovery: scanned up to log sequence number 16193095885824
InnoDB: Doing recovery: scanned up to log sequence number 16193101128704
InnoDB: Doing recovery: scanned up to log sequence number 16193106371584
InnoDB: Doing recovery: scanned up to log sequence number 16193111614464
InnoDB: Doing recovery: scanned up to log sequence number 16193116857344
InnoDB: Doing recovery: scanned up to log sequence number 16193122100224
InnoDB: Doing recovery: scanned up to log sequence number 16193127343104
InnoDB: Doing recovery: scanned up to log sequence number 16193132585984
InnoDB: Doing recovery: scanned up to log sequence number 16193137828864
InnoDB: Doing recovery: scanned up to log sequence number 16193143071744
InnoDB: Doing recovery: scanned up to log sequence number 16193148314624
InnoDB: Doing recovery: scanned up to log sequence number 16193153557504
InnoDB: Doing recovery: scanned up to log sequence number 16193158800384
InnoDB: Doing recovery: scanned up to log sequence number 16193164043264
InnoDB: Doing recovery: scanned up to log sequence number 16193169286144
InnoDB: Doing recovery: scanned up to log sequence number 16193174529024
InnoDB: Doing recovery: scanned up to log sequence number 16193179771904
InnoDB: Doing recovery: scanned up to log sequence number 16193185014784
InnoDB: Doing recovery: scanned up to log sequence number 16193190257664
InnoDB: Doing recovery: scanned up to log sequence number 16193195500544
InnoDB: Doing recovery: scanned up to log sequence number 16193200743424
InnoDB: Doing recovery: scanned up to log sequence number 16193205986304
InnoDB: Doing recovery: scanned up to log sequence number 16193211229184
InnoDB: Doing recovery: scanned up to log sequence number 16193216472064
InnoDB: Doing recovery: scanned up to log sequence number 16193221714944
InnoDB: Doing recovery: scanned up to log sequence number 16193226957824
InnoDB: Doing recovery: scanned up to log sequence number 16193232200704
InnoDB: Doing recovery: scanned up to log sequence number 16193237443584
InnoDB: Doing recovery: scanned up to log sequence number 16193242686464
InnoDB: Doing recovery: scanned up to log sequence number 16193247929344
InnoDB: Doing recovery: scanned up to log sequence number 16193253172224
InnoDB: Doing recovery: scanned up to log sequence number 16193258415104
InnoDB: Doing recovery: scanned up to log sequence number 16193263657984
InnoDB: Doing recovery: scanned up to log sequence number 16193268900864
InnoDB: Doing recovery: scanned up to log sequence number 16193274143744
InnoDB: Doing recovery: scanned up to log sequence number 16193279386624
InnoDB: Doing recovery: scanned up to log sequence number 16193284629504
InnoDB: Doing recovery: scanned up to log sequence number 16193289872384
InnoDB: Doing recovery: scanned up to log sequence number 16193295115264
InnoDB: Doing recovery: scanned up to log sequence number 16193300358144
InnoDB: Doing recovery: scanned up to log sequence number 16193305601024
InnoDB: Doing recovery: scanned up to log sequence number 16193310843904
InnoDB: Doing recovery: scanned up to log sequence number 16193316086784
InnoDB: Doing recovery: scanned up to log sequence number 16193321329664
InnoDB: Doing recovery: scanned up to log sequence number 16193326572544
InnoDB: Doing recovery: scanned up to log sequence number 16193331815424
InnoDB: Doing recovery: scanned up to log sequence number 16193337058304
InnoDB: Doing recovery: scanned up to log sequence number 16193342301184
InnoDB: Doing recovery: scanned up to log sequence number 16193347544064
InnoDB: Doing recovery: scanned up to log sequence number 16193352786944
InnoDB: Doing recovery: scanned up to log sequence number 16193358029824
InnoDB: Doing recovery: scanned up to log sequence number 16193363272704
InnoDB: Doing recovery: scanned up to log sequence number 16193368515584
InnoDB: Doing recovery: scanned up to log sequence number 16193373758464
InnoDB: Doing recovery: scanned up to log sequence number 16193379001344
InnoDB: Doing recovery: scanned up to log sequence number 16193384244224
InnoDB: Doing recovery: scanned up to log sequence number 16193389487104
InnoDB: Doing recovery: scanned up to log sequence number 16193394729984
InnoDB: Doing recovery: scanned up to log sequence number 16193399972864
InnoDB: Doing recovery: scanned up to log sequence number 16193405215744
InnoDB: Doing recovery: scanned up to log sequence number 16193410458624
InnoDB: Doing recovery: scanned up to log sequence number 16193415701504
InnoDB: Doing recovery: scanned up to log sequence number 16193420944384
InnoDB: Doing recovery: scanned up to log sequence number 16193426187264
InnoDB: Doing recovery: scanned up to log sequence number 16193431430144
InnoDB: Doing recovery: scanned up to log sequence number 16193436673024
InnoDB: Doing recovery: scanned up to log sequence number 16193441915904
InnoDB: Doing recovery: scanned up to log sequence number 16193447158784
InnoDB: Doing recovery: scanned up to log sequence number 16193452401664
InnoDB: Doing recovery: scanned up to log sequence number 16193457644544
InnoDB: Doing recovery: scanned up to log sequence number 16193462887424
InnoDB: Doing recovery: scanned up to log sequence number 16193468130304
InnoDB: Doing recovery: scanned up to log sequence number 16193473373184
InnoDB: Doing recovery: scanned up to log sequence number 16193478616064
InnoDB: Doing recovery: scanned up to log sequence number 16193483858944
InnoDB: Doing recovery: scanned up to log sequence number 16193489101824
InnoDB: Doing recovery: scanned up to log sequence number 16193494344704
InnoDB: Doing recovery: scanned up to log sequence number 16193499587584
InnoDB: Doing recovery: scanned up to log sequence number 16193504830464
InnoDB: Doing recovery: scanned up to log sequence number 16193510073344
InnoDB: Doing recovery: scanned up to log sequence number 16193515316224
InnoDB: Doing recovery: scanned up to log sequence number 16193520559104
InnoDB: Doing recovery: scanned up to log sequence number 16193525801984
InnoDB: Doing recovery: scanned up to log sequence number 16193531044864
InnoDB: Doing recovery: scanned up to log sequence number 16193536287744
InnoDB: Doing recovery: scanned up to log sequence number 16193541530624
InnoDB: Doing recovery: scanned up to log sequence number 16193546773504
InnoDB: Doing recovery: scanned up to log sequence number 16193552016384
InnoDB: Doing recovery: scanned up to log sequence number 16193557259264
InnoDB: Doing recovery: scanned up to log sequence number 16193562502144
InnoDB: Doing recovery: scanned up to log sequence number 16193567745024
InnoDB: Doing recovery: scanned up to log sequence number 16193572987904
InnoDB: Doing recovery: scanned up to log sequence number 16193578230784
InnoDB: Doing recovery: scanned up to log sequence number 16193583473664
InnoDB: Doing recovery: scanned up to log sequence number 16193588716544
InnoDB: Doing recovery: scanned up to log sequence number 16193593959424
InnoDB: Doing recovery: scanned up to log sequence number 16193599202304
InnoDB: Doing recovery: scanned up to log sequence number 16193604445184
InnoDB: Doing recovery: scanned up to log sequence number 16193609688064
InnoDB: Doing recovery: scanned up to log sequence number 16193614930944
InnoDB: Doing recovery: scanned up to log sequence number 16193620173824
InnoDB: Doing recovery: scanned up to log sequence number 16193625416704
InnoDB: Doing recovery: scanned up to log sequence number 16193630659584
InnoDB: Doing recovery: scanned up to log sequence number 16193635902464
InnoDB: Doing recovery: scanned up to log sequence number 16193641145344
InnoDB: Doing recovery: scanned up to log sequence number 16193646388224
InnoDB: Doing recovery: scanned up to log sequence number 16193651631104
InnoDB: Doing recovery: scanned up to log sequence number 16193656873984
InnoDB: Doing recovery: scanned up to log sequence number 16193662116864
InnoDB: Doing recovery: scanned up to log sequence number 16193667359744
InnoDB: Doing recovery: scanned up to log sequence number 16193672602624
InnoDB: Doing recovery: scanned up to log sequence number 16193677845504
InnoDB: Doing recovery: scanned up to log sequence number 16193683088384
InnoDB: Doing recovery: scanned up to log sequence number 16193688331264
InnoDB: Doing recovery: scanned up to log sequence number 16193693574144
InnoDB: Doing recovery: scanned up to log sequence number 16193698817024
InnoDB: Doing recovery: scanned up to log sequence number 16193704059904
InnoDB: Doing recovery: scanned up to log sequence number 16193709302784
InnoDB: Doing recovery: scanned up to log sequence number 16193714545664
InnoDB: Doing recovery: scanned up to log sequence number 16193719788544
InnoDB: Doing recovery: scanned up to log sequence number 16193725031424
InnoDB: Doing recovery: scanned up to log sequence number 16193730274304
InnoDB: Doing recovery: scanned up to log sequence number 16193735517184
InnoDB: Doing recovery: scanned up to log sequence number 16193740760064
InnoDB: Doing recovery: scanned up to log sequence number 16193746002944
InnoDB: Doing recovery: scanned up to log sequence number 16193751245824
InnoDB: Doing recovery: scanned up to log sequence number 16193756488704
InnoDB: Doing recovery: scanned up to log sequence number 16193761731584
InnoDB: Doing recovery: scanned up to log sequence number 16193766974464
InnoDB: Doing recovery: scanned up to log sequence number 16193772217344
InnoDB: Doing recovery: scanned up to log sequence number 16193777460224
InnoDB: Doing recovery: scanned up to log sequence number 16193782703104
InnoDB: Doing recovery: scanned up to log sequence number 16193787945984
InnoDB: Doing recovery: scanned up to log sequence number 16193793188864
InnoDB: Doing recovery: scanned up to log sequence number 16193798431744
InnoDB: Doing recovery: scanned up to log sequence number 16193803674624
InnoDB: Doing recovery: scanned up to log sequence number 16193808917504
InnoDB: Doing recovery: scanned up to log sequence number 16193814160384
InnoDB: Doing recovery: scanned up to log sequence number 16193819403264
InnoDB: Doing recovery: scanned up to log sequence number 16193824646144
InnoDB: Doing recovery: scanned up to log sequence number 16193829889024
InnoDB: Doing recovery: scanned up to log sequence number 16193835131904
InnoDB: Doing recovery: scanned up to log sequence number 16193840374784
InnoDB: Doing recovery: scanned up to log sequence number 16193845617664
InnoDB: Doing recovery: scanned up to log sequence number 16193850860544
InnoDB: Doing recovery: scanned up to log sequence number 16193856103424
InnoDB: Doing recovery: scanned up to log sequence number 16193861346304
InnoDB: Doing recovery: scanned up to log sequence number 16193866589184
InnoDB: Doing recovery: scanned up to log sequence number 16193871832064
InnoDB: Doing recovery: scanned up to log sequence number 16193877074944
InnoDB: Doing recovery: scanned up to log sequence number 16193882317824
InnoDB: Doing recovery: scanned up to log sequence number 16193887560704
InnoDB: Doing recovery: scanned up to log sequence number 16193892803584
InnoDB: Doing recovery: scanned up to log sequence number 16193898046464
InnoDB: Doing recovery: scanned up to log sequence number 16193903289344
InnoDB: Doing recovery: scanned up to log sequence number 16193908532224
InnoDB: Doing recovery: scanned up to log sequence number 16193913775104
InnoDB: Doing recovery: scanned up to log sequence number 16193919017984
InnoDB: Doing recovery: scanned up to log sequence number 16193924260864
InnoDB: Doing recovery: scanned up to log sequence number 16193929503744
InnoDB: Doing recovery: scanned up to log sequence number 16193934746624
InnoDB: Doing recovery: scanned up to log sequence number 16193939989504
InnoDB: Doing recovery: scanned up to log sequence number 16193945232384
InnoDB: Doing recovery: scanned up to log sequence number 16193950475264
InnoDB: Doing recovery: scanned up to log sequence number 16193955718144
InnoDB: Doing recovery: scanned up to log sequence number 16193960961024
InnoDB: Doing recovery: scanned up to log sequence number 16193966203904
InnoDB: Doing recovery: scanned up to log sequence number 16193971446784
InnoDB: Doing recovery: scanned up to log sequence number 16193976689664
InnoDB: Doing recovery: scanned up to log sequence number 16193981932544
InnoDB: Doing recovery: scanned up to log sequence number 16193987175424
InnoDB: Doing recovery: scanned up to log sequence number 16193992418304
InnoDB: Doing recovery: scanned up to log sequence number 16193997661184
InnoDB: Doing recovery: scanned up to log sequence number 16194002904064
InnoDB: Doing recovery: scanned up to log sequence number 16194008146944
InnoDB: Doing recovery: scanned up to log sequence number 16194013389824
InnoDB: Doing recovery: scanned up to log sequence number 16194018632704
InnoDB: Doing recovery: scanned up to log sequence number 16194023875584
InnoDB: Doing recovery: scanned up to log sequence number 16194029118464
InnoDB: Doing recovery: scanned up to log sequence number 16194034361344
InnoDB: Doing recovery: scanned up to log sequence number 16194039604224
InnoDB: Doing recovery: scanned up to log sequence number 16194044847104
InnoDB: Doing recovery: scanned up to log sequence number 16194050089984
InnoDB: Doing recovery: scanned up to log sequence number 16194055332864
InnoDB: Doing recovery: scanned up to log sequence number 16194060575744
InnoDB: Doing recovery: scanned up to log sequence number 16194065818624
InnoDB: Doing recovery: scanned up to log sequence number 16194071061504
InnoDB: Doing recovery: scanned up to log sequence number 16194076304384
InnoDB: Doing recovery: scanned up to log sequence number 16194081547264
InnoDB: Doing recovery: scanned up to log sequence number 16194086790144
InnoDB: Doing recovery: scanned up to log sequence number 16194092033024
InnoDB: Doing recovery: scanned up to log sequence number 16194097275904
InnoDB: Doing recovery: scanned up to log sequence number 16194102518784
InnoDB: Doing recovery: scanned up to log sequence number 16194107761664
InnoDB: Doing recovery: scanned up to log sequence number 16194113004544
InnoDB: Doing recovery: scanned up to log sequence number 16194118247424
InnoDB: Doing recovery: scanned up to log sequence number 16194123490304
InnoDB: Doing recovery: scanned up to log sequence number 16194128733184
InnoDB: Doing recovery: scanned up to log sequence number 16194133976064
InnoDB: Doing recovery: scanned up to log sequence number 16194139218944
InnoDB: Doing recovery: scanned up to log sequence number 16194144461824
InnoDB: Doing recovery: scanned up to log sequence number 16194149704704
InnoDB: Doing recovery: scanned up to log sequence number 16194154947584
InnoDB: Doing recovery: scanned up to log sequence number 16194160190464
InnoDB: Doing recovery: scanned up to log sequence number 16194165433344
InnoDB: Doing recovery: scanned up to log sequence number 16194170676224
InnoDB: Doing recovery: scanned up to log sequence number 16194175919104
InnoDB: Doing recovery: scanned up to log sequence number 16194181161984
InnoDB: Doing recovery: scanned up to log sequence number 16194186404864
InnoDB: Doing recovery: scanned up to log sequence number 16194191647744
InnoDB: Doing recovery: scanned up to log sequence number 16194196890624
InnoDB: Doing recovery: scanned up to log sequence number 16194202133504
InnoDB: Doing recovery: scanned up to log sequence number 16194207376384
InnoDB: Doing recovery: scanned up to log sequence number 16194208283296
InnoDB: 3 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 6 row operations to undo
InnoDB: Trx id counter is E15B0BE00
121017 13:28:25  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 121017 13:29:16  InnoDB: Assertion failure in thread 1262557536 in file /export/home/pb2/build/sb_0-3159149-1301580870.56/mysql-5.5.11/storage/innobase/ibuf/ibuf0ibuf.c line 4130
InnoDB: Failing assertion: page_get_n_recs(page) > 1
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.
121017 13:29:16 - 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.

key_buffer_size=1073741824
read_buffer_size=4194304
max_used_connections=0
max_threads=500
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 = 5150267 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 = (nil) thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x39)[0x795f29]
/usr/local/mysql/bin/mysqld(handle_segfault+0x380)[0x4fce00]
/lib64/tls/libpthread.so.0[0x32df10c5b0]
/lib64/tls/libc.so.6(gsignal+0x3d)[0x32de62e26d]
/lib64/tls/libc.so.6(abort+0xfe)[0x32de62fa6e]
/usr/local/mysql/bin/mysqld[0x86cd2d]
/usr/local/mysql/bin/mysqld[0x8224c1]
/usr/local/mysql/bin/mysqld[0x853cc0]
/usr/local/mysql/bin/mysqld[0x7dfdc0]
/lib64/tls/libpthread.so.0[0x32df106137]
/lib64/tls/libc.so.6(__clone+0x73)[0x32de6c9883]
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.
121017 13:29:17 mysqld_safe mysqld from pid file /opt/mysql/data1/q3-db1.webtech.local.pid ended
121017 13:38:52 mysqld_safe Starting mysqld daemon with databases from /opt/mysql/data1
121017 13:38:52 [Note] Plugin 'FEDERATED' is disabled.
121017 13:38:52 InnoDB: The InnoDB memory heap is disabled
121017 13:38:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121017 13:38:52 InnoDB: Compressed tables use zlib 1.2.3
121017 13:38:52 InnoDB: Using Linux native AIO
121017 13:38:52 InnoDB: Initializing buffer pool, size = 13.0G
121017 13:38:54 InnoDB: Completed initialization of buffer pool
121017 13:38:54 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 16191973909557
121017 13:38:54  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: Doing recovery: scanned up to log sequence number 16191979152384
InnoDB: Doing recovery: scanned up to log sequence number 16191984395264
InnoDB: Doing recovery: scanned up to log sequence number 16191989638144
InnoDB: Doing recovery: scanned up to log sequence number 16191994881024
InnoDB: Doing recovery: scanned up to log sequence number 16192000123904
InnoDB: Doing recovery: scanned up to log sequence number 16192005366784
InnoDB: Doing recovery: scanned up to log sequence number 16192010609664
InnoDB: Doing recovery: scanned up to log sequence number 16192015852544
InnoDB: Doing recovery: scanned up to log sequence number 16192021095424
InnoDB: Doing recovery: scanned up to log sequence number 16192026338304
InnoDB: Doing recovery: scanned up to log sequence number 16192031581184
InnoDB: Doing recovery: scanned up to log sequence number 16192036824064
InnoDB: Doing recovery: scanned up to log sequence number 16192042066944
InnoDB: Doing recovery: scanned up to log sequence number 16192047309824
InnoDB: Doing recovery: scanned up to log sequence number 16192052552704
InnoDB: Doing recovery: scanned up to log sequence number 16192057795584
InnoDB: Doing recovery: scanned up to log sequence number 16192063038464
InnoDB: Doing recovery: scanned up to log sequence number 16192068281344
InnoDB: Doing recovery: scanned up to log sequence number 16192073524224
InnoDB: Doing recovery: scanned up to log sequence number 16192078767104
InnoDB: Doing recovery: scanned up to log sequence number 16192084009984
InnoDB: Doing recovery: scanned up to log sequence number 16192089252864
InnoDB: Doing recovery: scanned up to log sequence number 16192094495744
InnoDB: Doing recovery: scanned up to log sequence number 16192099738624
InnoDB: Doing recovery: scanned up to log sequence number 16192104981504
InnoDB: Doing recovery: scanned up to log sequence number 16192110224384
InnoDB: Doing recovery: scanned up to log sequence number 16192115467264
InnoDB: Doing recovery: scanned up to log sequence number 16192120710144
InnoDB: Doing recovery: scanned up to log sequence number 16192125953024
InnoDB: Doing recovery: scanned up to log sequence number 16192131195904
InnoDB: Doing recovery: scanned up to log sequence number 16192136438784
InnoDB: Doing recovery: scanned up to log sequence number 16192141681664
InnoDB: Doing recovery: scanned up to log sequence number 16192146924544
InnoDB: Doing recovery: scanned up to log sequence number 16192152167424
InnoDB: Doing recovery: scanned up to log sequence number 16192157410304
InnoDB: Doing recovery: scanned up to log sequence number 16192162653184
InnoDB: Doing recovery: scanned up to log sequence number 16192167896064
InnoDB: Doing recovery: scanned up to log sequence number 16192173138944
InnoDB: Doing recovery: scanned up to log sequence number 16192178381824
InnoDB: Doing recovery: scanned up to log sequence number 16192183624704
InnoDB: Doing recovery: scanned up to log sequence number 16192188867584
InnoDB: Doing recovery: scanned up to log sequence number 16192194110464
InnoDB: Doing recovery: scanned up to log sequence number 16192199353344
InnoDB: Doing recovery: scanned up to log sequence number 16192204596224
InnoDB: Doing recovery: scanned up to log sequence number 16192209839104
InnoDB: Doing recovery: scanned up to log sequence number 16192215081984
InnoDB: Doing recovery: scanned up to log sequence number 16192220324864
InnoDB: Doing recovery: scanned up to log sequence number 16192225567744
InnoDB: Doing recovery: scanned up to log sequence number 16192230810624
InnoDB: Doing recovery: scanned up to log sequence number 16192236053504
InnoDB: Doing recovery: scanned up to log sequence number 16192241296384
InnoDB: Doing recovery: scanned up to log sequence number 16192246539264
InnoDB: Doing recovery: scanned up to log sequence number 16192251782144
InnoDB: Doing recovery: scanned up to log sequence number 16192257025024
InnoDB: Doing recovery: scanned up to log sequence number 16192262267904
InnoDB: Doing recovery: scanned up to log sequence number 16192267510784
InnoDB: Doing recovery: scanned up to log sequence number 16192272753664
InnoDB: Doing recovery: scanned up to log sequence number 16192277996544
InnoDB: Doing recovery: scanned up to log sequence number 16192283239424
InnoDB: Doing recovery: scanned up to log sequence number 16192288482304
InnoDB: Doing recovery: scanned up to log sequence number 16192293725184
InnoDB: Doing recovery: scanned up to log sequence number 16192298968064
InnoDB: Doing recovery: scanned up to log sequence number 16192304210944
InnoDB: Doing recovery: scanned up to log sequence number 16192309453824
InnoDB: Doing recovery: scanned up to log sequence number 16192314696704
InnoDB: Doing recovery: scanned up to log sequence number 16192319939584
InnoDB: Doing recovery: scanned up to log sequence number 16192325182464
InnoDB: Doing recovery: scanned up to log sequence number 16192330425344
InnoDB: Doing recovery: scanned up to log sequence number 16192335668224
InnoDB: Doing recovery: scanned up to log sequence number 16192340911104
InnoDB: Doing recovery: scanned up to log sequence number 16192346153984
InnoDB: Doing recovery: scanned up to log sequence number 16192351396864
InnoDB: Doing recovery: scanned up to log sequence number 16192356639744
InnoDB: Doing recovery: scanned up to log sequence number 16192361882624
InnoDB: Doing recovery: scanned up to log sequence number 16192367125504
InnoDB: Doing recovery: scanned up to log sequence number 16192372368384
InnoDB: Doing recovery: scanned up to log sequence number 16192377611264
InnoDB: Doing recovery: scanned up to log sequence number 16192382854144
InnoDB: Doing recovery: scanned up to log sequence number 16192388097024
InnoDB: Doing recovery: scanned up to log sequence number 16192393339904
InnoDB: Doing recovery: scanned up to log sequence number 16192398582784
InnoDB: Doing recovery: scanned up to log sequence number 16192403825664
InnoDB: Doing recovery: scanned up to log sequence number 16192409068544
InnoDB: Doing recovery: scanned up to log sequence number 16192414311424
InnoDB: Doing recovery: scanned up to log sequence number 16192419554304
InnoDB: Doing recovery: scanned up to log sequence number 16192424797184
InnoDB: Doing recovery: scanned up to log sequence number 16192430040064
InnoDB: Doing recovery: scanned up to log sequence number 16192435282944
InnoDB: Doing recovery: scanned up to log sequence number 16192440525824
InnoDB: Doing recovery: scanned up to log sequence number 16192445768704
InnoDB: Doing recovery: scanned up to log sequence number 16192451011584
InnoDB: Doing recovery: scanned up to log sequence number 16192456254464
InnoDB: Doing recovery: scanned up to log sequence number 16192461497344
InnoDB: Doing recovery: scanned up to log sequence number 16192466740224
InnoDB: Doing recovery: scanned up to log sequence number 16192471983104
InnoDB: Doing recovery: scanned up to log sequence number 16192477225984
InnoDB: Doing recovery: scanned up to log sequence number 16192482468864
InnoDB: Doing recovery: scanned up to log sequence number 16192487711744
InnoDB: Doing recovery: scanned up to log sequence number 16192492954624
InnoDB: Doing recovery: scanned up to log sequence number 16192498197504
InnoDB: Doing recovery: scanned up to log sequence number 16192503440384
InnoDB: Doing recovery: scanned up to log sequence number 16192508683264
InnoDB: Doing recovery: scanned up to log sequence number 16192513926144
InnoDB: Doing recovery: scanned up to log sequence number 16192519169024
InnoDB: Doing recovery: scanned up to log sequence number 16192524411904
InnoDB: Doing recovery: scanned up to log sequence number 16192529654784
InnoDB: Doing recovery: scanned up to log sequence number 16192534897664
InnoDB: Doing recovery: scanned up to log sequence number 16192540140544
InnoDB: Doing recovery: scanned up to log sequence number 16192545383424
InnoDB: Doing recovery: scanned up to log sequence number 16192550626304
InnoDB: Doing recovery: scanned up to log sequence number 16192555869184
InnoDB: Doing recovery: scanned up to log sequence number 16192561112064
InnoDB: Doing recovery: scanned up to log sequence number 16192566354944
InnoDB: Doing recovery: scanned up to log sequence number 16192571597824
InnoDB: Doing recovery: scanned up to log sequence number 16192576840704
InnoDB: Doing recovery: scanned up to log sequence number 16192582083584
InnoDB: Doing recovery: scanned up to log sequence number 16192587326464
InnoDB: Doing recovery: scanned up to log sequence number 16192592569344
InnoDB: Doing recovery: scanned up to log sequence number 16192597812224
InnoDB: Doing recovery: scanned up to log sequence number 16192603055104
InnoDB: Doing recovery: scanned up to log sequence number 16192608297984
InnoDB: Doing recovery: scanned up to log sequence number 16192613540864
InnoDB: Doing recovery: scanned up to log sequence number 16192618783744
InnoDB: Doing recovery: scanned up to log sequence number 16192624026624
InnoDB: Doing recovery: scanned up to log sequence number 16192629269504
InnoDB: Doing recovery: scanned up to log sequence number 16192634512384
InnoDB: Doing recovery: scanned up to log sequence number 16192639755264
InnoDB: Doing recovery: scanned up to log sequence number 16192644998144
InnoDB: Doing recovery: scanned up to log sequence number 16192650241024
InnoDB: Doing recovery: scanned up to log sequence number 16192655483904
InnoDB: Doing recovery: scanned up to log sequence number 16192660726784
InnoDB: Doing recovery: scanned up to log sequence number 16192665969664
InnoDB: Doing recovery: scanned up to log sequence number 16192671212544
InnoDB: Doing recovery: scanned up to log sequence number 16192676455424
InnoDB: Doing recovery: scanned up to log sequence number 16192681698304
InnoDB: Doing recovery: scanned up to log sequence number 16192686941184
InnoDB: Doing recovery: scanned up to log sequence number 16192692184064
InnoDB: Doing recovery: scanned up to log sequence number 16192697426944
InnoDB: Doing recovery: scanned up to log sequence number 16192702669824
InnoDB: Doing recovery: scanned up to log sequence number 16192707912704
InnoDB: Doing recovery: scanned up to log sequence number 16192713155584
InnoDB: Doing recovery: scanned up to log sequence number 16192718398464
InnoDB: Doing recovery: scanned up to log sequence number 16192723641344
InnoDB: Doing recovery: scanned up to log sequence number 16192728884224
InnoDB: Doing recovery: scanned up to log sequence number 16192734127104
InnoDB: Doing recovery: scanned up to log sequence number 16192739369984
InnoDB: Doing recovery: scanned up to log sequence number 16192744612864
InnoDB: Doing recovery: scanned up to log sequence number 16192749855744
InnoDB: Doing recovery: scanned up to log sequence number 16192755098624
InnoDB: Doing recovery: scanned up to log sequence number 16192760341504
InnoDB: Doing recovery: scanned up to log sequence number 16192765584384
InnoDB: Doing recovery: scanned up to log sequence number 16192770827264
InnoDB: Doing recovery: scanned up to log sequence number 16192776070144
InnoDB: Doing recovery: scanned up to log sequence number 16192781313024
InnoDB: Doing recovery: scanned up to log sequence number 16192786555904
InnoDB: Doing recovery: scanned up to log sequence number 16192791798784
InnoDB: Doing recovery: scanned up to log sequence number 16192797041664
InnoDB: Doing recovery: scanned up to log sequence number 16192802284544
InnoDB: Doing recovery: scanned up to log sequence number 16192807527424
InnoDB: Doing recovery: scanned up to log sequence number 16192812770304
InnoDB: Doing recovery: scanned up to log sequence number 16192818013184
InnoDB: Doing recovery: scanned up to log sequence number 16192823256064
InnoDB: Doing recovery: scanned up to log sequence number 16192828498944
InnoDB: Doing recovery: scanned up to log sequence number 16192833741824
InnoDB: Doing recovery: scanned up to log sequence number 16192838984704
InnoDB: Doing recovery: scanned up to log sequence number 16192844227584
InnoDB: Doing recovery: scanned up to log sequence number 16192849470464
InnoDB: Doing recovery: scanned up to log sequence number 16192854713344
InnoDB: Doing recovery: scanned up to log sequence number 16192859956224
InnoDB: Doing recovery: scanned up to log sequence number 16192865199104
InnoDB: Doing recovery: scanned up to log sequence number 16192870441984
InnoDB: Doing recovery: scanned up to log sequence number 16192875684864
InnoDB: Doing recovery: scanned up to log sequence number 16192880927744
InnoDB: Doing recovery: scanned up to log sequence number 16192886170624
InnoDB: Doing recovery: scanned up to log sequence number 16192891413504
InnoDB: Doing recovery: scanned up to log sequence number 16192896656384
InnoDB: Doing recovery: scanned up to log sequence number 16192901899264
InnoDB: Doing recovery: scanned up to log sequence number 16192907142144
InnoDB: Doing recovery: scanned up to log sequence number 16192912385024
InnoDB: Doing recovery: scanned up to log sequence number 16192917627904
InnoDB: Doing recovery: scanned up to log sequence number 16192922870784
InnoDB: Doing recovery: scanned up to log sequence number 16192928113664
InnoDB: Doing recovery: scanned up to log sequence number 16192933356544
InnoDB: Doing recovery: scanned up to log sequence number 16192938599424
InnoDB: Doing recovery: scanned up to log sequence number 16192943842304
InnoDB: Doing recovery: scanned up to log sequence number 16192949085184
InnoDB: Doing recovery: scanned up to log sequence number 16192954328064
InnoDB: Doing recovery: scanned up to log sequence number 16192959570944
InnoDB: Doing recovery: scanned up to log sequence number 16192964813824
InnoDB: Doing recovery: scanned up to log sequence number 16192970056704
InnoDB: Doing recovery: scanned up to log sequence number 16192975299584
InnoDB: Doing recovery: scanned up to log sequence number 16192980542464
InnoDB: Doing recovery: scanned up to log sequence number 16192985785344
InnoDB: Doing recovery: scanned up to log sequence number 16192991028224
InnoDB: Doing recovery: scanned up to log sequence number 16192996271104
InnoDB: Doing recovery: scanned up to log sequence number 16193001513984
InnoDB: Doing recovery: scanned up to log sequence number 16193006756864
InnoDB: Doing recovery: scanned up to log sequence number 16193011999744
InnoDB: Doing recovery: scanned up to log sequence number 16193017242624
InnoDB: Doing recovery: scanned up to log sequence number 16193022485504
InnoDB: Doing recovery: scanned up to log sequence number 16193027728384
InnoDB: Doing recovery: scanned up to log sequence number 16193032971264
InnoDB: Doing recovery: scanned up to log sequence number 16193038214144
InnoDB: Doing recovery: scanned up to log sequence number 16193043457024
InnoDB: Doing recovery: scanned up to log sequence number 16193048699904
InnoDB: Doing recovery: scanned up to log sequence number 16193053942784
InnoDB: Doing recovery: scanned up to log sequence number 16193059185664
InnoDB: Doing recovery: scanned up to log sequence number 16193064428544
InnoDB: Doing recovery: scanned up to log sequence number 16193069671424
InnoDB: Doing recovery: scanned up to log sequence number 16193074914304
InnoDB: Doing recovery: scanned up to log sequence number 16193080157184
InnoDB: Doing recovery: scanned up to log sequence number 16193085400064
InnoDB: Doing recovery: scanned up to log sequence number 16193090642944
InnoDB: Doing recovery: scanned up to log sequence number 16193095885824
InnoDB: Doing recovery: scanned up to log sequence number 16193101128704
InnoDB: Doing recovery: scanned up to log sequence number 16193106371584
InnoDB: Doing recovery: scanned up to log sequence number 16193111614464
InnoDB: Doing recovery: scanned up to log sequence number 16193116857344
InnoDB: Doing recovery: scanned up to log sequence number 16193122100224
InnoDB: Doing recovery: scanned up to log sequence number 16193127343104
InnoDB: Doing recovery: scanned up to log sequence number 16193132585984
InnoDB: Doing recovery: scanned up to log sequence number 16193137828864
InnoDB: Doing recovery: scanned up to log sequence number 16193143071744
InnoDB: Doing recovery: scanned up to log sequence number 16193148314624
InnoDB: Doing recovery: scanned up to log sequence number 16193153557504
InnoDB: Doing recovery: scanned up to log sequence number 16193158800384
InnoDB: Doing recovery: scanned up to log sequence number 16193164043264
InnoDB: Doing recovery: scanned up to log sequence number 16193169286144
InnoDB: Doing recovery: scanned up to log sequence number 16193174529024
InnoDB: Doing recovery: scanned up to log sequence number 16193179771904
InnoDB: Doing recovery: scanned up to log sequence number 16193185014784
InnoDB: Doing recovery: scanned up to log sequence number 16193190257664
InnoDB: Doing recovery: scanned up to log sequence number 16193195500544
InnoDB: Doing recovery: scanned up to log sequence number 16193200743424
InnoDB: Doing recovery: scanned up to log sequence number 16193205986304
InnoDB: Doing recovery: scanned up to log sequence number 16193211229184
InnoDB: Doing recovery: scanned up to log sequence number 16193216472064
InnoDB: Doing recovery: scanned up to log sequence number 16193221714944
InnoDB: Doing recovery: scanned up to log sequence number 16193226957824
InnoDB: Doing recovery: scanned up to log sequence number 16193232200704
InnoDB: Doing recovery: scanned up to log sequence number 16193237443584
InnoDB: Doing recovery: scanned up to log sequence number 16193242686464
InnoDB: Doing recovery: scanned up to log sequence number 16193247929344
InnoDB: Doing recovery: scanned up to log sequence number 16193253172224
InnoDB: Doing recovery: scanned up to log sequence number 16193258415104
InnoDB: Doing recovery: scanned up to log sequence number 16193263657984
InnoDB: Doing recovery: scanned up to log sequence number 16193268900864
InnoDB: Doing recovery: scanned up to log sequence number 16193274143744
InnoDB: Doing recovery: scanned up to log sequence number 16193279386624
InnoDB: Doing recovery: scanned up to log sequence number 16193284629504
InnoDB: Doing recovery: scanned up to log sequence number 16193289872384
InnoDB: Doing recovery: scanned up to log sequence number 16193295115264
InnoDB: Doing recovery: scanned up to log sequence number 16193300358144
InnoDB: Doing recovery: scanned up to log sequence number 16193305601024
InnoDB: Doing recovery: scanned up to log sequence number 16193310843904
InnoDB: Doing recovery: scanned up to log sequence number 16193316086784
InnoDB: Doing recovery: scanned up to log sequence number 16193321329664
InnoDB: Doing recovery: scanned up to log sequence number 16193326572544
InnoDB: Doing recovery: scanned up to log sequence number 16193331815424
InnoDB: Doing recovery: scanned up to log sequence number 16193337058304
InnoDB: Doing recovery: scanned up to log sequence number 16193342301184
InnoDB: Doing recovery: scanned up to log sequence number 16193347544064
InnoDB: Doing recovery: scanned up to log sequence number 16193352786944
InnoDB: Doing recovery: scanned up to log sequence number 16193358029824
InnoDB: Doing recovery: scanned up to log sequence number 16193363272704
InnoDB: Doing recovery: scanned up to log sequence number 16193368515584
InnoDB: Doing recovery: scanned up to log sequence number 16193373758464
InnoDB: Doing recovery: scanned up to log sequence number 16193379001344
InnoDB: Doing recovery: scanned up to log sequence number 16193384244224
InnoDB: Doing recovery: scanned up to log sequence number 16193389487104
InnoDB: Doing recovery: scanned up to log sequence number 16193394729984
InnoDB: Doing recovery: scanned up to log sequence number 16193399972864
InnoDB: Doing recovery: scanned up to log sequence number 16193405215744
InnoDB: Doing recovery: scanned up to log sequence number 16193410458624
InnoDB: Doing recovery: scanned up to log sequence number 16193415701504
InnoDB: Doing recovery: scanned up to log sequence number 16193420944384
InnoDB: Doing recovery: scanned up to log sequence number 16193426187264
InnoDB: Doing recovery: scanned up to log sequence number 16193431430144
InnoDB: Doing recovery: scanned up to log sequence number 16193436673024
InnoDB: Doing recovery: scanned up to log sequence number 16193441915904
InnoDB: Doing recovery: scanned up to log sequence number 16193447158784
InnoDB: Doing recovery: scanned up to log sequence number 16193452401664
InnoDB: Doing recovery: scanned up to log sequence number 16193457644544
InnoDB: Doing recovery: scanned up to log sequence number 16193462887424
InnoDB: Doing recovery: scanned up to log sequence number 16193468130304
InnoDB: Doing recovery: scanned up to log sequence number 16193473373184
InnoDB: Doing recovery: scanned up to log sequence number 16193478616064
InnoDB: Doing recovery: scanned up to log sequence number 16193483858944
InnoDB: Doing recovery: scanned up to log sequence number 16193489101824
InnoDB: Doing recovery: scanned up to log sequence number 16193494344704
InnoDB: Doing recovery: scanned up to log sequence number 16193499587584
InnoDB: Doing recovery: scanned up to log sequence number 16193504830464
InnoDB: Doing recovery: scanned up to log sequence number 16193510073344
InnoDB: Doing recovery: scanned up to log sequence number 16193515316224
InnoDB: Doing recovery: scanned up to log sequence number 16193520559104
InnoDB: Doing recovery: scanned up to log sequence number 16193525801984
InnoDB: Doing recovery: scanned up to log sequence number 16193531044864
InnoDB: Doing recovery: scanned up to log sequence number 16193536287744
InnoDB: Doing recovery: scanned up to log sequence number 16193541530624
InnoDB: Doing recovery: scanned up to log sequence number 16193546773504
InnoDB: Doing recovery: scanned up to log sequence number 16193552016384
InnoDB: Doing recovery: scanned up to log sequence number 16193557259264
InnoDB: Doing recovery: scanned up to log sequence number 16193562502144
InnoDB: Doing recovery: scanned up to log sequence number 16193567745024
InnoDB: Doing recovery: scanned up to log sequence number 16193572987904
InnoDB: Doing recovery: scanned up to log sequence number 16193578230784
InnoDB: Doing recovery: scanned up to log sequence number 16193583473664
InnoDB: Doing recovery: scanned up to log sequence number 16193588716544
InnoDB: Doing recovery: scanned up to log sequence number 16193593959424
InnoDB: Doing recovery: scanned up to log sequence number 16193599202304
InnoDB: Doing recovery: scanned up to log sequence number 16193604445184
InnoDB: Doing recovery: scanned up to log sequence number 16193609688064
InnoDB: Doing recovery: scanned up to log sequence number 16193614930944
InnoDB: Doing recovery: scanned up to log sequence number 16193620173824
InnoDB: Doing recovery: scanned up to log sequence number 16193625416704
InnoDB: Doing recovery: scanned up to log sequence number 16193630659584
InnoDB: Doing recovery: scanned up to log sequence number 16193635902464
InnoDB: Doing recovery: scanned up to log sequence number 16193641145344
InnoDB: Doing recovery: scanned up to log sequence number 16193646388224
InnoDB: Doing recovery: scanned up to log sequence number 16193651631104
InnoDB: Doing recovery: scanned up to log sequence number 16193656873984
InnoDB: Doing recovery: scanned up to log sequence number 16193662116864
InnoDB: Doing recovery: scanned up to log sequence number 16193667359744
InnoDB: Doing recovery: scanned up to log sequence number 16193672602624
InnoDB: Doing recovery: scanned up to log sequence number 16193677845504
InnoDB: Doing recovery: scanned up to log sequence number 16193683088384
InnoDB: Doing recovery: scanned up to log sequence number 16193688331264
InnoDB: Doing recovery: scanned up to log sequence number 16193693574144
InnoDB: Doing recovery: scanned up to log sequence number 16193698817024
InnoDB: Doing recovery: scanned up to log sequence number 16193704059904
InnoDB: Doing recovery: scanned up to log sequence number 16193709302784
InnoDB: Doing recovery: scanned up to log sequence number 16193714545664
InnoDB: Doing recovery: scanned up to log sequence number 16193719788544
InnoDB: Doing recovery: scanned up to log sequence number 16193725031424
InnoDB: Doing recovery: scanned up to log sequence number 16193730274304
InnoDB: Doing recovery: scanned up to log sequence number 16193735517184
InnoDB: Doing recovery: scanned up to log sequence number 16193740760064
InnoDB: Doing recovery: scanned up to log sequence number 16193746002944
InnoDB: Doing recovery: scanned up to log sequence number 16193751245824
InnoDB: Doing recovery: scanned up to log sequence number 16193756488704
InnoDB: Doing recovery: scanned up to log sequence number 16193761731584
InnoDB: Doing recovery: scanned up to log sequence number 16193766974464
InnoDB: Doing recovery: scanned up to log sequence number 16193772217344
InnoDB: Doing recovery: scanned up to log sequence number 16193777460224
InnoDB: Doing recovery: scanned up to log sequence number 16193782703104
InnoDB: Doing recovery: scanned up to log sequence number 16193787945984
InnoDB: Doing recovery: scanned up to log sequence number 16193793188864
InnoDB: Doing recovery: scanned up to log sequence number 16193798431744
InnoDB: Doing recovery: scanned up to log sequence number 16193803674624
InnoDB: Doing recovery: scanned up to log sequence number 16193808917504
InnoDB: Doing recovery: scanned up to log sequence number 16193814160384
InnoDB: Doing recovery: scanned up to log sequence number 16193819403264
InnoDB: Doing recovery: scanned up to log sequence number 16193824646144
InnoDB: Doing recovery: scanned up to log sequence number 16193829889024
InnoDB: Doing recovery: scanned up to log sequence number 16193835131904
InnoDB: Doing recovery: scanned up to log sequence number 16193840374784
InnoDB: Doing recovery: scanned up to log sequence number 16193845617664
InnoDB: Doing recovery: scanned up to log sequence number 16193850860544
InnoDB: Doing recovery: scanned up to log sequence number 16193856103424
InnoDB: Doing recovery: scanned up to log sequence number 16193861346304
InnoDB: Doing recovery: scanned up to log sequence number 16193866589184
InnoDB: Doing recovery: scanned up to log sequence number 16193871832064
InnoDB: Doing recovery: scanned up to log sequence number 16193877074944
InnoDB: Doing recovery: scanned up to log sequence number 16193882317824
InnoDB: Doing recovery: scanned up to log sequence number 16193887560704
InnoDB: Doing recovery: scanned up to log sequence number 16193892803584
InnoDB: Doing recovery: scanned up to log sequence number 16193898046464
InnoDB: Doing recovery: scanned up to log sequence number 16193903289344
InnoDB: Doing recovery: scanned up to log sequence number 16193908532224
InnoDB: Doing recovery: scanned up to log sequence number 16193913775104
InnoDB: Doing recovery: scanned up to log sequence number 16193919017984
InnoDB: Doing recovery: scanned up to log sequence number 16193924260864
InnoDB: Doing recovery: scanned up to log sequence number 16193929503744
InnoDB: Doing recovery: scanned up to log sequence number 16193934746624
InnoDB: Doing recovery: scanned up to log sequence number 16193939989504
InnoDB: Doing recovery: scanned up to log sequence number 16193945232384
InnoDB: Doing recovery: scanned up to log sequence number 16193950475264
InnoDB: Doing recovery: scanned up to log sequence number 16193955718144
InnoDB: Doing recovery: scanned up to log sequence number 16193960961024
InnoDB: Doing recovery: scanned up to log sequence number 16193966203904
InnoDB: Doing recovery: scanned up to log sequence number 16193971446784
InnoDB: Doing recovery: scanned up to log sequence number 16193976689664
InnoDB: Doing recovery: scanned up to log sequence number 16193981932544
InnoDB: Doing recovery: scanned up to log sequence number 16193987175424
InnoDB: Doing recovery: scanned up to log sequence number 16193992418304
InnoDB: Doing recovery: scanned up to log sequence number 16193997661184
InnoDB: Doing recovery: scanned up to log sequence number 16194002904064
InnoDB: Doing recovery: scanned up to log sequence number 16194008146944
InnoDB: Doing recovery: scanned up to log sequence number 16194013389824
InnoDB: Doing recovery: scanned up to log sequence number 16194018632704
InnoDB: Doing recovery: scanned up to log sequence number 16194023875584
InnoDB: Doing recovery: scanned up to log sequence number 16194029118464
InnoDB: Doing recovery: scanned up to log sequence number 16194034361344
InnoDB: Doing recovery: scanned up to log sequence number 16194039604224
InnoDB: Doing recovery: scanned up to log sequence number 16194044847104
InnoDB: Doing recovery: scanned up to log sequence number 16194050089984
InnoDB: Doing recovery: scanned up to log sequence number 16194055332864
InnoDB: Doing recovery: scanned up to log sequence number 16194060575744
InnoDB: Doing recovery: scanned up to log sequence number 16194065818624
InnoDB: Doing recovery: scanned up to log sequence number 16194071061504
InnoDB: Doing recovery: scanned up to log sequence number 16194076304384
InnoDB: Doing recovery: scanned up to log sequence number 16194081547264
InnoDB: Doing recovery: scanned up to log sequence number 16194086790144
InnoDB: Doing recovery: scanned up to log sequence number 16194092033024
InnoDB: Doing recovery: scanned up to log sequence number 16194097275904
InnoDB: Doing recovery: scanned up to log sequence number 16194102518784
InnoDB: Doing recovery: scanned up to log sequence number 16194107761664
InnoDB: Doing recovery: scanned up to log sequence number 16194113004544
InnoDB: Doing recovery: scanned up to log sequence number 16194118247424
InnoDB: Doing recovery: scanned up to log sequence number 16194123490304
InnoDB: Doing recovery: scanned up to log sequence number 16194128733184
InnoDB: Doing recovery: scanned up to log sequence number 16194133976064
InnoDB: Doing recovery: scanned up to log sequence number 16194139218944
InnoDB: Doing recovery: scanned up to log sequence number 16194144461824
InnoDB: Doing recovery: scanned up to log sequence number 16194149704704
InnoDB: Doing recovery: scanned up to log sequence number 16194154947584
InnoDB: Doing recovery: scanned up to log sequence number 16194160190464
InnoDB: Doing recovery: scanned up to log sequence number 16194165433344
InnoDB: Doing recovery: scanned up to log sequence number 16194170676224
InnoDB: Doing recovery: scanned up to log sequence number 16194175919104
InnoDB: Doing recovery: scanned up to log sequence number 16194181161984
InnoDB: Doing recovery: scanned up to log sequence number 16194186404864
InnoDB: Doing recovery: scanned up to log sequence number 16194191647744
InnoDB: Doing recovery: scanned up to log sequence number 16194196890624
InnoDB: Doing recovery: scanned up to log sequence number 16194202133504
InnoDB: Doing recovery: scanned up to log sequence number 16194207376384
InnoDB: Doing recovery: scanned up to log sequence number 16194208283296
InnoDB: 3 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 6 row operations to undo
InnoDB: Trx id counter is E15B0BE00
121017 13:41:49  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 121017 13:42:40  InnoDB: Assertion failure in thread 1262557536 in file /export/home/pb2/build/sb_0-3159149-1301580870.56/mysql-5.5.11/storage/innobase/ibuf/ibuf0ibuf.c line 4130
InnoDB: Failing assertion: page_get_n_recs(page) > 1
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.
121017 13:42:40 - 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.

key_buffer_size=1073741824
read_buffer_size=4194304
max_used_connections=0
max_threads=500
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 = 5150267 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 = (nil) thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x39)[0x795f29]
/usr/local/mysql/bin/mysqld(handle_segfault+0x380)[0x4fce00]
/lib64/tls/libpthread.so.0[0x32df10c5b0]
/lib64/tls/libc.so.6(gsignal+0x3d)[0x32de62e26d]
/lib64/tls/libc.so.6(abort+0xfe)[0x32de62fa6e]
/usr/local/mysql/bin/mysqld[0x86cd2d]
/usr/local/mysql/bin/mysqld[0x8224c1]
/usr/local/mysql/bin/mysqld[0x853cc0]
/usr/local/mysql/bin/mysqld[0x7dfdc0]
/lib64/tls/libpthread.so.0[0x32df106137]
/lib64/tls/libc.so.6(__clone+0x73)[0x32de6c9883]
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.
121017 13:42:41 mysqld_safe mysqld from pid file /opt/mysql/data1/q3-db1.webtech.local.pid ended