160603 04:32:50 mysqld_safe Starting mysqld daemon with databases from /opt/mysql/dbdata1/keywords-p0
2016-06-03 04:32:50 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
2016-06-03 04:32:50 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-06-03 04:32:50 0 [Warning] 'ERROR_FOR_DIVISION_BY_ZERO' is deprecated and will be removed in a future release.
2016-06-03 04:32:50 0 [Warning] 'NO_ZERO_DATE' is deprecated and will be removed in a future release.
2016-06-03 04:32:50 0 [Warning] 'NO_ZERO_IN_DATE' is deprecated and will be removed in a future release.
2016-06-03 04:32:50 0 [Note] /usr/sbin/mysqld (mysqld 5.6.25-log) starting as process 19175 ...
2016-06-03 04:32:50 19175 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
2016-06-03 04:32:50 19175 [Note] Plugin 'FEDERATED' is disabled.
2016-06-03 04:32:50 19175 [Warning] The option innodb (skip-innodb) is deprecated and will be removed in a future release
2016-06-03 04:32:50 19175 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-06-03 04:32:50 19175 [Note] InnoDB: The InnoDB memory heap is disabled
2016-06-03 04:32:50 19175 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-06-03 04:32:50 19175 [Note] InnoDB: Memory barrier is not used
2016-06-03 04:32:50 19175 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-06-03 04:32:50 19175 [Note] InnoDB: Using Linux native AIO
2016-06-03 04:32:50 19175 [Note] InnoDB: Using CPU crc32 instructions
2016-06-03 04:32:50 19175 [Note] InnoDB: Initializing buffer pool, size = 23.0G
2016-06-03 04:32:52 19175 [Note] InnoDB: Completed initialization of buffer pool
2016-06-03 04:32:52 19175 [Note] InnoDB: Highest supported file format is Barracuda.
2016-06-03 04:32:52 19175 [Note] InnoDB: Log scan progressed past the checkpoint lsn 14910476589518
2016-06-03 04:32:52 19175 [Note] InnoDB: Database was not shutdown normally!
2016-06-03 04:32:52 19175 [Note] InnoDB: Starting crash recovery.
2016-06-03 04:32:52 19175 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-06-03 04:32:52 19175 [Note] InnoDB: Restoring possible half-written data pages 
2016-06-03 04:32:52 19175 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 14910481831936
InnoDB: Doing recovery: scanned up to log sequence number 14910487074816
InnoDB: Doing recovery: scanned up to log sequence number 14910492317696
InnoDB: Doing recovery: scanned up to log sequence number 14910497560576
InnoDB: Doing recovery: scanned up to log sequence number 14910502803456
InnoDB: Doing recovery: scanned up to log sequence number 14910508046336
InnoDB: Doing recovery: scanned up to log sequence number 14910513289216
InnoDB: Doing recovery: scanned up to log sequence number 14910518532096
InnoDB: Doing recovery: scanned up to log sequence number 14910523774976
InnoDB: Doing recovery: scanned up to log sequence number 14910529017856
InnoDB: Doing recovery: scanned up to log sequence number 14910534260736
InnoDB: Doing recovery: scanned up to log sequence number 14910539503616
InnoDB: Doing recovery: scanned up to log sequence number 14910544746496
InnoDB: Doing recovery: scanned up to log sequence number 14910549989376
InnoDB: Doing recovery: scanned up to log sequence number 14910555232256
InnoDB: Doing recovery: scanned up to log sequence number 14910560475136
InnoDB: Doing recovery: scanned up to log sequence number 14910565718016
InnoDB: Doing recovery: scanned up to log sequence number 14910570960896
InnoDB: Doing recovery: scanned up to log sequence number 14910576203776
InnoDB: Doing recovery: scanned up to log sequence number 14910581446656
InnoDB: Doing recovery: scanned up to log sequence number 14910586689536
InnoDB: Doing recovery: scanned up to log sequence number 14910591932416
InnoDB: Doing recovery: scanned up to log sequence number 14910597175296
InnoDB: Doing recovery: scanned up to log sequence number 14910602418176
InnoDB: Doing recovery: scanned up to log sequence number 14910607661056
InnoDB: Doing recovery: scanned up to log sequence number 14910612903936
InnoDB: Doing recovery: scanned up to log sequence number 14910618146816
InnoDB: Doing recovery: scanned up to log sequence number 14910623389696
InnoDB: Doing recovery: scanned up to log sequence number 14910628632576
InnoDB: Doing recovery: scanned up to log sequence number 14910633875456
InnoDB: Doing recovery: scanned up to log sequence number 14910639118336
InnoDB: Doing recovery: scanned up to log sequence number 14910644361216
InnoDB: Doing recovery: scanned up to log sequence number 14910649604096
InnoDB: Doing recovery: scanned up to log sequence number 14910654846976
InnoDB: Doing recovery: scanned up to log sequence number 14910660089856
InnoDB: Doing recovery: scanned up to log sequence number 14910665332736
InnoDB: Doing recovery: scanned up to log sequence number 14910670575616
InnoDB: Doing recovery: scanned up to log sequence number 14910675818496
InnoDB: Doing recovery: scanned up to log sequence number 14910681061376
InnoDB: Doing recovery: scanned up to log sequence number 14910686304256
InnoDB: Doing recovery: scanned up to log sequence number 14910691547136
InnoDB: Doing recovery: scanned up to log sequence number 14910696790016
InnoDB: Doing recovery: scanned up to log sequence number 14910702032896
InnoDB: Doing recovery: scanned up to log sequence number 14910707275776
InnoDB: Doing recovery: scanned up to log sequence number 14910712518656
InnoDB: Doing recovery: scanned up to log sequence number 14910717761536
InnoDB: Doing recovery: scanned up to log sequence number 14910723004416
InnoDB: Doing recovery: scanned up to log sequence number 14910728247296
InnoDB: Doing recovery: scanned up to log sequence number 14910733490176
InnoDB: Doing recovery: scanned up to log sequence number 14910738733056
InnoDB: Doing recovery: scanned up to log sequence number 14910743975936
InnoDB: Doing recovery: scanned up to log sequence number 14910749218816
InnoDB: Doing recovery: scanned up to log sequence number 14910754461696
InnoDB: Doing recovery: scanned up to log sequence number 14910759704576
InnoDB: Doing recovery: scanned up to log sequence number 14910764947456
InnoDB: Doing recovery: scanned up to log sequence number 14910770190336
InnoDB: Doing recovery: scanned up to log sequence number 14910775433216
InnoDB: Doing recovery: scanned up to log sequence number 14910780676096
InnoDB: Doing recovery: scanned up to log sequence number 14910785918976
InnoDB: Doing recovery: scanned up to log sequence number 14910791161856
InnoDB: Doing recovery: scanned up to log sequence number 14910796404736
InnoDB: Doing recovery: scanned up to log sequence number 14910801647616
InnoDB: Doing recovery: scanned up to log sequence number 14910806890496
InnoDB: Doing recovery: scanned up to log sequence number 14910812133376
InnoDB: Doing recovery: scanned up to log sequence number 14910817376256
InnoDB: Doing recovery: scanned up to log sequence number 14910822619136
InnoDB: Doing recovery: scanned up to log sequence number 14910827862016
InnoDB: Doing recovery: scanned up to log sequence number 14910833104896
InnoDB: Doing recovery: scanned up to log sequence number 14910838347776
InnoDB: Doing recovery: scanned up to log sequence number 14910843590656
InnoDB: Doing recovery: scanned up to log sequence number 14910848833536
InnoDB: Doing recovery: scanned up to log sequence number 14910854076416
InnoDB: Doing recovery: scanned up to log sequence number 14910859319296
InnoDB: Doing recovery: scanned up to log sequence number 14910864562176
InnoDB: Doing recovery: scanned up to log sequence number 14910869805056
InnoDB: Doing recovery: scanned up to log sequence number 14910875047936
InnoDB: Doing recovery: scanned up to log sequence number 14910880290816
InnoDB: Doing recovery: scanned up to log sequence number 14910885533696
InnoDB: Doing recovery: scanned up to log sequence number 14910890776576
InnoDB: Doing recovery: scanned up to log sequence number 14910896019456
InnoDB: Doing recovery: scanned up to log sequence number 14910901262336
InnoDB: Doing recovery: scanned up to log sequence number 14910906505216
InnoDB: Doing recovery: scanned up to log sequence number 14910911748096
InnoDB: Doing recovery: scanned up to log sequence number 14910916990976
InnoDB: Doing recovery: scanned up to log sequence number 14910922233856
InnoDB: Doing recovery: scanned up to log sequence number 14910927476736
InnoDB: Doing recovery: scanned up to log sequence number 14910932719616
InnoDB: Doing recovery: scanned up to log sequence number 14910937962496
InnoDB: Doing recovery: scanned up to log sequence number 14910943205376
InnoDB: Doing recovery: scanned up to log sequence number 14910948448256
InnoDB: Doing recovery: scanned up to log sequence number 14910953691136
InnoDB: Doing recovery: scanned up to log sequence number 14910958934016
InnoDB: Doing recovery: scanned up to log sequence number 14910964176896
InnoDB: Doing recovery: scanned up to log sequence number 14910969419776
InnoDB: Doing recovery: scanned up to log sequence number 14910974662656
InnoDB: Doing recovery: scanned up to log sequence number 14910979905536
InnoDB: Doing recovery: scanned up to log sequence number 14910985148416
InnoDB: Doing recovery: scanned up to log sequence number 14910990391296
InnoDB: Doing recovery: scanned up to log sequence number 14910995634176
InnoDB: Doing recovery: scanned up to log sequence number 14911000877056
InnoDB: Doing recovery: scanned up to log sequence number 14911006119936
InnoDB: Doing recovery: scanned up to log sequence number 14911011362816
InnoDB: Doing recovery: scanned up to log sequence number 14911016605696
InnoDB: Doing recovery: scanned up to log sequence number 14911021848576
InnoDB: Doing recovery: scanned up to log sequence number 14911027091456
InnoDB: Doing recovery: scanned up to log sequence number 14911032334336
InnoDB: Doing recovery: scanned up to log sequence number 14911037577216
InnoDB: Doing recovery: scanned up to log sequence number 14911042820096
InnoDB: Doing recovery: scanned up to log sequence number 14911048062976
InnoDB: Doing recovery: scanned up to log sequence number 14911053305856
InnoDB: Doing recovery: scanned up to log sequence number 14911058548736
InnoDB: Doing recovery: scanned up to log sequence number 14911063791616
InnoDB: Doing recovery: scanned up to log sequence number 14911069034496
InnoDB: Doing recovery: scanned up to log sequence number 14911074277376
InnoDB: Doing recovery: scanned up to log sequence number 14911079520256
InnoDB: Doing recovery: scanned up to log sequence number 14911084763136
InnoDB: Doing recovery: scanned up to log sequence number 14911090006016
InnoDB: Doing recovery: scanned up to log sequence number 14911095248896
InnoDB: Doing recovery: scanned up to log sequence number 14911100491776
InnoDB: Doing recovery: scanned up to log sequence number 14911105734656
InnoDB: Doing recovery: scanned up to log sequence number 14911110977536
InnoDB: Doing recovery: scanned up to log sequence number 14911116220416
InnoDB: Doing recovery: scanned up to log sequence number 14911121463296
InnoDB: Doing recovery: scanned up to log sequence number 14911126706176
InnoDB: Doing recovery: scanned up to log sequence number 14911131949056
InnoDB: Doing recovery: scanned up to log sequence number 14911137191936
InnoDB: Doing recovery: scanned up to log sequence number 14911142434816
InnoDB: Doing recovery: scanned up to log sequence number 14911147677696
InnoDB: Doing recovery: scanned up to log sequence number 14911152920576
InnoDB: Doing recovery: scanned up to log sequence number 14911158163456
InnoDB: Doing recovery: scanned up to log sequence number 14911163406336
InnoDB: Doing recovery: scanned up to log sequence number 14911168649216
InnoDB: Doing recovery: scanned up to log sequence number 14911173892096
InnoDB: Doing recovery: scanned up to log sequence number 14911179134976
InnoDB: Doing recovery: scanned up to log sequence number 14911184377856
InnoDB: Doing recovery: scanned up to log sequence number 14911189620736
InnoDB: Doing recovery: scanned up to log sequence number 14911194863616
InnoDB: Doing recovery: scanned up to log sequence number 14911200106496
InnoDB: Doing recovery: scanned up to log sequence number 14911205349376
InnoDB: Doing recovery: scanned up to log sequence number 14911210592256
InnoDB: Doing recovery: scanned up to log sequence number 14911215835136
InnoDB: Doing recovery: scanned up to log sequence number 14911221078016
InnoDB: Doing recovery: scanned up to log sequence number 14911226320896
InnoDB: Doing recovery: scanned up to log sequence number 14911231563776
InnoDB: Doing recovery: scanned up to log sequence number 14911236806656
InnoDB: Doing recovery: scanned up to log sequence number 14911242049536
InnoDB: Doing recovery: scanned up to log sequence number 14911247292416
InnoDB: Doing recovery: scanned up to log sequence number 14911252535296
InnoDB: Doing recovery: scanned up to log sequence number 14911257778176
InnoDB: Doing recovery: scanned up to log sequence number 14911263021056
InnoDB: Doing recovery: scanned up to log sequence number 14911268263936
InnoDB: Doing recovery: scanned up to log sequence number 14911273506816
InnoDB: Doing recovery: scanned up to log sequence number 14911278749696
InnoDB: Doing recovery: scanned up to log sequence number 14911283992576
InnoDB: Doing recovery: scanned up to log sequence number 14911289235456
InnoDB: Doing recovery: scanned up to log sequence number 14911294478336
InnoDB: Doing recovery: scanned up to log sequence number 14911299721216
InnoDB: Doing recovery: scanned up to log sequence number 14911304964096
InnoDB: Doing recovery: scanned up to log sequence number 14911310206976
InnoDB: Doing recovery: scanned up to log sequence number 14911315449856
InnoDB: Doing recovery: scanned up to log sequence number 14911320692736
InnoDB: Doing recovery: scanned up to log sequence number 14911325935616
InnoDB: Doing recovery: scanned up to log sequence number 14911331178496
InnoDB: Doing recovery: scanned up to log sequence number 14911336421376
InnoDB: Doing recovery: scanned up to log sequence number 14911341664256
InnoDB: Doing recovery: scanned up to log sequence number 14911346907136
InnoDB: Doing recovery: scanned up to log sequence number 14911352150016
InnoDB: Doing recovery: scanned up to log sequence number 14911357392896
InnoDB: Doing recovery: scanned up to log sequence number 14911362635776
InnoDB: Doing recovery: scanned up to log sequence number 14911367878656
InnoDB: Doing recovery: scanned up to log sequence number 14911373121536
InnoDB: Doing recovery: scanned up to log sequence number 14911378364416
InnoDB: Doing recovery: scanned up to log sequence number 14911383607296
InnoDB: Doing recovery: scanned up to log sequence number 14911388850176
InnoDB: Doing recovery: scanned up to log sequence number 14911394093056
InnoDB: Doing recovery: scanned up to log sequence number 14911399335936
InnoDB: Doing recovery: scanned up to log sequence number 14911404578816
InnoDB: Doing recovery: scanned up to log sequence number 14911409821696
InnoDB: Doing recovery: scanned up to log sequence number 14911415064576
InnoDB: Doing recovery: scanned up to log sequence number 14911420307456
InnoDB: Doing recovery: scanned up to log sequence number 14911425550336
InnoDB: Doing recovery: scanned up to log sequence number 14911430793216
InnoDB: Doing recovery: scanned up to log sequence number 14911436036096
InnoDB: Doing recovery: scanned up to log sequence number 14911441278976
InnoDB: Doing recovery: scanned up to log sequence number 14911446521856
InnoDB: Doing recovery: scanned up to log sequence number 14911451764736
InnoDB: Doing recovery: scanned up to log sequence number 14911457007616
InnoDB: Doing recovery: scanned up to log sequence number 14911462250496
InnoDB: Doing recovery: scanned up to log sequence number 14911467493376
InnoDB: Doing recovery: scanned up to log sequence number 14911472736256
InnoDB: Doing recovery: scanned up to log sequence number 14911477979136
InnoDB: Doing recovery: scanned up to log sequence number 14911483222016
InnoDB: Doing recovery: scanned up to log sequence number 14911488464896
InnoDB: Doing recovery: scanned up to log sequence number 14911493707776
InnoDB: Doing recovery: scanned up to log sequence number 14911498950656
InnoDB: Doing recovery: scanned up to log sequence number 14911504193536
InnoDB: Doing recovery: scanned up to log sequence number 14911509436416
InnoDB: Doing recovery: scanned up to log sequence number 14911514679296
InnoDB: Doing recovery: scanned up to log sequence number 14911519922176
InnoDB: Doing recovery: scanned up to log sequence number 14911525165056
InnoDB: Doing recovery: scanned up to log sequence number 14911530407936
InnoDB: Doing recovery: scanned up to log sequence number 14911535650816
InnoDB: Doing recovery: scanned up to log sequence number 14911536060763
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 52823434752
2016-06-03 04:33:06 19175 [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 2016-06-03 04:33:11 7f6ae765f700  InnoDB: Assertion failure in thread 140097125480192 in file page0zip.cc line 3742
InnoDB: Failing assertion: !*data
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.
04:33:11 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=67108864
read_buffer_size=1048576
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 = 711926 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8df1f5]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x666c34]
/lib64/libpthread.so.0[0x3e7840f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x3e78032625]
/lib64/libc.so.6(abort+0x175)[0x3e78033e05]
/usr/sbin/mysqld[0x9aa618]
/usr/sbin/mysqld[0xa3e4bb]
/usr/sbin/mysqld[0x987997]
/usr/sbin/mysqld[0x9896e4]
/usr/sbin/mysqld[0xa5502f]
/usr/sbin/mysqld[0xa97210]
/usr/sbin/mysqld[0xa018f8]
/lib64/libpthread.so.0[0x3e78407aa1]
/lib64/libc.so.6(clone+0x6d)[0x3e780e893d]
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.
160603 04:33:11 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MySQL Daemon failed to start.
Starting mysqld: