teratail
回答率
85.30%
teratail header banner
teratail header banner
質問するログイン新規登録
トップに関する質問AWSでのVIP設定をpacemakerとcorosyncにて実施可能かどうか

編集履歴

質問編集履歴

10

修正

2021/06/06 21:43

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -185,7 +185,7 @@
185
185
  * eip (ocf::heartbeat:eip): Stopped
186
186
 
187
187
  Failed Resource Actions:
188
- * eip_start_0 on ip-10-10-10-2.ap-northeast-1.compute.internal 'error' (1): call=6, status='complete', exitreason='', last-rc-change='2021-06-07 03:10:06 +09:00', queued=0ms, exec=14ms
188
+ * eip_start_0 on ip-10-10-10-2.ap-northeast-1.compute.internal 'error' (1): call=244, status='complete', exitreason='', last-rc-change='2021-06-07 03:10:06 +09:00', queued=0ms, exec=14ms
189
189
 
190
190
  Daemon Status:
191
191
  corosync: active/enabled

9

修正

2021/06/06 21:43

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -185,7 +185,7 @@
185
185
  * eip (ocf::heartbeat:eip): Stopped
186
186
 
187
187
  Failed Resource Actions:
188
- * eip_start_0 on ip-10-10-10-1.ap-northeast-1.compute.internal 'error' (1): call=6, status='complete', exitreason='', last-rc-change='2021-06-07 03:10:06 +09:00', queued=0ms, exec=14ms
188
+ * eip_start_0 on ip-10-10-10-2.ap-northeast-1.compute.internal 'error' (1): call=6, status='complete', exitreason='', last-rc-change='2021-06-07 03:10:06 +09:00', queued=0ms, exec=14ms
189
189
 
190
190
  Daemon Status:
191
191
  corosync: active/enabled

8

修正

2021/06/06 21:42

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -174,7 +174,7 @@
174
174
  * Stack: corosync
175
175
  * Current DC: ip-10-10-10-1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition with quorum
176
176
  * Last updated: Mon Jun 7 03:39:48 2021
177
- * Last change: Mon Jun 7 03:23:05 2021 by root via cibadmin on ip-10-0-0-2.ap-northeast-1.compute.internal
177
+ * Last change: Mon Jun 7 03:23:05 2021 by root via cibadmin on ip-10-10-10-2.ap-northeast-1.compute.internal
178
178
  * 2 nodes configured
179
179
  * 1 resource instance configured
180
180
 

7

修正

2021/06/06 19:16

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -168,7 +168,7 @@
168
168
  timestamp: on
169
169
  }
170
170
 
171
- #Online後のpcs status
171
+ #Online後のpcs status [server01]
172
172
  Cluster name: aws-cluster
173
173
  Cluster Summary:
174
174
  * Stack: corosync

6

追記

2021/06/06 19:15

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -166,4 +166,28 @@
166
166
  to_logfile: yes
167
167
  logfile: /var/log/cluster/corosync.log
168
168
  timestamp: on
169
- }
169
+ }
170
+
171
+ #Online後のpcs status
172
+ Cluster name: aws-cluster
173
+ Cluster Summary:
174
+ * Stack: corosync
175
+ * Current DC: ip-10-10-10-1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition with quorum
176
+ * Last updated: Mon Jun 7 03:39:48 2021
177
+ * Last change: Mon Jun 7 03:23:05 2021 by root via cibadmin on ip-10-0-0-2.ap-northeast-1.compute.internal
178
+ * 2 nodes configured
179
+ * 1 resource instance configured
180
+
181
+ Node List:
182
+ * Online: [ ip-10-10-10-1.ap-northeast-1.compute.internal ip-10-10-10-2.ap-northeast-1.compute.internal ]
183
+
184
+ Full List of Resources:
185
+ * eip (ocf::heartbeat:eip): Stopped
186
+
187
+ Failed Resource Actions:
188
+ * eip_start_0 on ip-10-10-10-1.ap-northeast-1.compute.internal 'error' (1): call=6, status='complete', exitreason='', last-rc-change='2021-06-07 03:10:06 +09:00', queued=0ms, exec=14ms
189
+
190
+ Daemon Status:
191
+ corosync: active/enabled
192
+ pacemaker: active/enabled
193
+ pcsd: active/enabled

5

修正

2021/06/06 19:14

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -140,9 +140,7 @@
140
140
  # corosync.conf
