トップに関する質問 AWSでのVIP設定をpacemakerとcorosyncにて実施可能かどうか

編集履歴

質問編集履歴

修正

2021/06/06 21:43

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -372,7 +372,7 @@
 Failed Resource Actions:
-  * 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
+  * 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

修正

2021/06/06 21:43

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -372,7 +372,7 @@
 Failed Resource Actions:
-  * 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
+  * 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

修正

2021/06/06 21:42

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -350,7 +350,7 @@
   * Last updated: Mon Jun  7 03:39:48 2021
-  * Last change:  Mon Jun  7 03:23:05 2021 by root via cibadmin on ip-10-0-0-2.ap-northeast-1.compute.internal
+  * Last change:  Mon Jun  7 03:23:05 2021 by root via cibadmin on ip-10-10-10-2.ap-northeast-1.compute.internal
   * 2 nodes configured

修正

2021/06/06 19:16

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -338,7 +338,7 @@
-#Online後のpcs status
+#Online後のpcs status [server01]
 Cluster name: aws-cluster

追記

2021/06/06 19:15

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -335,3 +335,51 @@
     timestamp: on
 }
+#Online後のpcs status
+Cluster name: aws-cluster
+Cluster Summary:
+  * Stack: corosync
+  * Current DC: ip-10-10-10-1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition with quorum
+  * Last updated: Mon Jun  7 03:39:48 2021
+  * Last change:  Mon Jun  7 03:23:05 2021 by root via cibadmin on ip-10-0-0-2.ap-northeast-1.compute.internal
+  * 2 nodes configured
+  * 1 resource instance configured
+Node List:
+  * Online: [ ip-10-10-10-1.ap-northeast-1.compute.internal ip-10-10-10-2.ap-northeast-1.compute.internal ]
+Full List of Resources:
+  * eip (ocf::heartbeat:eip):    Stopped
+Failed Resource Actions:
+  * 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
+Daemon Status:
+  corosync: active/enabled
+  pacemaker: active/enabled
+  pcsd: active/enabled

修正

2021/06/06 19:14

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -282,11 +282,7 @@
       version: 2
-      transport:knet←ここをudpu、udpに変更したがサービス再起動でエラー
+      transport:udpu
-　　crypto_cipher: aes256
-      crypto_hash: sha256
 }

追記

2021/06/04 12:52

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -273,3 +273,69 @@
  pacemaker: active/disabled
   pcsd: active/enabled
+# corosync.conf
+totem {
+      version: 2
+      transport:knet←ここをudpu、udpに変更したがサービス再起動でエラー
+　　crypto_cipher: aes256
+      crypto_hash: sha256
+}
+nodelist {
+    node {
+　　　　 ring0_addr: 10.10.10.1
+　　　　 name: ip-10-10-10-1.ap-northeast-1.compute.internal
+　　　　 nodeid: 1
+    }
+    node {
+　　　　 ring0_addr: 10.10.10.2
+　　　　 name: ip-10-10-10-2.ap-northeast-1.compute.internal
+　　　　 nodeid: 2
+    }
+}
+quorum {
+    provider: corosync_votequorum
+    two_node: 2
+}
+logging {
+    to_logfile: yes
+    logfile: /var/log/cluster/corosync.log
+    timestamp: on
+}

修正

2021/06/04 12:35

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -26,11 +26,11 @@
-#pcs status node
+#pcs status node[server01]
-Pacemaker Nodes:
+Pacemaker Nodes:
-Online:ip-×-×-×-×.ap-northeast-1.compute.internal←操作しているサーバ
+Online:ip-10-10-10-1.ap-northeast-1.compute.internal
 Standby:
@@ -38,7 +38,23 @@
 Maintenance:
