質問編集履歴
2
ログの変更
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -238,35 +238,157 @@
|
|
|
238
238
|
|
|
239
239
|
```
|
|
240
240
|
|
|
241
|
-
|
|
242
|
-
|
|
243
|
-
|
|
244
|
-
|
|
245
|
-
|
|
246
|
-
|
|
247
|
-
|
|
248
|
-
|
|
249
|
-
|
|
250
|
-
|
|
251
|
-
|
|
252
|
-
|
|
253
|
-
|
|
254
|
-
|
|
255
|
-
|
|
256
|
-
|
|
257
|
-
|
|
258
|
-
|
|
259
|
-
|
|
260
|
-
|
|
261
|
-
20
|
|
262
|
-
|
|
263
|
-
2
|
|
241
|
+
￥2020-04-30T16:06:02.6NZ mysqld_safe Logging to '/var/log/mysqld.log'.
|
|
242
|
+
|
|
243
|
+
2020-04-30T16:06:02.6NZ mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
|
|
244
|
+
|
|
245
|
+
2020-04-30T16:06:03.364253Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
|
|
246
|
+
|
|
247
|
+
2020-04-30T16:06:03.365590Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
|
|
248
|
+
|
|
249
|
+
2020-04-30T16:06:03.366645Z 0 [Note] /usr/local/Cellar/mysql@5.7/5.7.29/bin/mysqld (mysqld 5.7.29) starting as process 8555 ...
|
|
250
|
+
|
|
251
|
+
2020-04-30T16:06:03.382354Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
|
|
252
|
+
|
|
253
|
+
2020-04-30T16:06:03.391224Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
|
254
|
+
|
|
255
|
+
2020-04-30T16:06:03.391274Z 0 [Note] InnoDB: Uses event mutexes
|
|
256
|
+
|
|
257
|
+
2020-04-30T16:06:03.391288Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
|
|
258
|
+
|
|
259
|
+
2020-04-30T16:06:03.391300Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
|
|
260
|
+
|
|
261
|
+
2020-04-30T16:06:03.392806Z 0 [Note] InnoDB: Number of pools: 1
|
|
262
|
+
|
|
263
|
+
2020-04-30T16:06:03.395250Z 0 [Note] InnoDB: Using CPU crc32 instructions
|
|
264
|
+
|
|
265
|
+
2020-04-30T16:06:03.397396Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
|
|
266
|
+
|
|
267
|
+
2020-04-30T16:06:03.415071Z 0 [Note] InnoDB: Completed initialization of buffer pool
|
|
268
|
+
|
|
269
|
+
2020-04-30T16:06:03.460536Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
|
|
270
|
+
|
|
271
|
+
2020-05-01 01:06:03 0x11a5235c0 InnoDB: Assertion failure in thread 4736562624 in file ut0ut.cc line 918
|
|
272
|
+
|
|
273
|
+
InnoDB: We intentionally generate a memory trap.
|
|
274
|
+
|
|
275
|
+
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
|
|
276
|
+
|
|
277
|
+
InnoDB: If you get repeated assertion failures or crashes, even
|
|
278
|
+
|
|
279
|
+
InnoDB: immediately after the mysqld startup, there may be
|
|
280
|
+
|
|
281
|
+
InnoDB: corruption in the InnoDB tablespace. Please refer to
|
|
282
|
+
|
|
283
|
+
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
|
|
284
|
+
|
|
285
|
+
InnoDB: about forcing recovery.
|
|
286
|
+
|
|
287
|
+
16:06:03 UTC - mysqld got signal 6 ;
|
|
288
|
+
|
|
289
|
+
This could be because you hit a bug. It is also possible that this binary
|
|
290
|
+
|
|
291
|
+
or one of the libraries it was linked against is corrupt, improperly built,
|
|
292
|
+
|
|
293
|
+
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
294
|
+
|
|
295
|
+
Attempting to collect some information that could help diagnose the problem.
|
|
296
|
+
|
|
297
|
+
As this is a crash and something is definitely wrong, the information
|
|
298
|
+
|
|
299
|
+
collection process might fail.
|
|
300
|
+
|
|
301
|
+
|
|
302
|
+
|
|
303
|
+
key_buffer_size=8388608
|
|
304
|
+
|
|
305
|
+
read_buffer_size=131072
|
|
306
|
+
|
|
307
|
+
max_used_connections=0
|
|
308
|
+
|
|
309
|
+
max_threads=151
|
|
310
|
+
|
|
311
|
+
|
|
312
|
+
|
|
313
|
+
|
|
314
|
+
|
|
315
|
+
thread_count=0
|
|
316
|
+
|
|
317
|
+
connection_count=0
|
|
318
|
+
|
|
319
|
+
It is possible that mysqld could use up to
|
|
320
|
+
|
|
321
|
+
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68221 K bytes of memory
|
|
322
|
+
|
|
323
|
+
Hope that's ok; if not, decrease some variables in the equation.
|
|
324
|
+
|
|
325
|
+
|
|
326
|
+
|
|
327
|
+
Thread pointer: 0x0
|
|
328
|
+
|
|
329
|
+
Attempting backtrace. You can use the following information to find out
|
|
330
|
+
|
|
331
|
+
where mysqld died. If you see no messages after this, something went
|
|
332
|
+
|
|
333
|
+
terribly wrong...
|
|
334
|
+
|
|
335
|
+
stack_bottom = 0 thread_stack 0x40000
|
|
336
|
+
|
|
337
|
+
0 mysqld 0x000000010b9e5139 my_print_stacktrace + 58
|
|
338
|
+
|
|
339
|
+
1 mysqld 0x000000010b964d1b handle_fatal_signal + 696
|
|
340
|
+
|
|
341
|
+
2 libsystem_platform.dylib 0x00007fff7b8bfb5d _sigtramp + 29
|
|
342
|
+
|
|
343
|
+
3 ??? 0x0000000000000000 0x0 + 0
|
|
344
|
+
|
|
345
|
+
4 libsystem_c.dylib 0x00007fff7b7796a6 abort + 127
|
|
346
|
+
|
|
347
|
+
5 mysqld 0x000000010bc91f88 _Z23ut_dbg_assertion_failedPKcS0_m + 161
|
|
348
|
+
|
|
349
|
+
6 mysqld 0x000000010bbd5947 _ZN2ib5fatalD2Ev + 91
|
|
350
|
+
|
|
351
|
+
7 mysqld 0x000000010bbd5985 _ZN2ib5fatalD1Ev + 9
|
|
352
|
+
|
|
353
|
+
8 mysqld 0x000000010ba7d55a _ZL18fil_node_open_fileP10fil_node_t + 2411
|
|
354
|
+
|
|
355
|
+
9 mysqld 0x000000010ba86e6e _ZL23fil_node_prepare_for_ioP10fil_node_tP12fil_system_tP11fil_space_t + 191
|
|
356
|
+
|
|
357
|
+
10 mysqld 0x000000010ba87556 _Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_ + 796
|
|
358
|
+
|
|
359
|
+
11 mysqld 0x000000010ba4e28c _ZL17buf_read_page_lowP7dberr_tbmmRK9page_id_tRK11page_size_tb + 408
|
|
360
|
+
|
|
361
|
+
12 mysqld 0x000000010ba4e3e3 _Z13buf_read_pageRK9page_id_tRK11page_size_t + 56
|
|
362
|
+
|
|
363
|
+
13 mysqld 0x000000010ba39cf7 _Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb + 953
|
|
364
|
+
|
|
365
|
+
14 mysqld 0x000000010bbc34fa _Z31trx_rseg_get_n_undo_tablespacesPm + 251
|
|
366
|
+
|
|
367
|
+
15 mysqld 0x000000010bba6f4b _Z34innobase_start_or_create_for_mysqlv + 6608
|
|
368
|
+
|
|
369
|
+
16 mysqld 0x000000010bad6a25 _ZL13innobase_initPv + 3636
|
|
370
|
+
|
|
371
|
+
17 mysqld 0x000000010b458508 _Z24ha_initialize_handlertonP13st_plugin_int + 78
|
|
372
|
+
|
|
373
|
+
18 mysqld 0x000000010b8b41fd _ZL17plugin_initializeP13st_plugin_int + 79
|
|
374
|
+
|
|
375
|
+
19 mysqld 0x000000010b8b3cfb _Z40plugin_register_builtin_and_init_core_sePiPPc + 707
|
|
376
|
+
|
|
377
|
+
20 mysqld 0x000000010b959cfd _Z11mysqld_mainiPPc + 2912
|
|
378
|
+
|
|
379
|
+
21 libdyld.dylib 0x00007fff7b6d43d5 start + 1
|
|
264
380
|
|
|
265
381
|
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
|
266
382
|
|
|
267
383
|
information that should help you find out what is causing the crash.
|
|
268
384
|
|
|
269
|
-
2020-04-30T16:06:03.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/XXXXX.pid ended
|
|
385
|
+
2020-04-30T16:06:03.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/XXXXXX.local.pid ended
|
|
386
|
+
|
|
387
|
+
|
|
388
|
+
|
|
389
|
+
|
|
390
|
+
|
|
391
|
+
|
|
270
392
|
|
|
271
393
|
```
|
|
272
394
|
|
1
ログの箇所を追加
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -224,6 +224,54 @@
|
|
|
224
224
|
|
|
225
225
|
|
|
226
226
|
|
|
227
|
+
|
|
228
|
+
|
|
229
|
+
|
|
230
|
+
|
|
231
|
+
追記
|
|
232
|
+
|
|
233
|
+
|
|
234
|
+
|
|
235
|
+
ログを見ることができました。
|
|
236
|
+
|
|
237
|
+
よくわかっていないのですが、貼り付けておきます。
|
|
238
|
+
|
|
239
|
+
```
|
|
240
|
+
|
|
241
|
+
$ vi /var/log/mysqld.log
|
|
242
|
+
|
|
243
|
+
|
|
244
|
+
|
|
245
|
+
12 mysqld 0x000000010ba4e3e3 _Z13buf_read_pageRK9page_id_tRK11page_size_t + 56
|
|
246
|
+
|
|
247
|
+
13 mysqld 0x000000010ba39cf7 _Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb + 953
|
|
248
|
+
|
|
249
|
+
14 mysqld 0x000000010bbc34fa _Z31trx_rseg_get_n_undo_tablespacesPm + 251
|
|
250
|
+
|
|
251
|
+
15 mysqld 0x000000010bba6f4b _Z34innobase_start_or_create_for_mysqlv + 6608
|
|
252
|
+
|
|
253
|
+
16 mysqld 0x000000010bad6a25 _ZL13innobase_initPv + 3636
|
|
254
|
+
|
|
255
|
+
17 mysqld 0x000000010b458508 _Z24ha_initialize_handlertonP13st_plugin_int + 78
|
|
256
|
+
|
|
257
|
+
18 mysqld 0x000000010b8b41fd _ZL17plugin_initializeP13st_plugin_int + 79
|
|
258
|
+
|
|
259
|
+
19 mysqld 0x000000010b8b3cfb _Z40plugin_register_builtin_and_init_core_sePiPPc + 707
|
|
260
|
+
|
|
261
|
+
20 mysqld 0x000000010b959cfd _Z11mysqld_mainiPPc + 2912
|
|
262
|
+
|
|
263
|
+
21 libdyld.dylib 0x00007fff7b6d43d5 start + 1
|
|
264
|
+
|
|
265
|
+
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
|
266
|
+
|
|
267
|
+
information that should help you find out what is causing the crash.
|
|
268
|
+
|
|
269
|
+
2020-04-30T16:06:03.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/XXXXX.pid ended
|
|
270
|
+
|
|
271
|
+
```
|
|
272
|
+
|
|
273
|
+
|
|
274
|
+
|
|
227
275
|
何がどうなっているのか
|
|
228
276
|
|
|
229
277
|
さっぱり分からなくなってきてしまいまい途方に暮れています。
|