141
141
  totem {
142
142
  version: 2
143
- transport:knet←ここをudpu、udpに変更したがサービス再起動でエラー
143
+ transport:udpu
144
- 　　crypto_cipher: aes256
145
- crypto_hash: sha256
146
144
  }
147
145
 
148
146
  nodelist {

4

追記

2021/06/04 12:52

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -135,4 +135,37 @@
135
135
  Daemon Status:
136
136
  corosync: active/disabled
137
137
  pacemaker: active/disabled
138
- pcsd: active/enabled
138
+ pcsd: active/enabled
139
+
140
+ # corosync.conf
141
+ totem {
142
+ version: 2
143
+ transport:knet←ここをudpu、udpに変更したがサービス再起動でエラー
144
+ 　　crypto_cipher: aes256
145
+ crypto_hash: sha256
146
+ }
147
+
148
+ nodelist {
149
+ node {
150
+ 　　　　 ring0_addr: 10.10.10.1
151
+ 　　　　 name: ip-10-10-10-1.ap-northeast-1.compute.internal
152
+ 　　　　 nodeid: 1
153
+ }
154
+
155
+ node {
156
+ 　　　　 ring0_addr: 10.10.10.2
157
+ 　　　　 name: ip-10-10-10-2.ap-northeast-1.compute.internal
158
+ 　　　　 nodeid: 2
159
+ }
160
+ }
161
+
162
+ quorum {
163
+ provider: corosync_votequorum
164
+ two_node: 2
165
+ }
166
+
167
+ logging {
168
+ to_logfile: yes
169
+ logfile: /var/log/cluster/corosync.log
170
+ timestamp: on
171
+ }

3

修正

2021/06/04 12:35

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -12,23 +12,31 @@
12
12
  AWSの設定は上記URLの内容とほとんど変更なし
13
13
  ### 発生している問題・エラーメッセージ
14
14
 
15
- #pcs status node
15
+ #pcs status node[server01]
16
16
  Pacemaker Nodes:
17
- Online:ip-×-×-×-×.ap-northeast-1.compute.internal←操作しているサーバ
17
+ Online:ip-10-10-10-1.ap-northeast-1.compute.internal
18
18
  Standby:
19
19
  Standby with resource(s) running:
20
20
  Maintenance:
21
- Offline:ip-×-×-×-×.ap-northeast-1.compute.internal←F/O先のサーバ
21
+ Offline:ip-10-10-10-2.ap-northeast-1.compute.internal
22
22
 
23
+ #pcs status node[server02]
24
+ Pacemaker Nodes:
25
+ Online:ip-10-10-10-2.ap-northeast-1.compute.internal
26
+ Standby:
27
+ Standby with resource(s) running:
28
+ Maintenance:
29
+ Offline:ip-10-10-10-1.ap-northeast-1.compute.internal
30
+
23
31
  #pcs config[server01]
24
32
  Cluster Name: aws-cluster
25
33
  Corosync Nodes:
26
- ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
34
+ ip-10-10-10-1.ap-northeast-1.compute.internal ip-10-10-10-2.ap-northeast-1.compute.internal
27
35
  Pacemaker Nodes:
28
- ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
36
+ ip-10-10-10-1.ap-northeast-1.compute.internal ip-10-10-10-2.ap-northeast-1.compute.internal
29
37
  Resources:
30
38
  Resource: eip (class=ocf provider=heartbeat type=eip)
31
- Attributes: elastic_ip=×.×.×.×
39
+ Attributes: elastic_ip=1.1.1.1←例
32
40
  Operations: start interval=0s timeout=60s on-fail=stop (eip-start-interval-0s)
33
41
  monitor interval=10s timeout=60s on-fail=restart (eip-monitor-interval-10s)
34
42
  stop interval=0s timeout=60s on-fail=block (eip-stop-interval-0s)
@@ -57,9 +65,9 @@
57
65
  #pcs config[server02]
58
66
  Cluster Name: aws-cluster
59
67
  Corosync Nodes:
60
- ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
68
+ ip-10-10-10-2.ap-northeast-1.compute.internal ip-10-10-10-1.ap-northeast-1.compute.internal
61
69
  Pacemaker Nodes:
62
- ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
70
+ ip-10-10-10-2.ap-northeast-1.compute.internal ip-10-10-10-1.ap-northeast-1.compute.internal
63
71
  Resources:
64
72
  Stonith Devices:
65
73
  Fencing Levels:
@@ -83,29 +91,24 @@
83
91
  Quorum:
84
92
  Options:
85
93
 
86
- #crm_mon -f1（Node Listのみ記載します）
87
- Nodo List:
88
- ＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal:UNCLEAN(offline)←F/O先のサーバ
89
- ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]←操作しているサーバ
90
-
91
94
  #pcs status[server01]
