teratail
回答率
85.31%
teratail header banner
teratail header banner
質問するログイン新規登録
トップに関する質問era-rogu tuikaMySQLが起動しません。

編集履歴

質問編集履歴

6

文法の修正

2017/07/08 03:17

投稿

scrollman
scrollman

スコア83

test CHANGED
File without changes
test CHANGED
@@ -90,7 +90,11 @@
90
90
 
91
91
  lines 1-13/13 (END)
92
92
 
93
+ ```
93
94
 
95
+
96
+
97
+ ```mysql
94
98
 
95
99
  InnoDB: Progress in percent: 2017-07-07T22:36:22.397197Z 0 [ERROR] InnoDB: Trying to access page number 278272 in space 145, space name coreprotect/wgc_block, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
96
100
 
@@ -156,6 +160,4 @@
156
160
 
157
161
  2017-07-07T22:36:52.903807Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
158
162
 
159
-
160
-
161
163
  ```

5

era-rogutuika

2017/07/08 03:17

投稿

scrollman
scrollman

スコア83

test CHANGED
@@ -1 +1 @@
1
- MySQLが起動しません。
1
+ era-rogu tuikaMySQLが起動しません。
test CHANGED
@@ -90,4 +90,72 @@
90
90
 
91
91
  lines 1-13/13 (END)
92
92
 
93
+
94
+
95
+ InnoDB: Progress in percent: 2017-07-07T22:36:22.397197Z 0 [ERROR] InnoDB: Trying to access page number 278272 in space 145, space name coreprotect/wgc_block, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
96
+
97
+ 2017-07-07T22:36:22.397210Z 0 [ERROR] InnoDB: Server exits.
98
+
99
+ 2017-07-07T22:36:52.597292Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
100
+
101
+ 2017-07-07T22:36:52.597384Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
102
+
103
+ 2017-07-07T22:36:52.798351Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
104
+
105
+ 2017-07-07T22:36:52.801916Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.18-0ubuntu0.16.04.1) starting as process 7733 ...
106
+
107
+ 2017-07-07T22:36:52.808342Z 0 [Note] InnoDB: PUNCH HOLE support available
108
+
109
+ 2017-07-07T22:36:52.808408Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
110
+
111
+ 2017-07-07T22:36:52.808420Z 0 [Note] InnoDB: Uses event mutexes
112
+
113
+ 2017-07-07T22:36:52.808432Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
114
+
115
+ 2017-07-07T22:36:52.808443Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
116
+
117
+ 2017-07-07T22:36:52.808454Z 0 [Note] InnoDB: Using Linux native AIO
118
+
119
+ 2017-07-07T22:36:52.808874Z 0 [Note] InnoDB: Number of pools: 1
120
+
121
+ 2017-07-07T22:36:52.809016Z 0 [Note] InnoDB: Not using CPU crc32 instructions
122
+
123
+ 2017-07-07T22:36:52.811104Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
124
+
125
+ 2017-07-07T22:36:52.827113Z 0 [Note] InnoDB: Completed initialization of buffer pool
126
+
127
+ 2017-07-07T22:36:52.829523Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
128
+
129
+ 2017-07-07T22:36:52.843674Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
130
+
131
+ 2017-07-07T22:36:52.845334Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 22488436582
132
+
133
+ 2017-07-07T22:36:52.845444Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 22488445105
134
+
135
+ 2017-07-07T22:36:52.846946Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 22488445105
136
+
137
+ 2017-07-07T22:36:52.848503Z 0 [Note] InnoDB: Database was not shutdown normally!
138
+
139
+ 2017-07-07T22:36:52.848555Z 0 [Note] InnoDB: Starting crash recovery.
140
+
141
+ 2017-07-07T22:36:52.848836Z 0 [Warning] InnoDB: Page 4 in the doublewrite buffer is not within space bounds: page [page id: space=145, page number=183176]
142
+
143
+ 2017-07-07T22:36:52.848853Z 0 [Warning] InnoDB: Page 5 in the doublewrite buffer is not within space bounds: page [page id: space=145, page number=254575]
144
+
145
+ 2017-07-07T22:36:52.848866Z 0 [Warning] InnoDB: Page 6 in the doublewrite buffer is not within space bounds: page [page id: space=145, page number=231687]
146
+
147
+ 2017-07-07T22:36:52.849812Z 0 [Warning] InnoDB: Page 34 in the doublewrite buffer is not within space bounds: page [page id: space=145, page number=196927]
148
+
149
+ 2017-07-07T22:36:52.849848Z 0 [Warning] InnoDB: Page 35 in the doublewrite buffer is not within space bounds: page [page id: space=145, page number=214280]
150
+
151
+ 2017-07-07T22:36:52.849860Z 0 [Warning] InnoDB: Page 36 in the doublewrite buffer is not within space bounds: page [page id: space=145, page number=233064]
152
+
153
+ 2017-07-07T22:36:52.903722Z 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 34 row operations to undo
154
+
155
+ 2017-07-07T22:36:52.903773Z 0 [Note] InnoDB: Trx id counter is 3117056
156
+
157
+ 2017-07-07T22:36:52.903807Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
158
+
159
+
160
+
93
161
  ```

