お世話になっております。曾利田と申します。 mysqld がクラッシュし MySQL エラーログを確認したところ mroonga の amrn_free_long_term_share 関数から mysqld の my_hash_delete 関数を呼び出す部分が関連しているようなのですが 類似事象等が見当たりませんでしたので、問合せに至っています。 現状、事象の発生は１回のみとなり、再現は見られません。 なにかわかることがあればご教示いただきたいです。 以下に環境の情報と MySQL クラッシュ時のエラーログを記載します。 どうぞ、よろしくお願いいたします。 ■ 環境 ・CentOS 64bit 7.4 ・MySQL 5.7.19 ・mroonga 7.05-2 ■ MySQL エラーログ 04:13:51 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=8388608 read_buffer_size=131072 max_used_connections=353 max_threads=6000 thread_count=13 connection_count=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 7000254 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f88c01150b0 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 = 7f8b211e0e70 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf1126b] /usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7c4141] /lib64/libpthread.so.0(+0xf5e0)[0x7fb2608215e0] /usr/sbin/mysqld[0x14281ed] /usr/sbin/mysqld[0xef2c3d] /usr/sbin/mysqld(my_hash_delete+0x8d)[0xef37cd] /usr/lib64/mysql/plugin/ha_mroonga.so(mrn_free_long_term_share+0x3f)[0x7f8b23bd947f] /usr/lib64/mysql/plugin/ha_mroonga.so(_ZN10ha_mroonga5closeEv+0x134)[0x7f8b23bbeb04] /usr/sbin/mysqld(_Z8closefrmP5TABLEb+0x129)[0xd77309] /usr/sbin/mysqld(_Z18intern_close_tableP5TABLE+0x37)[0xc82fc7] /usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x1286)[0xc864d6] /usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x612)[0xc8cf62] /usr/sbin/mysqld(_Z21open_tables_for_queryP3THDP10TABLE_LISTj+0x5a)[0xc8d8ba] /usr/sbin/mysqld[0x7864b8] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x446c)[0xcdfe6c] /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3b5)[0xce23a5] /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xa7a)[0xce2e9a] /usr/sbin/mysqld(_Z10do_commandP3THD+0x19f)[0xce48df] /usr/sbin/mysqld(handle_connection+0x288)[0xda4308] /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x1286874] /lib64/libpthread.so.0(+0x7e25)[0x7fb260819e25] /lib64/libc.so.6(clone+0x6d)[0x7fb25f2d634d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f88c0123be0): select MARKET_UPDATE_ORDER from D_MARKET_UPDATE_TIME_9 where MAC_ADRS = '9aa140ee8739' Connection ID (thread ID): 2311699699 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-24T13:13:54.370918+09:00 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2019-03-24T13:13:54.374441+09:00 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set. 2019-03-24T13:13:54.378634+09:00 0 [Note] /usr/sbin/mysqld (mysqld 5.7.19-enterprise-commercial-advanced-log) starting as process 50946 ... 2019-03-24T13:13:54.429792+09:00 0 [Note] InnoDB: PUNCH HOLE support available 2019-03-24T13:13:54.433760+09:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-03-24T13:13:54.433796+09:00 0 [Note] InnoDB: Uses event mutexes 2019-03-24T13:13:54.433809+09:00 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2019-03-24T13:13:54.433821+09:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.3 2019-03-24T13:13:54.433831+09:00 0 [Note] InnoDB: Using Linux native AIO 2019-03-24T13:13:54.445312+09:00 0 [Note] InnoDB: Number of pools: 1 2019-03-24T13:13:54.445631+09:00 0 [Note] InnoDB: Using CPU crc32 instructions 2019-03-24T13:13:54.457758+09:00 0 [Note] InnoDB: Initializing buffer pool, total size = 150G, instances = 8, chunk size = 128M 2019-03-24T13:13:54.458079+09:00 0 [Note] InnoDB: Setting NUMA memory policy to MPOL_INTERLEAVE 2019-03-24T13:14:03.303010+09:00 0 [Note] InnoDB: Setting NUMA memory policy to MPOL_DEFAULT 2019-03-24T13:14:03.303094+09:00 0 [Note] InnoDB: Completed initialization of buffer pool 2019-03-24T13:14:04.217078+09:00 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-24T13:14:04.235742+09:00 0 [Note] InnoDB: Highest supported file format is Barracuda. 2019-03-24T13:14:04.872971+09:00 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7587821167489 2019-03-24T13:14:05.202517+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587826409984 2019-03-24T13:14:05.245200+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587831652864 2019-03-24T13:14:05.287991+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587836895744 2019-03-24T13:14:05.329635+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587842138624 2019-03-24T13:14:05.372009+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587847381504 2019-03-24T13:14:05.414927+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587852624384 2019-03-24T13:14:05.459017+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587857867264 2019-03-24T13:14:05.502867+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587863110144 2019-03-24T13:14:05.546049+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587868353024 2019-03-24T13:14:05.591388+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587873595904 2019-03-24T13:14:05.636137+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587878838784 2019-03-24T13:14:05.682780+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587884081664 2019-03-24T13:14:05.726268+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587889324544 2019-03-24T13:14:05.770198+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587894567424 2019-03-24T13:14:05.814158+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587899810304 2019-03-24T13:14:05.857006+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587905053184 2019-03-24T13:14:05.899913+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587910296064 2019-03-24T13:14:05.942464+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587915538944 2019-03-24T13:14:05.984820+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587920781824 2019-03-24T13:14:06.028015+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587926024704 2019-03-24T13:14:06.072872+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587931267584 2019-03-24T13:14:06.116653+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587936510464 2019-03-24T13:14:06.163284+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587941753344 2019-03-24T13:14:06.207784+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587946996224 2019-03-24T13:14:06.250400+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587952239104 2019-03-24T13:14:06.293998+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587957481984 2019-03-24T13:14:06.337636+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587962724864 2019-03-24T13:14:06.380310+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587967967744 2019-03-24T13:14:06.424167+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587973210624 2019-03-24T13:14:06.469732+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587978453504 2019-03-24T13:14:06.514039+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587983696384 2019-03-24T13:14:06.559457+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587988939264 2019-03-24T13:14:06.603292+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587994182144 2019-03-24T13:14:06.647257+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7587999425024 2019-03-24T13:14:06.690219+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588004667904 2019-03-24T13:14:06.737551+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588009910784 2019-03-24T13:14:06.783082+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588015153664 2019-03-24T13:14:06.827464+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588020396544 2019-03-24T13:14:06.871111+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588025639424 2019-03-24T13:14:06.915985+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588030882304 2019-03-24T13:14:06.967250+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588036125184 2019-03-24T13:14:07.012214+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588041368064 2019-03-24T13:14:07.058918+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588046610944 2019-03-24T13:14:07.104137+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588051853824 2019-03-24T13:14:07.150215+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588057096704 2019-03-24T13:14:07.195627+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588062339584 2019-03-24T13:14:07.239220+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588067582464 2019-03-24T13:14:07.286482+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588072825344 2019-03-24T13:14:07.332778+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588078068224 2019-03-24T13:14:07.376084+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588083311104 2019-03-24T13:14:07.421224+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588088553984 2019-03-24T13:14:07.465838+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588093796864 2019-03-24T13:14:07.512030+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588099039744 2019-03-24T13:14:07.559506+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588104282624 2019-03-24T13:14:07.606179+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588109525504 2019-03-24T13:14:07.655579+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588114768384 2019-03-24T13:14:07.700827+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588120011264 2019-03-24T13:14:07.749125+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588125254144 2019-03-24T13:14:07.796102+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588130497024 2019-03-24T13:14:07.840596+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588135739904 2019-03-24T13:14:07.889661+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588140982784 2019-03-24T13:14:07.936829+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588146225664 2019-03-24T13:14:07.985005+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588151468544 2019-03-24T13:14:08.032905+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588156711424 2019-03-24T13:14:08.078845+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588161954304 2019-03-24T13:14:08.125910+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588167197184 2019-03-24T13:14:08.171526+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588172440064 2019-03-24T13:14:08.218473+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588177682944 2019-03-24T13:14:08.264287+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588182925824 2019-03-24T13:14:08.310062+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588188168704 2019-03-24T13:14:08.354115+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588193411584 2019-03-24T13:14:08.401773+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588198654464 2019-03-24T13:14:08.446788+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588203897344 2019-03-24T13:14:08.492750+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588209140224 2019-03-24T13:14:08.539064+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588214383104 2019-03-24T13:14:08.583919+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588219625984 2019-03-24T13:14:08.630563+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588224868864 2019-03-24T13:14:08.676004+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588230111744 2019-03-24T13:14:08.722562+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588235354624 2019-03-24T13:14:08.768494+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588240597504 2019-03-24T13:14:08.815521+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588245840384 2019-03-24T13:14:08.861233+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588251083264 2019-03-24T13:14:08.905161+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588256326144 2019-03-24T13:14:08.952193+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588261569024 2019-03-24T13:14:08.996538+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588266811904 2019-03-24T13:14:09.042456+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588272054784 2019-03-24T13:14:09.092048+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588277297664 2019-03-24T13:14:09.139807+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588282540544 2019-03-24T13:14:09.185673+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588287783424 2019-03-24T13:14:09.230108+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588293026304 2019-03-24T13:14:09.275239+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588298269184 2019-03-24T13:14:09.321284+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588303512064 2019-03-24T13:14:09.367056+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588308754944 2019-03-24T13:14:09.412862+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588313997824 2019-03-24T13:14:09.458945+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588319240704 2019-03-24T13:14:09.505577+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588324483584 2019-03-24T13:14:09.550080+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588329726464 2019-03-24T13:14:09.595707+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588334969344 2019-03-24T13:14:09.643192+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588340212224 2019-03-24T13:14:09.688705+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588345455104 2019-03-24T13:14:09.735212+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588350697984 2019-03-24T13:14:09.782310+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588355940864 2019-03-24T13:14:09.831204+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588361183744 2019-03-24T13:14:09.878386+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588366426624 2019-03-24T13:14:09.923896+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588371669504 2019-03-24T13:14:09.969360+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588376912384 2019-03-24T13:14:10.014730+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588382155264 2019-03-24T13:14:10.060650+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588387398144 2019-03-24T13:14:10.105386+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588392641024 2019-03-24T13:14:10.151191+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588397883904 2019-03-24T13:14:10.201978+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588403126784 2019-03-24T13:14:10.250110+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588408369664 2019-03-24T13:14:10.298630+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588413612544 2019-03-24T13:14:10.344578+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588418855424 2019-03-24T13:14:10.391318+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588424098304 2019-03-24T13:14:10.439108+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588429341184 2019-03-24T13:14:10.488601+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588434584064 2019-03-24T13:14:10.544425+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588439826944 2019-03-24T13:14:10.599551+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588445069824 2019-03-24T13:14:10.650222+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588450312704 2019-03-24T13:14:10.702451+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588455555584 2019-03-24T13:14:10.748630+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588460798464 2019-03-24T13:14:10.797302+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588466041344 2019-03-24T13:14:10.842987+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588471284224 2019-03-24T13:14:10.886525+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588476527104 2019-03-24T13:14:10.933474+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588481769984 2019-03-24T13:14:10.983602+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588487012864 2019-03-24T13:14:11.027992+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588492255744 2019-03-24T13:14:11.072810+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588497498624 2019-03-24T13:14:11.124149+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588502741504 2019-03-24T13:14:11.184978+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588507984384 2019-03-24T13:14:11.242561+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588513227264 2019-03-24T13:14:11.343238+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588518470144 2019-03-24T13:14:11.452408+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588523713024 2019-03-24T13:14:11.571864+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588528955904 2019-03-24T13:14:11.688861+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588534198784 2019-03-24T13:14:11.769089+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588539441664 2019-03-24T13:14:11.866310+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588544684544 2019-03-24T13:14:11.973437+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588549927424 2019-03-24T13:14:12.082084+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588555170304 2019-03-24T13:14:12.164160+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588560413184 2019-03-24T13:14:12.224124+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588565656064 2019-03-24T13:14:12.273694+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588570898944 2019-03-24T13:14:12.320247+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588576141824 2019-03-24T13:14:12.364091+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588581384704 2019-03-24T13:14:12.410533+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588586627584 2019-03-24T13:14:12.456023+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588591870464 2019-03-24T13:14:12.479143+09:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 7588594488897 2019-03-24T13:14:12.479553+09:00 0 [Note] InnoDB: Database was not shutdown normally! 2019-03-24T13:14:12.479563+09:00 0 [Note] InnoDB: Starting crash recovery. -- 曾利田勁介 <keisu****@kccs*****>