92
95
  Cluster name: aws-cluster
93
96
  Cluster Summary:
94
97
  ＊ Stack: corosync
95
- ＊ Current DC: ip-×-×-×-×.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
98
+ ＊ Current DC: ip-10-10-10-1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
96
99
  ＊Last updated: Fri Jun 4 14:20:06 2021
97
- ＊ Last change: Fri Jun 4 09:46:23 2021 by root via cibadmin on ip-×-×-×-×.ap-northeast-1.compute.internal
100
+ ＊ Last change: Fri Jun 4 09:46:23 2021 by root via cibadmin on ip-10-10-10-1.ap-northeast-1.compute.internal
98
101
  ＊2 nodes configured
99
102
  ＊1 resource instance configured
100
103
  Node List:
101
- ＊Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
104
+ ＊Online: [ ip-10-10-10-1.ap-northeast-1.compute.internal ]
102
- ＊OFFLINE: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
105
+ ＊OFFLINE: [ ip-10-10-10-2.ap-northeast-1.compute.internal ]
103
106
 
104
107
  Full List of Resources:
105
108
  ＊eip (ocf::heartbeat:eip): Stopped
106
109
  Failed Resource Actions:
107
110
 
108
- ＊eip_start_0 on ip-×-×-×-×.ap-northeast-1.compute.internal 'error' (1): call=6, status='complete', exitreason='', last-rc-change='2021-06-04 09:32:25 +09:00', queued=0ms, exec=12ms
111
+ ＊eip_start_0 on ip-10-10-10-1.ap-northeast-1.compute.internal 'error' (1): call=6, status='complete', exitreason='', last-rc-change='2021-06-04 09:32:25 +09:00', queued=0ms, exec=12ms
109
112
 
110
113
  Daemon Status:
111
114
  corosync: active/disabled
@@ -118,14 +121,14 @@
118
121
  No stonith devices and stonith-enabled is not false
119
122
  Cluster Summary:
120
123
  ＊ Stack: corosync
121
- ＊ Current DC: ip-×-×-×-×1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
124
+ ＊ Current DC: ip-10-10-10-2.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
122
125
  ＊ Last updated: Fri Jun 4 14:28:01 2021
123
- ＊ Last change: Fri Jun 4 09:29:47 2021 by hacluster via crmd on ip-×-×-×-×.ap-northeast-1.compute.internal
126
+ ＊ Last change: Fri Jun 4 09:29:47 2021 by hacluster via crmd on ip-10-10-10-2.ap-northeast-1.compute.internal
124
127
  ＊ 2 nodes configured
125
128
  ＊ 0 resource instances configured
126
129
  Node List:
127
- ＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal: UNCLEAN (offline)
130
+ ＊ Node ip-10-10-10-1.ap-northeast-1.compute.internal: UNCLEAN (offline)
128
- ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
131
+ ＊ Online: [ ip-10-10-10-2.ap-northeast-1.compute.internal ]
129
132
 
130
133
  Full List of Resources:
131
134
  ＊ No resources

2

追記

2021/06/04 06:26

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -1,5 +1,4 @@
1
1
  ### 前提・実現したいこと
2
-
3
2
  AWSを利用してMulti-AZのHA構成でサーバを構築しています。
4
3
  利用しているクラスターソフトはPacemekarとcorosyncです。
5
4
  VIPの設定を実施したところ上手く動作しません。
@@ -11,57 +10,126 @@
11
10
 
12
11
  OS：Red Hat Enterprise Linux 8 with High Availability
13
12
  AWSの設定は上記URLの内容とほとんど変更なし
13
+ ### 発生している問題・エラーメッセージ
14
14
 
15
- ### 発生している問題・エラーメッセージ
16
15
  #pcs status node
17
16
  Pacemaker Nodes:
18
- Online:ip-×-×-×-×.ap-northeast-1.compute.internal←操作しているサーバ
17
+ Online:ip-×-×-×-×.ap-northeast-1.compute.internal←操作しているサーバ
19
- Standby:
18
+ Standby:
20
- Standby with resource(s) running:
19
+ Standby with resource(s) running:
21
- Maintenance:
20
+ Maintenance:
22
- Offline:ip-×-×-×-×.ap-northeast-1.compute.internal←F/O先のサーバ
21
+ Offline:ip-×-×-×-×.ap-northeast-1.compute.internal←F/O先のサーバ
23
22
 
