ROW OPERATIONS
--------------
0 queries inside InnoDB, 0 queries in queue
3 read views open inside InnoDB
Main thread process no. 2376, id 139688581822208, state: doing insert buffer merge
Number of rows inserted 199807793, updated 1003503102, deleted 124405713, read 3445542818038
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 1972091.50 reads/s
----------------------------
END OF INNODB MONITOR OUTPUT
============================
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Warning: a long semaphore wait:
--Thread 139682125571840 has waited at buf0buf.cc line 2477 for 268.00 seconds the semaphore:
S-lock on RW-latch at 0x7f0c23824cc0 created in file buf0buf.cc line 1016
a writer (thread id 139682125571840) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file buf0flu.cc line 1033
Last time write locked in file /pb2/build/sb_0-11763321-1394824179.77/rpm/BUILD/mysql-5.6.17/mysql-5.6.17/storage/innobase/buf/buf0buf.cc line 3598
InnoDB: Warning: a long semaphore wait:
--Thread 139686395033344 has waited at dict0dict.cc line 941 for 271.00 seconds the semaphore:
Mutex at 0x72b2be8 created file dict0dict.cc line 878, lock var 1
--
--------------
0 queries inside InnoDB, 0 queries in queue
6 read views open inside InnoDB
Main thread process no. 2376, id 139688581822208, state: doing insert buffer merge
Number of rows inserted 199807793, updated 1003503102, deleted 124405713, read 3445582531959
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 1985596.77 reads/s
----------------------------
END OF INNODB MONITOR OUTPUT
END OF INNODB MONITOR OUTPUT
============================
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Warning: a long semaphore wait:
--Thread 139682125571840 has waited at buf0buf.cc line 2477 for 485.00 seconds the semaphore:
S-lock on RW-latch at 0x7f0c23824cc0 created in file buf0buf.cc line 1016
a writer (thread id 139682125571840) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file buf0flu.cc line 1033
Last time write locked in file /pb2/build/sb_0-11763321-1394824179.77/rpm/BUILD/mysql-5.6.17/mysql-5.6.17/storage/innobase/buf/buf0buf.cc line 3598
InnoDB: Warning: a long semaphore wait:
--Thread 139686395033344 has waited at dict0dict.cc line 941 for 488.00 seconds the semaphore:
Mutex at 0x72b2be8 created file dict0dict.cc line 878, lock var 1
--
--Thread 139688571332352 has waited at row0purge.cc line 720 for 489.00 seconds the semaphore:
S-lock on RW-latch at 0x135d740 created in file dict0dict.cc line 887
a writer (thread id 139686375597824) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0purge.cc line 720
Last time write locked in file /pb2/build/sb_0-11763321-1394824179.77/rpm/BUILD/mysql-5.6.17/mysql-5.6.17/storage/innobase/handler/handler0alter.cc line 5418
InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
InnoDB: Pending preads 0, pwrites 0
2015-07-31 02:18:53 7f0b44cc2700  InnoDB: Warning: problems renaming 'simutv/out_sms_backup' to 'simutv/#sql-ib22520', 25000 iterations
2015-07-31 02:18:53 7f0b44cc2700  InnoDB: Assertion failure in thread 139686375597824 in file handler0alter.cc line 4948
InnoDB: Failing assertion: error == DB_SUCCESS
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.
23:18:53 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=125829120
read_buffer_size=131072
max_used_connections=222
max_threads=500
thread_count=60
connection_count=57