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

編集履歴

質問編集履歴

6

文法の修正

2017/07/08 03:17

投稿

scrollman
scrollman

スコア83

title CHANGED
File without changes
body CHANGED
@@ -44,7 +44,9 @@
44
44
  7月 08 11:31:43 DOG2 systemd[1]: Starting MySQL Community Server...
45
45
  7月 08 11:31:43 DOG2 systemd[1]: mysql.service: Main process exited, code=exite
46
46
  lines 1-13/13 (END)
47
+ ```
47
48
 
49
+ ```mysql
48
50
  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.
49
51
  2017-07-07T22:36:22.397210Z 0 [ERROR] InnoDB: Server exits.
50
52
  2017-07-07T22:36:52.597292Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
@@ -77,5 +79,4 @@
77
79
  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
78
80
  2017-07-07T22:36:52.903773Z 0 [Note] InnoDB: Trx id counter is 3117056
79
81
  2017-07-07T22:36:52.903807Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
80
-
81
82
  ```

5

era-rogutuika

2017/07/08 03:17

投稿

scrollman
scrollman

スコア83

title CHANGED
@@ -1,1 +1,1 @@
1
- MySQLが起動しません。
1
+ era-rogu tuikaMySQLが起動しません。
body CHANGED
@@ -44,4 +44,38 @@
44
44
  7月 08 11:31:43 DOG2 systemd[1]: Starting MySQL Community Server...
45
45
  7月 08 11:31:43 DOG2 systemd[1]: mysql.service: Main process exited, code=exite
46
46
  lines 1-13/13 (END)
47
+
48
+ 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.
49
+ 2017-07-07T22:36:22.397210Z 0 [ERROR] InnoDB: Server exits.
50
+ 2017-07-07T22:36:52.597292Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
51
+ 2017-07-07T22:36:52.597384Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
52
+ 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).
53
+ 2017-07-07T22:36:52.801916Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.18-0ubuntu0.16.04.1) starting as process 7733 ...
54
+ 2017-07-07T22:36:52.808342Z 0 [Note] InnoDB: PUNCH HOLE support available
55
+ 2017-07-07T22:36:52.808408Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
56
+ 2017-07-07T22:36:52.808420Z 0 [Note] InnoDB: Uses event mutexes
57
+ 2017-07-07T22:36:52.808432Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
58
+ 2017-07-07T22:36:52.808443Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
59
+ 2017-07-07T22:36:52.808454Z 0 [Note] InnoDB: Using Linux native AIO
60
+ 2017-07-07T22:36:52.808874Z 0 [Note] InnoDB: Number of pools: 1
61
+ 2017-07-07T22:36:52.809016Z 0 [Note] InnoDB: Not using CPU crc32 instructions
62
+ 2017-07-07T22:36:52.811104Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
63
+ 2017-07-07T22:36:52.827113Z 0 [Note] InnoDB: Completed initialization of buffer pool
64
+ 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().
65
+ 2017-07-07T22:36:52.843674Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
66
+ 2017-07-07T22:36:52.845334Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 22488436582
67
+ 2017-07-07T22:36:52.845444Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 22488445105
68
+ 2017-07-07T22:36:52.846946Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 22488445105
69
+ 2017-07-07T22:36:52.848503Z 0 [Note] InnoDB: Database was not shutdown normally!
70
+ 2017-07-07T22:36:52.848555Z 0 [Note] InnoDB: Starting crash recovery.
71
+ 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]
72
+ 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]
73
+ 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]
74
+ 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]
75
+ 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]
76
+ 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]
77
+ 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
78
+ 2017-07-07T22:36:52.903773Z 0 [Note] InnoDB: Trx id counter is 3117056
79
+ 2017-07-07T22:36:52.903807Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
80
+
47
81
  ```

4

エラーの追加

2017/07/08 03:16

投稿

scrollman
scrollman

スコア83

title CHANGED
File without changes
body CHANGED
@@ -8,7 +8,9 @@
8
8
 
9
9
  なんででしょうか、、、
10
10
 
11
+ ```mysql
11
12
  mysql.serviceJob for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.
13
+ ```
12
14
 
13
15
  OS:Linux Mint 32bit