24
-
25
-
26
- #pcs status
23
+ #pcs config[server01]
27
-
28
24
  Cluster Name: aws-cluster
29
25
  Corosync Nodes:
30
- ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
26
+ ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
31
27
  Pacemaker Nodes:
32
- ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
28
+ ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
33
-
34
29
  Resources:
35
- Resource: eip (class=ocf provider=heartbeat type=eip)
30
+ Resource: eip (class=ocf provider=heartbeat type=eip)
36
- Attributes: elastic_ip=×.×.×.×
31
+ Attributes: elastic_ip=×.×.×.×
37
32
  Operations: start interval=0s timeout=60s on-fail=stop (eip-start-interval-0s)
38
33
  monitor interval=10s timeout=60s on-fail=restart (eip-monitor-interval-10s)
39
34
  stop interval=0s timeout=60s on-fail=block (eip-stop-interval-0s)
40
35
 
41
36
  Stonith Devices:
37
+ Fencing Levels:
38
+ Location Constraints:
39
+ Ordering Constraints:
40
+ Colocation Constraints:
41
+ Resources Defaults:
42
+ resource-stickiness: INFINITY
43
+ migration-threshold: 1
44
+ Operations Defaults:
45
+ No defaults set
46
+ Cluster Properties:
47
+ cluster-infrastructure: corosync
48
+ cluster-name: aws-cluster
49
+ transition-delay: 0s
50
+ dc-version: 1.1.13-10.el7-44eb2dd
51
+ have-watchdog: false
52
+ no-quorum-policy: ignore
53
+ stonith-enabled: false
54
+
55
+
56
+
57
+ #pcs config[server02]
58
+ Cluster Name: aws-cluster
59
+ Corosync Nodes:
60
+ ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
61
+ Pacemaker Nodes:
62
+ ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
63
+ Resources:
64
+ Stonith Devices:
42
65
  Fencing Levels:
43
-
44
66
  Location Constraints:
45
67
  Ordering Constraints:
46
68
  Colocation Constraints:
47
-
69
+ Ticket Constraints:
70
+ Alerts:
71
+ No alerts defined
48
72
  Resources Defaults:
49
- resource-stickiness: INFINITY
50
- migration-threshold: 1
73
+ No defaults set
51
74
  Operations Defaults:
52
- No defaults set
75
+ No defaults set
53
-
54
76
  Cluster Properties:
55
- cluster-infrastructure: corosync
77
+ cluster-infrastructure: corosync
56
- cluster-name: aws-cluster
78
+ cluster-name: aws-cluster
57
- transition-delay: 0s
58
- dc-version: 1.1.13-10.el7-44eb2dd
79
+ dc-version: 2.0.5-9.el8_4.1-ba59be7122
59
- have-watchdog: false
80
+ have-watchdog: false
60
- no-quorum-policy: ignore
81
+ Tags:
61
- stonith-enabled: false
82
+ No tags defined
83
+ Quorum:
84
+ Options:
62
85
 
63
-
64
86
  #crm_mon -f1（Node Listのみ記載します）
65
87
  Nodo List:
66
88
  ＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal:UNCLEAN(offline)←F/O先のサーバ
67
- ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]←操作しているサーバ
89
+ ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]←操作しているサーバ
90
+
91
+ #pcs status[server01]
92
+ Cluster name: aws-cluster
93
+ Cluster Summary:
94
+ ＊ Stack: corosync
95
+ ＊ Current DC: ip-×-×-×-×.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
96
+ ＊Last updated: Fri Jun 4 14:20:06 2021
97
+ ＊ Last change: Fri Jun 4 09:46:23 2021 by root via cibadmin on ip-×-×-×-×.ap-northeast-1.compute.internal
98
+ ＊2 nodes configured
99
+ ＊1 resource instance configured
100
+ Node List:
101
+ ＊Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
102
+ ＊OFFLINE: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
103
+
104
+ Full List of Resources:
105
+ ＊eip (ocf::heartbeat:eip): Stopped
106
+ Failed Resource Actions:
107
+
108
+ ＊eip_start_0 on ip-×-×-×-×.ap-northeast-1.compute.internal 'error' (1): call=6, status='complete', exitreason='', last-rc-change='2021-06-04 09:32:25 +09:00', queued=0ms, exec=12ms
109
+
110
+ Daemon Status:
111
+ corosync: active/disabled
112
+ pacemaker: active/disabled
113
+ pcsd: active/enabled
114
+
115
+ #pcs status[server02]
116
+ Cluster name: aws-cluster
117
+ WARNINGS:
118
+ No stonith devices and stonith-enabled is not false
119
+ Cluster Summary:
120
+ ＊ Stack: corosync
121
+ ＊ Current DC: ip-×-×-×-×1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
122
+ ＊ Last updated: Fri Jun 4 14:28:01 2021
123
+ ＊ Last change: Fri Jun 4 09:29:47 2021 by hacluster via crmd on ip-×-×-×-×.ap-northeast-1.compute.internal
124
+ ＊ 2 nodes configured
125
+ ＊ 0 resource instances configured
126
+ Node List:
127
+ ＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal: UNCLEAN (offline)
128
+ ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
129
+
130
+ Full List of Resources:
131
+ ＊ No resources
132
+ Daemon Status:
133
+ corosync: active/disabled
134
+ pacemaker: active/disabled
135
+ pcsd: active/enabled

