質問編集履歴
2
ログの変更
title
CHANGED
|
File without changes
|
body
CHANGED
|
@@ -118,21 +118,82 @@
|
|
|
118
118
|
ログを見ることができました。
|
|
119
119
|
よくわかっていないのですが、貼り付けておきます。
|
|
120
120
|
```
|
|
121
|
-
|
|
121
|
+
￥2020-04-30T16:06:02.6NZ mysqld_safe Logging to '/var/log/mysqld.log'.
|
|
122
|
+
2020-04-30T16:06:02.6NZ mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
|
|
123
|
+
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).
|
|
124
|
+
2020-04-30T16:06:03.365590Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
|
|
125
|
+
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 ...
|
|
126
|
+
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
|
|
127
|
+
2020-04-30T16:06:03.391224Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
|
128
|
+
2020-04-30T16:06:03.391274Z 0 [Note] InnoDB: Uses event mutexes
|
|
129
|
+
2020-04-30T16:06:03.391288Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
|
|
130
|
+
2020-04-30T16:06:03.391300Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
|
|
131
|
+
2020-04-30T16:06:03.392806Z 0 [Note] InnoDB: Number of pools: 1
|
|
132
|
+
2020-04-30T16:06:03.395250Z 0 [Note] InnoDB: Using CPU crc32 instructions
|
|
133
|
+
2020-04-30T16:06:03.397396Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
|
|
134
|
+
2020-04-30T16:06:03.415071Z 0 [Note] InnoDB: Completed initialization of buffer pool
|
|
135
|
+
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!
|
|
136
|
+
2020-05-01 01:06:03 0x11a5235c0 InnoDB: Assertion failure in thread 4736562624 in file ut0ut.cc line 918
|
|
137
|
+
InnoDB: We intentionally generate a memory trap.
|
|
138
|
+
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
|
|
139
|
+
InnoDB: If you get repeated assertion failures or crashes, even
|
|
140
|
+
InnoDB: immediately after the mysqld startup, there may be
|
|
141
|
+
InnoDB: corruption in the InnoDB tablespace. Please refer to
|
|
142
|
+
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
|
|
143
|
+
InnoDB: about forcing recovery.
|
|
144
|
+
16:06:03 UTC - mysqld got signal 6 ;
|
|
145
|
+
This could be because you hit a bug. It is also possible that this binary
|
|
146
|
+
or one of the libraries it was linked against is corrupt, improperly built,
|
|
147
|
+
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
148
|
+
Attempting to collect some information that could help diagnose the problem.
|
|
149
|
+
As this is a crash and something is definitely wrong, the information
|
|
150
|
+
collection process might fail.
|
|
122
151
|
|
|
152
|
+
key_buffer_size=8388608
|
|
153
|
+
read_buffer_size=131072
|
|
154
|
+
max_used_connections=0
|
|
155
|
+
max_threads=151
|
|
156
|
+
|
|
157
|
+
|
|
158
|
+
thread_count=0
|
|
159
|
+
connection_count=0
|
|
160
|
+
It is possible that mysqld could use up to
|
|
161
|
+
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68221 K bytes of memory
|
|
162
|
+
Hope that's ok; if not, decrease some variables in the equation.
|
|
163
|
+
|
|
164
|
+
Thread pointer: 0x0
|
|
165
|
+
Attempting backtrace. You can use the following information to find out
|
|
166
|
+
where mysqld died. If you see no messages after this, something went
|
|
167
|
+
terribly wrong...
|
|
168
|
+
stack_bottom = 0 thread_stack 0x40000
|
|
169
|
+
0 mysqld 0x000000010b9e5139 my_print_stacktrace + 58
|
|
170
|
+
1 mysqld 0x000000010b964d1b handle_fatal_signal + 696
|
|
171
|
+
2 libsystem_platform.dylib 0x00007fff7b8bfb5d _sigtramp + 29
|
|
172
|
+
3 ??? 0x0000000000000000 0x0 + 0
|
|
173
|
+
4 libsystem_c.dylib 0x00007fff7b7796a6 abort + 127
|
|
174
|
+
5 mysqld 0x000000010bc91f88 _Z23ut_dbg_assertion_failedPKcS0_m + 161
|
|
175
|
+
6 mysqld 0x000000010bbd5947 _ZN2ib5fatalD2Ev + 91
|
|
176
|
+
7 mysqld 0x000000010bbd5985 _ZN2ib5fatalD1Ev + 9
|
|
177
|
+
8 mysqld 0x000000010ba7d55a _ZL18fil_node_open_fileP10fil_node_t + 2411
|
|
178
|
+
9 mysqld 0x000000010ba86e6e _ZL23fil_node_prepare_for_ioP10fil_node_tP12fil_system_tP11fil_space_t + 191
|
|
179
|
+
10 mysqld 0x000000010ba87556 _Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_ + 796
|
|
180
|
+
11 mysqld 0x000000010ba4e28c _ZL17buf_read_page_lowP7dberr_tbmmRK9page_id_tRK11page_size_tb + 408
|
|
123
|
-
12
|
|
181
|
+
12 mysqld 0x000000010ba4e3e3 _Z13buf_read_pageRK9page_id_tRK11page_size_t + 56
|
|
124
|
-
13
|
|
182
|
+
13 mysqld 0x000000010ba39cf7 _Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb + 953
|
|
125
|
-
14
|
|
183
|
+
14 mysqld 0x000000010bbc34fa _Z31trx_rseg_get_n_undo_tablespacesPm + 251
|
|
126
|
-
15
|
|
184
|
+
15 mysqld 0x000000010bba6f4b _Z34innobase_start_or_create_for_mysqlv + 6608
|
|
127
|
-
16
|
|
185
|
+
16 mysqld 0x000000010bad6a25 _ZL13innobase_initPv + 3636
|
|
128
|
-
17
|
|
186
|
+
17 mysqld 0x000000010b458508 _Z24ha_initialize_handlertonP13st_plugin_int + 78
|
|
129
|
-
18
|
|
187
|
+
18 mysqld 0x000000010b8b41fd _ZL17plugin_initializeP13st_plugin_int + 79
|
|
130
|
-
19
|
|
188
|
+
19 mysqld 0x000000010b8b3cfb _Z40plugin_register_builtin_and_init_core_sePiPPc + 707
|
|
131
|
-
20
|
|
189
|
+
20 mysqld 0x000000010b959cfd _Z11mysqld_mainiPPc + 2912
|
|
132
|
-
21
|
|
190
|
+
21 libdyld.dylib 0x00007fff7b6d43d5 start + 1
|
|
133
191
|
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
|
134
192
|
information that should help you find out what is causing the crash.
|
|
135
|
-
2020-04-30T16:06:03.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/
|
|
193
|
+
2020-04-30T16:06:03.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/XXXXXX.local.pid ended
|
|
194
|
+
|
|
195
|
+
|
|
196
|
+
|
|
136
197
|
```
|
|
137
198
|
|
|
138
199
|
何がどうなっているのか
|
1
ログの箇所を追加
title
CHANGED
|
File without changes
|
body
CHANGED
|
@@ -111,6 +111,30 @@
|
|
|
111
111
|
|
|
112
112
|
|
|
113
113
|
|
|
114
|
+
|
|
115
|
+
|
|
116
|
+
追記
|
|
117
|
+
|
|
118
|
+
ログを見ることができました。
|
|
119
|
+
よくわかっていないのですが、貼り付けておきます。
|
|
120
|
+
```
|
|
121
|
+
$ vi /var/log/mysqld.log
|
|
122
|
+
|
|
123
|
+
12 mysqld 0x000000010ba4e3e3 _Z13buf_read_pageRK9page_id_tRK11page_size_t + 56
|
|
124
|
+
13 mysqld 0x000000010ba39cf7 _Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb + 953
|
|
125
|
+
14 mysqld 0x000000010bbc34fa _Z31trx_rseg_get_n_undo_tablespacesPm + 251
|
|
126
|
+
15 mysqld 0x000000010bba6f4b _Z34innobase_start_or_create_for_mysqlv + 6608
|
|
127
|
+
16 mysqld 0x000000010bad6a25 _ZL13innobase_initPv + 3636
|
|
128
|
+
17 mysqld 0x000000010b458508 _Z24ha_initialize_handlertonP13st_plugin_int + 78
|
|
129
|
+
18 mysqld 0x000000010b8b41fd _ZL17plugin_initializeP13st_plugin_int + 79
|
|
130
|
+
19 mysqld 0x000000010b8b3cfb _Z40plugin_register_builtin_and_init_core_sePiPPc + 707
|
|
131
|
+
20 mysqld 0x000000010b959cfd _Z11mysqld_mainiPPc + 2912
|
|
132
|
+
21 libdyld.dylib 0x00007fff7b6d43d5 start + 1
|
|
133
|
+
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
|
134
|
+
information that should help you find out what is causing the crash.
|
|
135
|
+
2020-04-30T16:06:03.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/XXXXX.pid ended
|
|
136
|
+
```
|
|
137
|
+
|
|
114
138
|
何がどうなっているのか
|
|
115
139
|
さっぱり分からなくなってきてしまいまい途方に暮れています。
|
|
116
140
|
何かしらヒントをいただけると大変助かります。
|