-Offline:ip-×-×-×-×.ap-northeast-1.compute.internal←F/O先のサーバ
+Offline:ip-10-10-10-2.ap-northeast-1.compute.internal
+#pcs status node[server02]
+Pacemaker Nodes:
+Online:ip-10-10-10-2.ap-northeast-1.compute.internal
+Standby:
+Standby with resource(s) running:
+Maintenance:
+Offline:ip-10-10-10-1.ap-northeast-1.compute.internal
@@ -48,17 +64,17 @@
 Corosync Nodes:
-ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+ip-10-10-10-1.ap-northeast-1.compute.internal ip-10-10-10-2.ap-northeast-1.compute.internal
-Pacemaker Nodes:
+Pacemaker Nodes:
-ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+ip-10-10-10-1.ap-northeast-1.compute.internal ip-10-10-10-2.ap-northeast-1.compute.internal
 Resources:
 Resource: eip (class=ocf provider=heartbeat type=eip)
- Attributes: elastic_ip=×.×.×.×
+ Attributes: elastic_ip=1.1.1.1←例
   Operations: start interval=0s timeout=60s on-fail=stop (eip-start-interval-0s)
@@ -116,11 +132,11 @@
 Corosync Nodes:
-ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+ip-10-10-10-2.ap-northeast-1.compute.internal ip-10-10-10-1.ap-northeast-1.compute.internal
-Pacemaker Nodes:
+Pacemaker Nodes:
-ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+ip-10-10-10-2.ap-northeast-1.compute.internal ip-10-10-10-1.ap-northeast-1.compute.internal
 Resources:
@@ -168,16 +184,6 @@
-#crm_mon -f1（Node Listのみ記載します）
-Nodo List:
-＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal:UNCLEAN(offline)←F/O先のサーバ
-＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]←操作しているサーバ
 #pcs status[server01]
 Cluster name: aws-cluster
@@ -186,11 +192,11 @@
   ＊ Stack: corosync
-  ＊ Current DC: ip-×-×-×-×.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
+  ＊ Current DC: ip-10-10-10-1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
   ＊Last updated: Fri Jun  4 14:20:06 2021
-  ＊ Last change:  Fri Jun  4 09:46:23 2021 by root via cibadmin on ip-×-×-×-×.ap-northeast-1.compute.internal
+  ＊ Last change:  Fri Jun  4 09:46:23 2021 by root via cibadmin on ip-10-10-10-1.ap-northeast-1.compute.internal
   ＊2 nodes configured
@@ -198,9 +204,9 @@
 Node List:
-  ＊Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
+  ＊Online: [ ip-10-10-10-1.ap-northeast-1.compute.internal ]
-  ＊OFFLINE: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
+  ＊OFFLINE: [ ip-10-10-10-2.ap-northeast-1.compute.internal ]
@@ -212,7 +218,7 @@
-  ＊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
+  ＊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
@@ -238,11 +244,11 @@
   ＊ Stack: corosync
-  ＊ Current DC: ip-×-×-×-×1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
+  ＊ Current DC: ip-10-10-10-2.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
   ＊ Last updated: Fri Jun  4 14:28:01 2021
-  ＊ Last change:  Fri Jun  4 09:29:47 2021 by hacluster via crmd on ip-×-×-×-×.ap-northeast-1.compute.internal
+  ＊ Last change:  Fri Jun  4 09:29:47 2021 by hacluster via crmd on ip-10-10-10-2.ap-northeast-1.compute.internal
   ＊ 2 nodes configured
@@ -250,9 +256,9 @@
 Node List:
-  ＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal: UNCLEAN (offline)
+  ＊ Node ip-10-10-10-1.ap-northeast-1.compute.internal: UNCLEAN (offline)
-  ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
+  ＊ Online: [ ip-10-10-10-2.ap-northeast-1.compute.internal ]

追記

2021/06/04 06:26

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -1,7 +1,5 @@
 ### 前提・実現したいこと
 AWSを利用してMulti-AZのHA構成でサーバを構築しています。
 利用しているクラスターソフトはPacemekarとcorosyncです。
@@ -24,51 +22,43 @@
 AWSの設定は上記URLの内容とほとんど変更なし
 ### 発生している問題・エラーメッセージ
 #pcs status node
 Pacemaker Nodes:
- Online:ip-×-×-×-×.ap-northeast-1.compute.internal←操作しているサーバ
+Online:ip-×-×-×-×.ap-northeast-1.compute.internal←操作しているサーバ
- Standby:
+Standby:
- Standby with resource(s) running:
+Standby with resource(s) running:
- Maintenance:
+Maintenance:
- Offline:ip-×-×-×-×.ap-northeast-1.compute.internal←F/O先のサーバ
+Offline:ip-×-×-×-×.ap-northeast-1.compute.internal←F/O先のサーバ
-#pcs status
+#pcs config[server01]
 Cluster Name: aws-cluster
 Corosync Nodes:
- ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
 Pacemaker Nodes:
- ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
 Resources:
- Resource: eip (class=ocf provider=heartbeat type=eip)
+Resource: eip (class=ocf provider=heartbeat type=eip)
-  Attributes: elastic_ip=×.×.×.×
+ Attributes: elastic_ip=×.×.×.×
   Operations: start interval=0s timeout=60s on-fail=stop (eip-start-interval-0s)
@@ -80,47 +70,101 @@
 Stonith Devices:
+Fencing Levels:
+Location Constraints:
+Ordering Constraints:
+Colocation Constraints:
+Resources Defaults:
+resource-stickiness: INFINITY
+migration-threshold: 1
+Operations Defaults:
+No defaults set
+Cluster Properties:
+cluster-infrastructure: corosync
+cluster-name: aws-cluster
+transition-delay: 0s
+dc-version: 1.1.13-10.el7-44eb2dd
+have-watchdog: false
+no-quorum-policy: ignore
+stonith-enabled: false
+#pcs config[server02]
+Cluster Name: aws-cluster
+Corosync Nodes:
+ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+Pacemaker Nodes:
+ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+Resources:
+Stonith Devices:
 Fencing Levels:
 Location Constraints:
 Ordering Constraints:
 Colocation Constraints:
+Ticket Constraints:
+Alerts:
+No alerts defined
 Resources Defaults:
- resource-stickiness: INFINITY
- migration-threshold: 1
+  No defaults set
 Operations Defaults:
- No defaults set
+  No defaults set
 Cluster Properties:
- cluster-infrastructure: corosync
+cluster-infrastructure: corosync
- cluster-name: aws-cluster
+cluster-name: aws-cluster
- transition-delay: 0s
- dc-version: 1.1.13-10.el7-44eb2dd
+dc-version: 2.0.5-9.el8_4.1-ba59be7122
- have-watchdog: false
+have-watchdog: false
- no-quorum-policy: ignore
+Tags:
- stonith-enabled: false
+No tags defined
+Quorum:
+  Options:
@@ -131,3 +175,95 @@
 ＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal:UNCLEAN(offline)←F/O先のサーバ
 ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]←操作しているサーバ
+#pcs status[server01]
+Cluster name: aws-cluster
+Cluster Summary:
+  ＊ Stack: corosync
+  ＊ Current DC: ip-×-×-×-×.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
+  ＊Last updated: Fri Jun  4 14:20:06 2021
+  ＊ Last change:  Fri Jun  4 09:46:23 2021 by root via cibadmin on ip-×-×-×-×.ap-northeast-1.compute.internal
+  ＊2 nodes configured
+  ＊1 resource instance configured
+Node List:
+  ＊Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
+  ＊OFFLINE: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
+Full List of Resources:
+  ＊eip (ocf::heartbeat:eip):    Stopped
+Failed Resource Actions:
+  ＊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
+Daemon Status:
+  corosync: active/disabled
+  pacemaker: active/disabled
+  pcsd: active/enabled
+#pcs status[server02]
+Cluster name: aws-cluster
+WARNINGS:
+No stonith devices and stonith-enabled is not false
+Cluster Summary:
+  ＊ Stack: corosync
+  ＊ Current DC: ip-×-×-×-×1.ap-northeast-1.compute.internal (version 2.0.5-9.el8_4.1-ba59be7122) - partition WITHOUT quorum
+  ＊ Last updated: Fri Jun  4 14:28:01 2021
+  ＊ Last change:  Fri Jun  4 09:29:47 2021 by hacluster via crmd on ip-×-×-×-×.ap-northeast-1.compute.internal
+  ＊ 2 nodes configured
+  ＊ 0 resource instances configured
+Node List:
+  ＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal: UNCLEAN (offline)
+  ＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]
+Full List of Resources:
+  ＊ No resources
+Daemon Status:
+  corosync: active/disabled
+ pacemaker: active/disabled
+  pcsd: active/enabled