1

文の追加

2021/06/04 05:48

投稿

kensan_p
kensan_p

スコア0

title CHANGED
File without changes
body CHANGED
@@ -1,25 +1,67 @@
1
1
  ### 前提・実現したいこと
2
2
 
3
- ここに質問の内容を詳しく書いてください。
4
- （例）PHP(CakePHP)で●●なシステムを作っています。
3
+ AWSを利用してMulti-AZのHA構成でサーバを構築しています。
4
+ 利用しているクラスターソフトはPacemekarとcorosyncです。
5
- ■■な機能を実装中に以下のエラーメッセージが発生しました。
5
+ VIPの設定を実施したところ上手く動作しません。
6
+ また、Pacemekar設定時からですがpcs statusで確認したところ自身のサーバのみOnlineになり、
7
+ 対象のサーバがOfflineになったままになります。
6
8
 
9
+ 下記の内容を参考に実施しております。
10
+ https://qiita.com/kenzo0107/items/851c002b6ea62f9a07c4
11
+
12
+ OS：Red Hat Enterprise Linux 8 with High Availability
13
+ AWSの設定は上記URLの内容とほとんど変更なし
14
+
7
15
  ### 発生している問題・エラーメッセージ
16
+ #pcs status node
17
+ Pacemaker Nodes:
18
+ Online:ip-×-×-×-×.ap-northeast-1.compute.internal←操作しているサーバ
19
+ Standby:
20
+ Standby with resource(s) running:
21
+ Maintenance:
22
+ Offline:ip-×-×-×-×.ap-northeast-1.compute.internal←F/O先のサーバ
8
23
 
9
- ```
10
- エラーメッセージ
11
- ```
12
24
 
13
- ### 該当のソースコード
14
25
 
15
- ```ここに言語名を入力
26
+ #pcs status
16
- ソースコード
17
- ```
18
27
 
28
+ Cluster Name: aws-cluster
19
- ### 試したこと
29
+ Corosync Nodes:
30
+ ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
31
+ Pacemaker Nodes:
32
+ ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
20
33
 
34
+ Resources:
35
+ Resource: eip (class=ocf provider=heartbeat type=eip)
21
- ここに問題に対して試したことを記載してください。
36
+ Attributes: elastic_ip=×.×.×.×
37
+ Operations: start interval=0s timeout=60s on-fail=stop (eip-start-interval-0s)
38
+ monitor interval=10s timeout=60s on-fail=restart (eip-monitor-interval-10s)
39
+ stop interval=0s timeout=60s on-fail=block (eip-stop-interval-0s)
22
40
 
41
+ Stonith Devices:
23
- ### 補足情報（FW/ツールのバージョンなど）
42
+ Fencing Levels:
24
43
 
44
+ Location Constraints:
45
+ Ordering Constraints:
46
+ Colocation Constraints:
47
+
48
+ Resources Defaults:
49
+ resource-stickiness: INFINITY
50
+ migration-threshold: 1
25
- ここにより詳細な情報を記載してください。
51
+ Operations Defaults:
52
+ No defaults set
53
+
54
+ Cluster Properties:
55
+ cluster-infrastructure: corosync
56
+ cluster-name: aws-cluster
57
+ transition-delay: 0s
58
+ dc-version: 1.1.13-10.el7-44eb2dd
59
+ have-watchdog: false
60
+ no-quorum-policy: ignore
61
+ stonith-enabled: false
62
+
63
+
64
+ #crm_mon -f1（Node Listのみ記載します）
65
+ Nodo List:
66
+ ＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal:UNCLEAN(offline)←F/O先のサーバ
67
+ ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]←操作しているサーバ