2019-03-28T08:07:19.067038Z 2731508 [Note] Aborted connection 2731508 to db: 'ugcdata' user: 'ugcadmin' host: '10.25.151.201' (Got timeout reading communication packets)
2019-03-28T08:07:19.233105Z 2731513 [Note] Aborted connection 2731513 to db: 'ugcdata' user: 'ugcadmin' host: '10.25.151.201' (Got timeout reading communication packets)
2019-03-28T08:07:22.297221Z 2729172 [Note] Aborted connection 2729172 to db: 'ugcdata' user: 'ugcadmin' host: '10.25.151.206' (Got timeout reading communication packets)
08:07:45 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=4194304
read_buffer_size=2097152
max_used_connections=260
max_threads=500
thread_count=141
connection_count=135
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2078846 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fba18039fe0
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 = 7fbc190a0e28 thread_stack 0x80000
/usr/local/mysql5722/bin/mysqld(my_print_stacktrace+0x35)[0xf4b6d5]
/usr/local/mysql5722/bin/mysqld(handle_fatal_signal+0x4a4)[0x7d0d74]
/lib64/libpthread.so.0[0x30b340f710]
/usr/local/mysql5722/bin/mysqld(_ZN5mtr_t7Command17release_resourcesEv+0x12)[0xfea382]
/usr/local/mysql5722/bin/mysqld(_ZN5mtr_t7Command7executeEv+0xd6)[0xfece56]
/usr/local/mysql5722/bin/mysqld(_ZN5mtr_t6commitEv+0x71)[0xfed341]
/usr/local/mysql5722/bin/mysqld(_Z29row_ins_clust_index_entry_lowmmP12dict_index_tmP8dtuple_tmP9que_thr_tb+0x5b9)[0x1037399]
/usr/local/mysql5722/bin/mysqld(_Z25row_ins_clust_index_entryP12dict_index_tP8dtuple_tP9que_thr_tmb+0xb8)[0x103ce28]
/usr/local/mysql5722/bin/mysqld(_Z12row_ins_stepP9que_thr_t+0x35b)[0x103d34b]
/usr/local/mysql5722/bin/mysqld[0x1057895]
/usr/local/mysql5722/bin/mysqld(_ZN11ha_innobase9write_rowEPh+0x384)[0xf8ab44]
/usr/local/mysql5722/bin/mysqld(_ZN7handler12ha_write_rowEPh+0x13f)[0x81e5bf]
/usr/local/mysql5722/bin/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0xa7)[0xe9d4c7]
/usr/local/mysql5722/bin/mysqld(_ZN19Query_result_insert9send_dataER4ListI4ItemE+0xae)[0xe9dfde]
/usr/local/mysql5722/bin/mysqld[0xce4828]
/usr/local/mysql5722/bin/mysqld[0xce9cfe]
/usr/local/mysql5722/bin/mysqld(_Z10sub_selectP4JOINP7QEP_TABb+0x323)[0xceade3]
/usr/local/mysql5722/bin/mysqld(_ZN4JOIN4execEv+0x27a)[0xcea2ba]
/usr/local/mysql5722/bin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x250)[0xd54a10]
/usr/local/mysql5722/bin/mysqld(_ZN21Sql_cmd_insert_select7executeEP3THD+0x434)[0xe9c9b4]
/usr/local/mysql5722/bin/mysqld(_Z21mysql_execute_commandP3THDb+0xd82)[0xd163a2]
/usr/local/mysql5722/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x40d)[0xd1aaad]
/usr/local/mysql5722/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x119a)[0xd1bcca]
/usr/local/mysql5722/bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1cb74]
/usr/local/mysql5722/bin/mysqld(handle_connection+0x29c)[0xdedaec]
/usr/local/mysql5722/bin/mysqld(pfs_spawn_thread+0x174)[0x1256a94]
/lib64/libpthread.so.0[0x30b34079d1]
/lib64/libc.so.6(clone+0x6d)[0x30b30e8b6d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fba18031b20): is an invalid pointer
Connection ID (thread ID): 2731737
Status: NOT_KILLED

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.
2019-03-28T08:07:51.473262Z 0 [Warning] option 'max_binlog_size': unsigned value 2147483648 adjusted to 1073741824
2019-03-28T08:07:51.473547Z 0 [Warning] option 'max_binlog_size': unsigned value 2147483648 adjusted to 1073741824
2019-03-28T08:07:51.473718Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2019-03-28T08:07:51.473756Z 0 [Note] /usr/local/mysql5722/bin/mysqld (mysqld 5.7.22-log) starting as process 24661 ...
2019-03-28T08:07:51.489565Z 0 [Warning] Using pre 5.5 semantics to load error messages from /usr/local/mysql5722/share/english/.
2019-03-28T08:07:51.489575Z 0 [Warning] If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.
2019-03-28T08:07:51.560438Z 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2019-03-28T08:07:51.560493Z 0 [Warning] InnoDB: Using innodb_file_format_max is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2019-03-28T08:07:51.560670Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-03-28T08:07:51.560703Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-28T08:07:51.560739Z 0 [Note] InnoDB: Uses event mutexes
2019-03-28T08:07:51.560757Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2019-03-28T08:07:51.560786Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-03-28T08:07:51.560819Z 0 [Note] InnoDB: Using Linux native AIO
2019-03-28T08:07:51.563669Z 0 [Note] InnoDB: Number of pools: 1
2019-03-28T08:07:51.563993Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-03-28T08:07:51.568264Z 0 [Note] InnoDB: Initializing buffer pool, total size = 32G, instances = 8, chunk size = 128M
2019-03-28T08:07:51.568313Z 0 [Note] InnoDB: Setting NUMA memory policy to MPOL_INTERLEAVE
2019-03-28T08:07:58.512371Z 0 [Note] InnoDB: Setting NUMA memory policy to MPOL_DEFAULT
2019-03-28T08:07:58.512422Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-03-28T08:08:00.336662Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-03-28T08:08:00.388572Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-28T08:08:01.945425Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1155074982230
2019-03-28T08:08:02.131538Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155080224768
2019-03-28T08:08:02.314312Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155085467648
2019-03-28T08:08:02.494560Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155090710528
2019-03-28T08:08:02.676457Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155095953408
2019-03-28T08:08:02.857285Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155101196288
2019-03-28T08:08:03.029266Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155106439168
2019-03-28T08:08:03.352777Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155111682048
2019-03-28T08:08:03.648470Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155116924928
2019-03-28T08:08:03.840818Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155122167808
2019-03-28T08:08:04.039296Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155127410688
2019-03-28T08:08:04.239160Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155132653568
2019-03-28T08:08:04.437670Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155137896448
2019-03-28T08:08:04.636715Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155143139328
2019-03-28T08:08:04.844853Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155148382208
2019-03-28T08:08:05.054419Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155153625088
2019-03-28T08:08:05.258853Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155158867968
2019-03-28T08:08:05.460443Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155164110848
2019-03-28T08:08:05.659354Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155169353728
2019-03-28T08:08:05.866296Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155174596608
2019-03-28T08:08:06.073271Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155179839488
2019-03-28T08:08:06.273304Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155185082368
2019-03-28T08:08:06.476181Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155190325248
2019-03-28T08:08:06.675836Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155195568128
2019-03-28T08:08:06.881774Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155200811008
2019-03-28T08:08:07.085203Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155206053888
2019-03-28T08:08:07.281181Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155211296768
2019-03-28T08:08:07.482470Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155216539648
2019-03-28T08:08:07.679123Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155221782528
2019-03-28T08:08:07.885812Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155227025408
2019-03-28T08:08:08.089927Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155232268288
2019-03-28T08:08:08.295941Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155237511168
2019-03-28T08:08:08.498494Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155242754048
2019-03-28T08:08:08.706253Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155247996928
2019-03-28T08:08:08.907338Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155253239808
2019-03-28T08:08:09.112250Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155258482688
2019-03-28T08:08:09.318753Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155263725568
2019-03-28T08:08:09.521956Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155268968448
2019-03-28T08:08:09.719612Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155274211328
2019-03-28T08:08:09.919084Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155279454208
2019-03-28T08:08:10.125201Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155284697088
2019-03-28T08:08:10.331098Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155289939968
2019-03-28T08:08:10.533222Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155295182848
2019-03-28T08:08:10.733600Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155300425728
2019-03-28T08:08:10.943042Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155305668608
2019-03-28T08:08:11.146373Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155310911488
2019-03-28T08:08:11.355296Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155316154368
2019-03-28T08:08:11.561250Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155321397248
2019-03-28T08:08:11.765731Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155326640128
2019-03-28T08:08:11.963223Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155331883008
2019-03-28T08:08:12.166319Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155337125888
2019-03-28T08:08:12.370058Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155342368768
2019-03-28T08:08:12.567183Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155347611648
2019-03-28T08:08:12.770643Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155352854528
2019-03-28T08:08:12.976275Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155358097408
2019-03-28T08:08:13.185911Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155363340288
2019-03-28T08:08:13.391658Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155368583168
2019-03-28T08:08:13.597045Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155373826048
2019-03-28T08:08:13.802451Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155379068928
2019-03-28T08:08:14.003805Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155384311808
2019-03-28T08:08:14.209120Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155389554688
2019-03-28T08:08:14.417406Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155394797568
2019-03-28T08:08:14.620103Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155400040448
2019-03-28T08:08:14.824736Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155405283328
2019-03-28T08:08:15.023578Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155410526208
2019-03-28T08:08:15.233056Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155415769088
2019-03-28T08:08:15.436452Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155421011968
2019-03-28T08:08:15.644120Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155426254848
2019-03-28T08:08:15.848982Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155431497728
2019-03-28T08:08:16.057764Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155436740608
2019-03-28T08:08:16.253755Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155441983488
2019-03-28T08:08:16.458876Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155447226368
2019-03-28T08:08:16.666395Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155452469248
2019-03-28T08:08:16.874714Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155457712128
2019-03-28T08:08:17.081334Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155462955008
2019-03-28T08:08:17.284486Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155468197888
2019-03-28T08:08:17.496508Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155473440768
2019-03-28T08:08:17.700615Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155478683648
2019-03-28T08:08:17.910413Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155483926528
2019-03-28T08:08:18.114627Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155489169408
2019-03-28T08:08:18.315403Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155494412288
2019-03-28T08:08:18.512736Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155499655168
2019-03-28T08:08:18.721859Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155504898048
2019-03-28T08:08:18.925863Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155510140928
2019-03-28T08:08:19.133734Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155515383808
2019-03-28T08:08:19.340963Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155520626688
2019-03-28T08:08:19.546600Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155525869568
2019-03-28T08:08:19.750614Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155531112448
2019-03-28T08:08:19.952819Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155536355328
2019-03-28T08:08:20.158484Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155541598208
2019-03-28T08:08:20.368272Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155546841088
2019-03-28T08:08:20.574255Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155552083968
2019-03-28T08:08:20.773447Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155557326848
2019-03-28T08:08:20.980615Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155562569728
2019-03-28T08:08:21.181571Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155567812608
2019-03-28T08:08:21.383006Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155573055488
2019-03-28T08:08:21.589359Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155578298368
2019-03-28T08:08:21.787905Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155583541248
2019-03-28T08:08:21.998392Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155588784128
2019-03-28T08:08:22.196497Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155594027008
2019-03-28T08:08:22.408571Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155599269888
2019-03-28T08:08:22.616767Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155604512768
2019-03-28T08:08:22.825824Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155609755648
2019-03-28T08:08:23.026261Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155614998528
2019-03-28T08:08:23.232691Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155620241408
2019-03-28T08:08:23.450656Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155625484288
2019-03-28T08:08:23.662309Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155630727168
2019-03-28T08:08:23.871411Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155635970048
2019-03-28T08:08:24.074850Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155641212928
2019-03-28T08:08:24.281498Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155646455808
2019-03-28T08:08:24.492331Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155651698688
2019-03-28T08:08:24.698953Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155656941568
2019-03-28T08:08:24.907502Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155662184448
2019-03-28T08:08:25.120776Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155667427328
2019-03-28T08:08:25.328415Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155672670208
2019-03-28T08:08:25.542197Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155677913088
2019-03-28T08:08:25.756489Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155683155968
2019-03-28T08:08:25.973441Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155688398848
2019-03-28T08:08:26.183326Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155693641728
2019-03-28T08:08:26.390251Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155698884608
2019-03-28T08:08:26.613252Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155704127488
2019-03-28T08:08:26.824551Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155709370368
2019-03-28T08:08:27.034991Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155714613248
2019-03-28T08:08:27.250287Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155719856128
2019-03-28T08:08:27.453312Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155725099008
2019-03-28T08:08:27.660006Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155730341888
2019-03-28T08:08:27.868140Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155735584768
2019-03-28T08:08:28.073709Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155740827648
2019-03-28T08:08:28.283129Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155746070528
2019-03-28T08:08:28.492552Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155751313408
2019-03-28T08:08:28.693288Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155756556288
2019-03-28T08:08:28.902984Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155761799168
2019-03-28T08:08:29.112924Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155767042048
2019-03-28T08:08:29.315366Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155772284928
2019-03-28T08:08:29.554556Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155777527808
2019-03-28T08:08:29.758749Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155782770688
2019-03-28T08:08:29.970736Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155788013568
2019-03-28T08:08:30.176108Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155793256448
2019-03-28T08:08:30.384899Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155798499328
2019-03-28T08:08:30.602139Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155803742208
2019-03-28T08:08:30.810379Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155808985088
2019-03-28T08:08:31.024480Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155814227968
2019-03-28T08:08:31.237939Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155819470848
2019-03-28T08:08:31.454034Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155824713728
2019-03-28T08:08:31.663640Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155829956608
2019-03-28T08:08:31.878619Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155835199488
2019-03-28T08:08:32.088921Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155840442368
2019-03-28T08:08:32.302965Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155845685248
2019-03-28T08:08:32.509445Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155850928128
2019-03-28T08:08:32.721377Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155856171008
2019-03-28T08:08:32.932252Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155861413888
2019-03-28T08:08:33.140095Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155866656768
2019-03-28T08:08:33.345151Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155871899648
2019-03-28T08:08:33.556530Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155877142528
2019-03-28T08:08:33.770400Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155882385408
2019-03-28T08:08:33.983415Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155887628288
2019-03-28T08:08:34.203877Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155892871168
2019-03-28T08:08:34.411671Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155898114048
2019-03-28T08:08:34.614983Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155903356928
2019-03-28T08:08:34.832873Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155908599808
2019-03-28T08:08:35.040224Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155913842688
2019-03-28T08:08:35.255201Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155919085568
2019-03-28T08:08:35.462231Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155924328448
2019-03-28T08:08:35.676465Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155929571328
2019-03-28T08:08:35.885181Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155934814208
2019-03-28T08:08:36.096236Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155940057088
2019-03-28T08:08:36.316128Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155945299968
2019-03-28T08:08:36.524819Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155950542848
2019-03-28T08:08:36.737890Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155955785728
2019-03-28T08:08:36.951592Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155961028608
2019-03-28T08:08:37.168029Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155966271488
2019-03-28T08:08:37.376237Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155971514368
2019-03-28T08:08:37.588752Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155976757248
2019-03-28T08:08:37.793834Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155982000128
2019-03-28T08:08:38.011419Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155987243008
2019-03-28T08:08:38.222121Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155992485888
2019-03-28T08:08:38.436592Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1155997728768
2019-03-28T08:08:38.651295Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156002971648
2019-03-28T08:08:38.865917Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156008214528
2019-03-28T08:08:39.073477Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156013457408
2019-03-28T08:08:39.289519Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156018700288
2019-03-28T08:08:39.500525Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156023943168
2019-03-28T08:08:39.711937Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156029186048
2019-03-28T08:08:39.917704Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156034428928
2019-03-28T08:08:40.121741Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156039671808
2019-03-28T08:08:40.342256Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156044914688
2019-03-28T08:08:40.550798Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156050157568
2019-03-28T08:08:40.767492Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156055400448
2019-03-28T08:08:40.979247Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156060643328
2019-03-28T08:08:41.181027Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156065886208
2019-03-28T08:08:41.401825Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156071129088
2019-03-28T08:08:41.616384Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156076371968
2019-03-28T08:08:41.834085Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156081614848
2019-03-28T08:08:42.047009Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156086857728
2019-03-28T08:08:42.266075Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156092100608
2019-03-28T08:08:42.473311Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156097343488
2019-03-28T08:08:42.676362Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156102586368
2019-03-28T08:08:42.889649Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156107829248
2019-03-28T08:08:43.097991Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156113072128
2019-03-28T08:08:43.310347Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156118315008
2019-03-28T08:08:43.524779Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156123557888
2019-03-28T08:08:43.739526Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156128800768
2019-03-28T08:08:43.943453Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156134043648
2019-03-28T08:08:44.163419Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156139286528
2019-03-28T08:08:44.367409Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156144529408
2019-03-28T08:08:44.580620Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156149772288
2019-03-28T08:08:44.798474Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156155015168
2019-03-28T08:08:45.019263Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156160258048
2019-03-28T08:08:45.233894Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156165500928
2019-03-28T08:08:45.437466Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156170743808
2019-03-28T08:08:45.658005Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156175986688
2019-03-28T08:08:45.871842Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156181229568
2019-03-28T08:08:46.092466Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156186472448
2019-03-28T08:08:46.309346Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156191715328
2019-03-28T08:08:46.518794Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156196958208
2019-03-28T08:08:46.738531Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156202201088
2019-03-28T08:08:46.950580Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156207443968
2019-03-28T08:08:47.166277Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156212686848
2019-03-28T08:08:47.375761Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156217929728
2019-03-28T08:08:47.589446Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156223172608
2019-03-28T08:08:47.802456Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156228415488
2019-03-28T08:08:48.016133Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156233658368
2019-03-28T08:08:48.234335Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156238901248
2019-03-28T08:08:48.445774Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156244144128
2019-03-28T08:08:48.661473Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156249387008
2019-03-28T08:08:48.872418Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156254629888
2019-03-28T08:08:49.085358Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156259872768
2019-03-28T08:08:49.295085Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156265115648
2019-03-28T08:08:49.505338Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156270358528
2019-03-28T08:08:49.721453Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156275601408
2019-03-28T08:08:49.933014Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156280844288
2019-03-28T08:08:50.147963Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156286087168
2019-03-28T08:08:50.365665Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156291330048
2019-03-28T08:08:50.574094Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156296572928
2019-03-28T08:08:50.789437Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156301815808
2019-03-28T08:08:50.998103Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156307058688
2019-03-28T08:08:51.209787Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156312301568
2019-03-28T08:08:51.426757Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156317544448
2019-03-28T08:08:51.635891Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156322787328
2019-03-28T08:08:51.856511Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156328030208
2019-03-28T08:08:52.066727Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156333273088
2019-03-28T08:08:52.271845Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156338515968
2019-03-28T08:08:52.481043Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156343758848
2019-03-28T08:08:52.691079Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156349001728
2019-03-28T08:08:52.903645Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156354244608
2019-03-28T08:08:53.120346Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156359487488
2019-03-28T08:08:53.329302Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156364730368
2019-03-28T08:08:53.546572Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156369973248
2019-03-28T08:08:53.757777Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156375216128
2019-03-28T08:08:53.976429Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156380459008
2019-03-28T08:08:54.175710Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156385701888
2019-03-28T08:08:54.381063Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156390944768
2019-03-28T08:08:54.596228Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156396187648
2019-03-28T08:08:54.810855Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156401430528
2019-03-28T08:08:55.030333Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156406673408
2019-03-28T08:08:55.249931Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156411916288
2019-03-28T08:08:55.455625Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156417159168
2019-03-28T08:08:55.664710Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156422402048
2019-03-28T08:08:55.882718Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156427644928
2019-03-28T08:08:56.094427Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156432887808
2019-03-28T08:08:56.297117Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156438130688
2019-03-28T08:08:56.504766Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156443373568
2019-03-28T08:08:56.723002Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156448616448
2019-03-28T08:08:56.939276Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156453859328
2019-03-28T08:08:57.162007Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156459102208
2019-03-28T08:08:57.377993Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156464345088
2019-03-28T08:08:57.593060Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156469587968
2019-03-28T08:08:57.795162Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156474830848
2019-03-28T08:08:58.010983Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156480073728
2019-03-28T08:08:58.221296Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156485316608
2019-03-28T08:08:58.436480Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156490559488
2019-03-28T08:08:58.651145Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156495802368
2019-03-28T08:08:58.863888Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156501045248
2019-03-28T08:08:59.072596Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156506288128
2019-03-28T08:08:59.281660Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156511531008
2019-03-28T08:08:59.493525Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156516773888
2019-03-28T08:08:59.703790Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156522016768
2019-03-28T08:08:59.914248Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156527259648
2019-03-28T08:09:00.124857Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156532502528
2019-03-28T08:09:00.328763Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156537745408
2019-03-28T08:09:00.543095Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156542988288
2019-03-28T08:09:00.763292Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156548231168
2019-03-28T08:09:00.973202Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156553474048
2019-03-28T08:09:01.179227Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156558716928
2019-03-28T08:09:01.394283Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156563959808
2019-03-28T08:09:01.478910Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 1156566088917
2019-03-28T08:09:01.479902Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-03-28T08:09:01.479933Z 0 [Note] InnoDB: Starting crash recovery.
2019-03-28T08:09:03.272386Z 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 4211 row operations to undo
2019-03-28T08:09:03.272457Z 0 [Note] InnoDB: Trx id counter is 6745850880
2019-03-28T08:09:03.273839Z 0 [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 7
1 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 
2019-03-28T08:09:24.162063Z 0 [Note] InnoDB: Apply batch completed
2019-03-28T08:09:24.162148Z 0 [Note] InnoDB: Last MySQL binlog file position 0 314570537, file name mysql-bin.000154
2019-03-28T08:09:24.523553Z 0 [Note] InnoDB: Starting in background the rollback of uncommitted transactions
2019-03-28T08:09:24.523690Z 0 [Note] InnoDB: Rolling back trx with id 6745848577, 4211 rows to undo

InnoDB: Progress in percents: 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 572019-03-28T08:09:24.730204Z 0 [Note] InnoD
B: Removed temporary tablespace data file: "ibtmp1"
2019-03-28T08:09:24.730273Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-03-28T08:09:24.730402Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 782019-03-28T08:09:24.805547Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-03-28T08:09:24.808151Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-03-28T08:09:24.808191Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-03-28T08:09:24.817247Z 0 [Note] InnoDB: Waiting for purge to start
 79 80 81 82 83 84 85 86 87 88 89 90 91 92 932019-03-28T08:09:24.867464Z 0 [Note] InnoDB: 5.7.22 started; log sequence number 1156566088917
2019-03-28T08:09:24.867654Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 84531ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
 942019-03-28T08:09:24.868158Z 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysql/ib_buffer_pool
 95 96 97 98 99 1002019-03-28T08:09:24.889079Z 0 [Note] Plugin 'FEDERATED' is disabled.
2019-03-28T08:09:24.893678Z 0 [Note] InnoDB: Rollback of trx with id 6745848577 completed
2019-03-28T08:09:24.893743Z 0 [Note] InnoDB: Rollback of non-prepared transactions completed
2019-03-28T08:09:24.905320Z 0 [ERROR] Function 'validate_password' already exists
2019-03-28T08:09:24.905374Z 0 [ERROR] Couldn't load plugin named 'validate_password' with soname 'validate_password.so'.
2019-03-28T08:09:24.925899Z 0 [ERROR] Function 'validate_password' already exists
2019-03-28T08:09:24.925967Z 0 [Warning] Couldn't load plugin named 'validate_password' with soname 'validate_password.so'.
2019-03-28T08:09:24.926381Z 0 [Warning] Plugin validate_password reported: 'Dictionary file not specified'
2019-03-28T08:09:24.926879Z 0 [Note] Recovering after a crash using /log/mysql/binary/mysql-bin
2019-03-28T08:09:26.181047Z 0 [Note] Starting crash recovery...
2019-03-28T08:09:26.181369Z 0 [Note] Crash recovery finished.
2019-03-28T08:09:26.940123Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2019-03-28T08:09:26.940204Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2019-03-28T08:09:26.940379Z 0 [Note] IPv6 is available.
2019-03-28T08:09:26.940421Z 0 [Note]   - '::' resolves to '::';
2019-03-28T08:09:26.940508Z 0 [Note] Server socket created on IP: '::'.
2019-03-28T08:09:27.162793Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.163013Z 0 [Warning] 'user' entry 'backup@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.163123Z 0 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.163162Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.197251Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.197313Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.198164Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.342303Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.342399Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2019-03-28T08:09:27.430129Z 0 [Warning] Recovery from master pos 264859003 and file mysql-bin.000148 for channel ''. Previous relay log pos and relay log file had been set to 407, /log/mysql/relay/slave-relay-bin.000348 respectively.
2019-03-28T08:09:27.431418Z 1 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for 
START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2019-03-28T08:09:27.432808Z 1 [Note] Slave I/O thread for channel '': connected to master 'repl@10.25.151.215:3306',replication started in log 'mysql-bin.000148' at position 264859003
2019-03-28T08:09:27.441600Z 2 [Note] Slave SQL thread for channel '' initialized, starting replication in log 'mysql-bin.000148' at position 264859003, relay log '/log/mysql/relay/slave-relay-bin.000349' position: 4
2019-03-28T08:09:27.596467Z 0 [Note] Event Scheduler: Loaded 0 events
2019-03-28T08:09:27.597061Z 0 [Note] /usr/local/mysql5722/bin/mysqld: ready for connections.
Version: '5.7.22-log'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server (GPL)
2019-03-28T08:09:50.797479Z 14 [Note] Start binlog_dump to master_thread_id(14) slave_server(2153306), pos(, 4)
2019-03-28T08:12:16.387815Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190328 16:12:16