文の追加

2021/06/04 05:48

投稿

kensan_p

スコア0

test CHANGED Viewed

File without changes

test CHANGED Viewed

@@ -2,48 +2,132 @@
-ここに質問の内容を詳しく書いてください。
+AWSを利用してMulti-AZのHA構成でサーバを構築しています。
-（例）PHP(CakePHP)で●●なシステムを作っています。
+利用しているクラスターソフトはPacemekarとcorosyncです。
-■■な機能を実装中に以下のエラーメッセージが発生しました。
+VIPの設定を実施したところ上手く動作しません。
+また、Pacemekar設定時からですがpcs statusで確認したところ自身のサーバのみOnlineになり、
+対象のサーバがOfflineになったままになります。
+下記の内容を参考に実施しております。
+https://qiita.com/kenzo0107/items/851c002b6ea62f9a07c4
+OS：Red Hat Enterprise Linux 8 with High Availability
+AWSの設定は上記URLの内容とほとんど変更なし
 ### 発生している問題・エラーメッセージ
+#pcs status node
+Pacemaker Nodes:
-```
+ Online:ip-×-×-×-×.ap-northeast-1.compute.internal←操作しているサーバ
-エラーメッセージ
+ Standby:
+ Standby with resource(s) running:
-```
+ Maintenance:
+ Offline:ip-×-×-×-×.ap-northeast-1.compute.internal←F/O先のサーバ
-### 該当のソースコード
-```ここに言語名を入力
-ソースコード
+#pcs status
-```
+Cluster Name: aws-cluster
-### 試したこと
+Corosync Nodes:
+ ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+Pacemaker Nodes:
+ ip-×-×-×-×.ap-northeast-1.compute.internal ip-×-×-×-×.ap-northeast-1.compute.internal
+Resources:
+ Resource: eip (class=ocf provider=heartbeat type=eip)
-ここに問題に対して試したことを記載してください。
+  Attributes: elastic_ip=×.×.×.×
+  Operations: start interval=0s timeout=60s on-fail=stop (eip-start-interval-0s)
+              monitor interval=10s timeout=60s on-fail=restart (eip-monitor-interval-10s)
+              stop interval=0s timeout=60s on-fail=block (eip-stop-interval-0s)
+Stonith Devices:
-### 補足情報（FW/ツールのバージョンなど）
+Fencing Levels:
+Location Constraints:
+Ordering Constraints:
+Colocation Constraints:
+Resources Defaults:
+ resource-stickiness: INFINITY
+ migration-threshold: 1
-ここにより詳細な情報を記載してください。
+Operations Defaults:
+ No defaults set
+Cluster Properties:
+ cluster-infrastructure: corosync
+ cluster-name: aws-cluster
+ transition-delay: 0s
+ dc-version: 1.1.13-10.el7-44eb2dd
+ have-watchdog: false
+ no-quorum-policy: ignore
+ stonith-enabled: false
+#crm_mon -f1（Node Listのみ記載します）
+Nodo List:
+＊ Node ip-×-×-×-×.ap-northeast-1.compute.internal:UNCLEAN(offline)←F/O先のサーバ
+＊ Online: [ ip-×-×-×-×.ap-northeast-1.compute.internal ]←操作しているサーバ