Description:
151029 11:22:21 mysqld_safe Starting mysqld daemon with databases from /storedb/mysql
2015-10-29 11:22:21 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2015-10-29 11:22:21 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-10-29 11:22:21 0 [Note] /opt/mysql/bin/mysqld (mysqld 5.6.24-enterprise-commercial-advanced-log) starting as process 4261 ...
2015-10-29 11:22:21 4261 [Note] Plugin 'FEDERATED' is disabled.
2015-10-29 11:22:21 1 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-10-29 11:22:21 4261 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-10-29 11:22:21 4261 [Note] InnoDB: The InnoDB memory heap is disabled
2015-10-29 11:22:21 4261 [Note] InnoDB: Mutexes and rw_locks use Solaris atomic functions
2015-10-29 11:22:21 4261 [Note] InnoDB: Memory barrier is not used
2015-10-29 11:22:21 4261 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-10-29 11:22:21 4261 [Note] InnoDB: Not using CPU crc32 instructions
2015-10-29 11:22:21 4261 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2015-10-29 11:22:21 4261 [Note] InnoDB: Completed initialization of buffer pool
2015-10-29 11:22:21 4261 [Note] InnoDB: Highest supported file format is Barracuda.
2015-10-29 11:22:21 4261 [Note] InnoDB: Log scan progressed past the checkpoint lsn 9751808481
2015-10-29 11:22:21 4261 [Note] InnoDB: Database was not shutdown normally!
2015-10-29 11:22:21 4261 [Note] InnoDB: Starting crash recovery.
2015-10-29 11:22:21 4261 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-10-29 11:22:21 4261 [Note] InnoDB: Restoring possible half-written data pages
2015-10-29 11:22:21 4261 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 9752129000
InnoDB: Transaction 8078629846 was in the XA prepared state.
InnoDB: Since innodb_force_recovery > 0, we will rollback it anyway.
2015-10-29 11:22:21 1 InnoDB: index "componentuid" of table "caldav"."CalProp" is corrupted
2015-10-29 11:22:21 1 InnoDB: load corrupted index index "componentuid" of table "caldav"."CalProp"
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2 row operations to undo
InnoDB: Trx id counter is 8078630144
2015-10-29 11:22:21 4261 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
InnoDB: Last MySQL binlog file position 0 109453, file name mysql-bin.000025
2015-10-29 11:22:22 4261 [Note] InnoDB: 128 rollback segment(s) are active.
InnoDB: Starting in background the rollback of uncommitted transactions
2015-10-29 11:22:22 d InnoDB: Rolling back trx with id 8078629846, 2 rows to undo
2015-10-29 11:22:22 4261 [Note] InnoDB: Waiting for purge to start
2015-10-29 11:22:22 4261 [Note] InnoDB: Rollback of trx with id 8078629846 completed
2015-10-29 11:22:22 d InnoDB: Rollback of non-prepared transactions completed
2015-10-29 11:22:22 12 InnoDB: Assertion failure in thread 18 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
10:22:22 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=536870912
read_buffer_size=16777216
max_used_connections=0
max_threads=250
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 = 8719416 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...
/opt/mysql/bin/mysqld:my_print_stacktrace+0x1e
/opt/mysql/bin/mysqld:handle_fatal_signal+0x3e7
/lib/amd64/libc.so.1:0xdde26
/lib/amd64/libc.so.1:0xd26f2
/lib/amd64/libc.so.1:__lwp_kill+0xa [ Signal 6 (ABRT)]
/lib/amd64/libc.so.1:raise+0x19
/lib/amd64/libc.so.1:abort+0x5e
/opt/mysql/bin/mysqld:0xc5927c
/opt/mysql/bin/mysqld:0xc593e0
/opt/mysql/bin/mysqld:0xc5967b
/opt/mysql/bin/mysqld:0xc597c5
/opt/mysql/bin/mysqld:0xc59a61
/opt/mysql/bin/mysqld:__1cJtrx_purge6FLLb_L_+0x1fe
/opt/mysql/bin/mysqld:0xc4884b
/opt/mysql/bin/mysqld:srv_purge_coordinator_thread+0x290
/lib/amd64/libc.so.1:0xddaeb
/lib/amd64/libc.so.1:0xddd20
Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.html
and follow instructions on how to resolve the stack trace.
Resolved stack trace is much more helpful in diagnosing the
problem, so please do resolve it
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.
151029 11:22:22 mysqld_safe mysqld from pid file /storedb/mysql/cs6.pid ended
How to repeat:
can reprat with a corrupt INNODB