14
16
  MySQL: mysql-server 5.7.18-0ubuntu0.16.04.1
@@ -22,8 +24,11 @@
22
24
  > *pidファイルも作られてたら削除してください。
23
25
 
24
26
  と書いてありました。
27
+ 見てみたところ、mysql.sockもpidも生成されていないんです。←これは間違いでした。/var/lib/mysqlにちゃんとありました。→mysql.sockを消去。改めて./mysql start をするも同じエラーが発生
28
+
25
- 見てみたところ、mysql.sockもpidも生成されていないんです。
29
+ systemctl status mysql.service を実行していみる。
26
30
 
31
+ ```mysql
27
32
  /etc/init.d$ systemctl status mysql.service
28
33
  ● mysql.service - MySQL Community Server
29
34
  Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: en
@@ -38,4 +43,5 @@
38
43
 
39
44
  7月 08 11:31:43 DOG2 systemd[1]: Starting MySQL Community Server...
40
45
  7月 08 11:31:43 DOG2 systemd[1]: mysql.service: Main process exited, code=exite
41
- lines 1-13/13 (END)
46
+ lines 1-13/13 (END)
47
+ ```

3

era-notuika

2017/07/08 02:37

投稿

scrollman
scrollman

スコア83

title CHANGED
File without changes
body CHANGED
@@ -22,4 +22,20 @@
22
22
  > *pidファイルも作られてたら削除してください。
23
23
 
24
24
  と書いてありました。
25
- 見てみたところ、mysql.sockもpidも生成されていないんです。
25
+ 見てみたところ、mysql.sockもpidも生成されていないんです。
26
+
27
+ /etc/init.d$ systemctl status mysql.service
28
+ ● mysql.service - MySQL Community Server
29
+ Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: en
30
+ Active: activating (start-post) (Result: exit-code) since 土 2017-07-08 11:31
31
+ Process: 21779 ExecStart=/usr/sbin/mysqld (code=exited, status=1/FAILURE)
32
+ Process: 21771 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exi
33
+ Main PID: 21779 (code=exited, status=1/FAILURE); : 21780 (mysql-systemd
34
+ CGroup: /system.slice/mysql.service
35
+ └─control
36
+ ├─21780 /bin/bash /usr/share/mysql/mysql-systemd-start post
37
+ └─21880 sleep 1
38
+
39
+ 7月 08 11:31:43 DOG2 systemd[1]: Starting MySQL Community Server...
40
+ 7月 08 11:31:43 DOG2 systemd[1]: mysql.service: Main process exited, code=exite
41
+ lines 1-13/13 (END)

2

文法の修正

2017/07/08 02:34

投稿

scrollman
scrollman

スコア83

title CHANGED
File without changes
body CHANGED
@@ -16,8 +16,10 @@
16
16
  やってみた事
17
17
  テラテイルの過去の質問に同じトラブルがあり
18
18
  そこの回答には
19
+
19
20
  > >1.解消方法教えてくださいm(__)m
20
21
  > mysql.sockは自動で作成されるのでこちらを削除してください。
21
22
  > *pidファイルも作られてたら削除してください。
23
+
22
24
  と書いてありました。
23
25
  見てみたところ、mysql.sockもpidも生成されていないんです。

1

やってみた事の追加

2017/07/08 02:22

投稿

scrollman
scrollman

スコア83

title CHANGED
File without changes
body CHANGED
@@ -11,4 +11,13 @@
11
11
  mysql.serviceJob for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.
12
12
 
13
13
  OS:Linux Mint 32bit
14
- MySQL: mysql-server 5.7.18-0ubuntu0.16.04.1
14
+ MySQL: mysql-server 5.7.18-0ubuntu0.16.04.1
15
+
16
+ やってみた事
17
+ テラテイルの過去の質問に同じトラブルがあり
18
+ そこの回答には
19
+ > >1.解消方法教えてくださいm(__)m
20
+ > mysql.sockは自動で作成されるのでこちらを削除してください。
21
+ > *pidファイルも作られてたら削除してください。
22
+ と書いてありました。
23
+ 見てみたところ、mysql.sockもpidも生成されていないんです。