4

エラーの追加

2017/07/08 03:16

投稿

scrollman
scrollman

スコア83

test CHANGED
File without changes
test CHANGED
@@ -18,7 +18,11 @@
18
18
 
19
19
 
20
20
 
21
+ ```mysql
22
+
21
23
  mysql.serviceJob for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.
24
+
25
+ ```
22
26
 
23
27
 
24
28
 
@@ -46,9 +50,15 @@
46
50
 
47
51
  と書いてありました。
48
52
 
53
+ 見てみたところ、mysql.sockもpidも生成されていないんです。←これは間違いでした。/var/lib/mysqlにちゃんとありました。→mysql.sockを消去。改めて./mysql start をするも同じエラーが発生
54
+
55
+
56
+
49
- 見てみたところ、mysql.sockもpidも生成されていないんです。
57
+ systemctl status mysql.service を実行していみる。
50
58
 
51
59
 
60
+
61
+ ```mysql
52
62
 
53
63
  /etc/init.d$ systemctl status mysql.service
54
64
 
@@ -79,3 +89,5 @@
79
89
  7月 08 11:31:43 DOG2 systemd[1]: mysql.service: Main process exited, code=exite
80
90
 
81
91
  lines 1-13/13 (END)
92
+
93
+ ```

3

era-notuika

2017/07/08 02:37

投稿

scrollman
scrollman

スコア83

test CHANGED
File without changes
test CHANGED
@@ -47,3 +47,35 @@
47
47
  と書いてありました。
48
48
 
49
49
  見てみたところ、mysql.sockもpidも生成されていないんです。
50
+
51
+
52
+
53
+ /etc/init.d$ systemctl status mysql.service
54
+
55
+ ● mysql.service - MySQL Community Server
56
+
57
+ Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: en
58
+
59
+ Active: activating (start-post) (Result: exit-code) since 土 2017-07-08 11:31
60
+
61
+ Process: 21779 ExecStart=/usr/sbin/mysqld (code=exited, status=1/FAILURE)
62
+
63
+ Process: 21771 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exi
64
+
65
+ Main PID: 21779 (code=exited, status=1/FAILURE); : 21780 (mysql-systemd
66
+
67
+ CGroup: /system.slice/mysql.service
68
+
69
+ └─control
70
+
71
+ ├─21780 /bin/bash /usr/share/mysql/mysql-systemd-start post
72
+
73
+ └─21880 sleep 1
74
+
75
+
76
+
77
+ 7月 08 11:31:43 DOG2 systemd[1]: Starting MySQL Community Server...
78
+
79
+ 7月 08 11:31:43 DOG2 systemd[1]: mysql.service: Main process exited, code=exite
80
+
81
+ lines 1-13/13 (END)

2

文法の修正

2017/07/08 02:34

投稿

scrollman
scrollman

スコア83

test CHANGED
File without changes
test CHANGED
@@ -34,12 +34,16 @@
34
34
 
35
35
  そこの回答には
36
36
 
37
+
38
+
37
39
  > >1.解消方法教えてくださいm(__)m
38
40
 
39
41
  > mysql.sockは自動で作成されるのでこちらを削除してください。
40
42
 
41
43
  > *pidファイルも作られてたら削除してください。
42
44
 
45
+
46
+
43
47
  と書いてありました。
44
48
 
45
49
  見てみたところ、mysql.sockもpidも生成されていないんです。

1

やってみた事の追加

2017/07/08 02:22

投稿

scrollman
scrollman

スコア83

test CHANGED
File without changes
test CHANGED
@@ -25,3 +25,21 @@
25
25
  OS:Linux Mint 32bit
26
26
 
27
27
  MySQL: mysql-server 5.7.18-0ubuntu0.16.04.1
28
+
29
+
30
+
31
+ やってみた事
32
+
33
+ テラテイルの過去の質問に同じトラブルがあり
34
+
35
+ そこの回答には
36
+
37
+ > >1.解消方法教えてくださいm(__)m
38
+
39
+ > mysql.sockは自動で作成されるのでこちらを削除してください。
40
+
41
+ > *pidファイルも作られてたら削除してください。
42
+
43
+ と書いてありました。
44
+
45
+ 見てみたところ、mysql.sockもpidも生成されていないんです。