質問編集履歴
1
mysqld.logエラー全文やmy.cnfを更新
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -12,41 +12,155 @@
|
|
|
12
12
|
|
|
13
13
|
|
|
14
14
|
|
|
15
|
-
/
|
|
16
|
-
|
|
17
|
-
```
|
|
18
|
-
|
|
19
|
-
2018-10-1
|
|
20
|
-
|
|
21
|
-
2018-10-1
|
|
22
|
-
|
|
23
|
-
2018-10-1
|
|
24
|
-
|
|
25
|
-
2018-10-1
|
|
26
|
-
|
|
27
|
-
2018-10-1
|
|
28
|
-
|
|
29
|
-
2018-10-1
|
|
30
|
-
|
|
31
|
-
2018-10-1
|
|
32
|
-
|
|
33
|
-
2018-10-1
|
|
34
|
-
|
|
35
|
-
2018-10-1
|
|
36
|
-
|
|
37
|
-
2018-10-1
|
|
38
|
-
|
|
39
|
-
2018-10-1
|
|
40
|
-
|
|
41
|
-
2018-10-1
|
|
42
|
-
|
|
43
|
-
2018-10-1
|
|
44
|
-
|
|
45
|
-
2018-10-1
|
|
46
|
-
|
|
47
|
-
2018-10-1
|
|
48
|
-
|
|
49
|
-
2018-10-11
|
|
15
|
+
/var/log/mysqld.log/mysqld.log でログを確認しましたが、特に原因になるようなものは見つからず。。。
|
|
16
|
+
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
2018-10-11T10:44:13.6NZ mysqld_safe Logging to '/var/log/mysqld.log'.
|
|
20
|
+
|
|
21
|
+
2018-10-11T10:44:13.6NZ mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
|
|
22
|
+
|
|
23
|
+
2018-10-11T10:44:13.355504Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
|
|
24
|
+
|
|
25
|
+
2018-10-11T10:44:13.356074Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
|
|
26
|
+
|
|
27
|
+
2018-10-11T10:44:13.356148Z 0 [Note] /usr/local/Cellar/mysql@5.7/5.7.23/bin/mysqld (mysqld 5.7.23) starting as process 9404 ...
|
|
28
|
+
|
|
29
|
+
2018-10-11T10:44:13.359806Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
|
|
30
|
+
|
|
31
|
+
2018-10-11T10:44:13.362055Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
|
32
|
+
|
|
33
|
+
2018-10-11T10:44:13.362144Z 0 [Note] InnoDB: Uses event mutexes
|
|
34
|
+
|
|
35
|
+
2018-10-11T10:44:13.362354Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
|
|
36
|
+
|
|
37
|
+
2018-10-11T10:44:13.362414Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
|
|
38
|
+
|
|
39
|
+
2018-10-11T10:44:13.362898Z 0 [Note] InnoDB: Number of pools: 1
|
|
40
|
+
|
|
41
|
+
2018-10-11T10:44:13.363033Z 0 [Note] InnoDB: Using CPU crc32 instructions
|
|
42
|
+
|
|
43
|
+
2018-10-11T10:44:13.365052Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
|
|
44
|
+
|
|
45
|
+
2018-10-11T10:44:13.383451Z 0 [Note] InnoDB: Completed initialization of buffer pool
|
|
46
|
+
|
|
47
|
+
2018-10-11T10:44:13.402392Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!
|
|
48
|
+
|
|
49
|
+
2018-10-11 19:44:13 0x7fff8f9f5340 InnoDB: Assertion failure in thread 140735602971456 in file ut0ut.cc line 942
|
|
50
|
+
|
|
51
|
+
InnoDB: We intentionally generate a memory trap.
|
|
52
|
+
|
|
53
|
+
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
|
|
54
|
+
|
|
55
|
+
InnoDB: If you get repeated assertion failures or crashes, even
|
|
56
|
+
|
|
57
|
+
InnoDB: immediately after the mysqld startup, there may be
|
|
58
|
+
|
|
59
|
+
InnoDB: corruption in the InnoDB tablespace. Please refer to
|
|
60
|
+
|
|
61
|
+
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
|
|
62
|
+
|
|
63
|
+
InnoDB: about forcing recovery.
|
|
64
|
+
|
|
65
|
+
10:44:13 UTC - mysqld got signal 6 ;
|
|
66
|
+
|
|
67
|
+
This could be because you hit a bug. It is also possible that this binary
|
|
68
|
+
|
|
69
|
+
or one of the libraries it was linked against is corrupt, improperly built,
|
|
70
|
+
|
|
71
|
+
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
72
|
+
|
|
73
|
+
Attempting to collect some information that could help diagnose the problem.
|
|
74
|
+
|
|
75
|
+
As this is a crash and something is definitely wrong, the information
|
|
76
|
+
|
|
77
|
+
collection process might fail.
|
|
78
|
+
|
|
79
|
+
|
|
80
|
+
|
|
81
|
+
key_buffer_size=8388608
|
|
82
|
+
|
|
83
|
+
read_buffer_size=131072
|
|
84
|
+
|
|
85
|
+
max_used_connections=0
|
|
86
|
+
|
|
87
|
+
max_threads=151
|
|
88
|
+
|
|
89
|
+
thread_count=0
|
|
90
|
+
|
|
91
|
+
connection_count=0
|
|
92
|
+
|
|
93
|
+
It is possible that mysqld could use up to
|
|
94
|
+
|
|
95
|
+
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68220 K bytes of memory
|
|
96
|
+
|
|
97
|
+
Hope that's ok; if not, decrease some variables in the equation.
|
|
98
|
+
|
|
99
|
+
|
|
100
|
+
|
|
101
|
+
Thread pointer: 0x0
|
|
102
|
+
|
|
103
|
+
Attempting backtrace. You can use the following information to find out
|
|
104
|
+
|
|
105
|
+
where mysqld died. If you see no messages after this, something went
|
|
106
|
+
|
|
107
|
+
terribly wrong...
|
|
108
|
+
|
|
109
|
+
stack_bottom = 0 thread_stack 0x40000
|
|
110
|
+
|
|
111
|
+
0 mysqld 0x00000001010e2d8e my_print_stacktrace + 58
|
|
112
|
+
|
|
113
|
+
1 mysqld 0x00000001010620b9 handle_fatal_signal + 700
|
|
114
|
+
|
|
115
|
+
2 libsystem_platform.dylib 0x00007fff56c32f5a _sigtramp + 26
|
|
116
|
+
|
|
117
|
+
3 mysqld 0x000000010192b32d _ZZL18innodb_show_statusP10handlertonP3THDPFbS2_PKcmS4_mS4_mEE13truncated_msg + 123453
|
|
118
|
+
|
|
119
|
+
4 libsystem_c.dylib 0x00007fff56a5d312 abort + 127
|
|
120
|
+
|
|
121
|
+
5 mysqld 0x00000001012d1019 _Z23ut_dbg_assertion_failedPKcS0_m + 161
|
|
122
|
+
|
|
123
|
+
6 mysqld 0x00000001012d3aea _ZN2ib5fatalD2Ev + 88
|
|
124
|
+
|
|
125
|
+
7 mysqld 0x00000001012d3b23 _ZN2ib5fatalD1Ev + 9
|
|
126
|
+
|
|
127
|
+
8 mysqld 0x000000010117bc6b _ZL18fil_node_open_fileP10fil_node_t + 2446
|
|
128
|
+
|
|
129
|
+
9 mysqld 0x00000001011853e7 _ZL23fil_node_prepare_for_ioP10fil_node_tP12fil_system_tP11fil_space_t + 191
|
|
130
|
+
|
|
131
|
+
10 mysqld 0x0000000101185acb _Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_ + 794
|
|
132
|
+
|
|
133
|
+
11 mysqld 0x000000010114c186 _ZL17buf_read_page_lowP7dberr_tbmmRK9page_id_tRK11page_size_tb + 384
|
|
134
|
+
|
|
135
|
+
12 mysqld 0x000000010114c2d6 _Z13buf_read_pageRK9page_id_tRK11page_size_t + 59
|
|
136
|
+
|
|
137
|
+
13 mysqld 0x00000001011381c8 _Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb + 953
|
|
138
|
+
|
|
139
|
+
14 mysqld 0x00000001012c0bf7 _Z31trx_rseg_get_n_undo_tablespacesPm + 262
|
|
140
|
+
|
|
141
|
+
15 mysqld 0x00000001012a487a _Z34innobase_start_or_create_for_mysqlv + 7007
|
|
142
|
+
|
|
143
|
+
16 mysqld 0x00000001011d5b7f _ZL13innobase_initPv + 3700
|
|
144
|
+
|
|
145
|
+
17 mysqld 0x0000000100b4836b _Z24ha_initialize_handlertonP13st_plugin_int + 79
|
|
146
|
+
|
|
147
|
+
18 mysqld 0x0000000100fb3503 _ZL17plugin_initializeP13st_plugin_int + 79
|
|
148
|
+
|
|
149
|
+
19 mysqld 0x0000000100fb300b _Z40plugin_register_builtin_and_init_core_sePiPPc + 653
|
|
150
|
+
|
|
151
|
+
20 mysqld 0x0000000101057b36 _Z11mysqld_mainiPPc + 2929
|
|
152
|
+
|
|
153
|
+
21 libdyld.dylib 0x00007fff569b1115 start + 1
|
|
154
|
+
|
|
155
|
+
22 ??? 0x0000000000000007 0x0 + 7
|
|
156
|
+
|
|
157
|
+
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
|
158
|
+
|
|
159
|
+
information that should help you find out what is causing the crash.
|
|
160
|
+
|
|
161
|
+
2018-10-11T10:44:13.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/mac名 ended
|
|
162
|
+
|
|
163
|
+
|
|
50
164
|
|
|
51
165
|
```
|
|
52
166
|
|
|
@@ -68,6 +182,12 @@
|
|
|
68
182
|
|
|
69
183
|
socket = /tmp/mysql.sock
|
|
70
184
|
|
|
185
|
+
|
|
186
|
+
|
|
187
|
+
# エラーログ
|
|
188
|
+
|
|
189
|
+
log-error=/var/log/mysqld.log
|
|
190
|
+
|
|
71
191
|
```
|
|
72
192
|
|
|
73
193
|
|