Takehiro Matsushima
takeh****@gmail*****
2017年 7月 21日 (金) 17:49:54 JST
大川さん DRBD9に詳しくなくて申し訳ございません。 こちら↓と同じように見えますが、この方はノードを再起動してうまくいっているようです。 http://lists.linbit.com/pipermail/drbd-user/2016-July/022513.html drbdmanageプロセスを止めてから…と言われていますが… 家に帰ったら少し試してみます。 松島 2017-07-21 13:07 GMT+09:00 大川敬臣 <yoshi****@kccs*****>: > 松島さん > > ご連絡ありがとうございます。 > > FirewalldとSELinuxは確認しておりますが、 > 無効になっております。 > firewalldはインストールされていないように見えますが。。。 > > # systemctl status firewalld > Unit firewalld.service could not be found. > > # > # rpm -qa | grep fire > # > > # getenforce > Disabled > > > 2017-07-21 12:48 GMT+09:00 Takehiro Matsushima > <takeh****@gmail*****>: >> >> 大川さん >> >> 松島と申します。 >> >> systemctl stop firewalld >> setenforce 0 >> してみてどうでしょうか？？ >> >> 2017/07/21 午前10:09 "大川敬臣" <yoshi****@kccs*****>: >> >> いつもお世話になっております。 >> >> 大川と申します。 >> >> RHEL7.3環境で、DRBD9.0.8のインストールおよび、設定について質問させてください。 >> >> 【構成】 >> OS：RHEL 7.3 >> Kernel version:3.10.0-514.el7.x86_64 >> DRBD:drbd-9.0.8-1 >> drbd-utils-9.0.0 >> drbdmanage-0.99 >> HOST名：DRBD01、DRBD02 >> DRBD領域:/dev/xvdb >> >> ・DRBD領域をMｙSQLのデータ領域として使用 >> ・検証中のためAWS環境で構築 >> >> 【インストールした手順】 >> ・必要パッケージのインストール >> # yum -y install kernel-devel.x86_64 >> # yum -y install gcc.x86_64 >> # yum -y install flex.x86_64 >> >> ・DRBDのインストール >> # cd /usr/local/src/ >> # tar zxf drbd-9.0.8-1.tar.gz >> # cd drbd-9.0.8-1 >> # make KDIR=/usr/src/kernels/$(uname -r) >> # make install >> # modprobe drbd >> # cat /proc/drbd >> >> ・drbd-utilのインストール >> # cd /usr/local/src/ >> # tar zxf drbd-utils-9.0.0.tar.gz >> # cd drbd-utils-9.0.0 >> # ./configure >> # make >> # make install >> >> ・DRBD Manageインストール >> # cd /usr/local/src/ >> # tar zxf drbdmanage-0.99.tar.gz >> # cd drbdmanage-0.99 >> # ./setup.py build >> # ./setup.py install >> >> 【DRBD初期設定】 >> - プールの作成 >> # vgcreate drbdpool /dev/xvdb1 >> Physical volume "/dev/xvdb1" successfully created. >> Volume group "drbdpool" successfully created >> # >> >> - DRBD01で実施 >> # drbdmanage init >> >> You are going to initialize a new drbdmanage cluster. >> CAUTION! Note that: >> * Any previous drbdmanage cluster information may be removed >> * Any remaining resources managed by a previous drbdmanage installation >> that still exist on this system will no longer be managed by >> drbdmanage >> >> Confirm: >> >> yes/no: yes >> Empty drbdmanage control volume initialized on '/dev/drbd0'. >> Empty drbdmanage control volume initialized on '/dev/drbd1'. >> Waiting for server: . >> Operation completed successfully >> # >> # drbdadm status >> .drbdctrl role:Primary >> volume:0 disk:UpToDate >> volume:1 disk:UpToDate >> >> # >> # lvdisplay -c >> /dev/drbdpool/.drbdctrl_0:drbdpool:3:1:-1:2:8192:1:-1:0:-1:253:0 >> /dev/drbdpool/.drbdctrl_1:drbdpool:3:1:-1:2:8192:1:-1:0:-1:253:1 >> # >> # drbdmanage list-nodes >> >> +------------------------------------------------------------------------------------------------------------+ >> | Name | Pool Size | Pool Free >> | | State | >> >> |------------------------------------------------------------------------------------------------------------| >> | ip-172-31-1-155.ap-northeast-1.compute.internal | 10236 | 10228 >> | | ok | >> >> +------------------------------------------------------------------------------------------------------------+ >> # >> # drbdmanage new-node ip-172-31-8-103.ap-northeast-1.compute.internal >> 172.31.8.103 >> Operation completed successfully >> Operation completed successfully >> >> Executing join command using ssh. >> IMPORTANT: The output you see comes from >> ip-172-31-8-103.ap-northeast-1.compute.internal >> IMPORTANT: Your input is executed on >> ip-172-31-8-103.ap-northeast-1.compute.internal >> You are going to join an existing drbdmanage cluster. >> CAUTION! Note that: >> * Any previous drbdmanage cluster information may be removed >> * Any remaining resources managed by a previous drbdmanage installation >> that still exist on this system will no longer be managed by >> drbdmanage >> >> Confirm: >> >> yes/no: yes >> ERROR:dbus.proxies:Introspect error on :1.26:/interface: >> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not >> receive a reply. Possible causes include: the remote application did not >> send a reply, the message bus security policy blocked the reply, the reply >> timeout expired, or the network connection was broken. >> Waiting for server: ...... >> Operation completed successfully >> # >> # drbdmanage howto-join ip-172-31-8-103.ap-northeast-1.compute.internal >> IMPORTANT: Execute the following command only on node >> ip-172-31-8-103.ap-northeast-1.compute.internal! >> drbdmanage join -p 6999 172.31.8.103 1 >> ip-172-31-1-155.ap-northeast-1.compute.internal 172.31.1.155 0 >> +tz+CGAKCb0YwuD+E1NM >> Operation completed successfully >> # >> >> - DRBD02で実施 >> # drbdmanage join -p 6999 172.31.8.103 1 >> ip-172-31-1-155.ap-northeast-1.compute.internal 172.31.1.155 0 >> +tz+CGAKCb0YwuD+E1NM >> You are going to join an existing drbdmanage cluster. >> CAUTION! Note that: >> * Any previous drbdmanage cluster information may be removed >> * Any remaining resources managed by a previous drbdmanage installation >> that still exist on this system will no longer be managed by >> drbdmanage >> >> Confirm: >> >> yes/no: yes >> Operation completed successfully >> # >> >> - drbdmanage list-nodesを各ノードで実施 >> - DRBD01で実施 >> # drbdmanage list-nodes >> >> +------------------------------------------------------------------------------------------------------------+ >> | Name | Pool Size | Pool Free >> | | State | >> >> |------------------------------------------------------------------------------------------------------------| >> | ip-172-31-1-155.ap-northeast-1.compute.internal | 10236 | 10228 >> | | ok | >> | ip-172-31-8-103.ap-northeast-1.compute.internal | 10236 | 10228 >> | | offline/quorum vote ignored | >> >> +------------------------------------------------------------------------------------------------------------+ >> >> - DRBD02で実施 >> # drbdmanage list-nodes >> ERROR:dbus.proxies:Introspect error on :1.26:/interface: >> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not >> receive a reply. Possible causes include: the remote application did not >> send a reply, the message bus security policy blocked the reply, the reply >> timeout expired, or the network connection was broken. >> Waiting for server: ...... >> >> +------------------------------------------------------------------------------------------------------------+ >> | Name | Pool Size | Pool Free >> | | State | >> >> |------------------------------------------------------------------------------------------------------------| >> | ip-172-31-1-155.ap-northeast-1.compute.internal | 10236 | 10228 >> | | OFFLINE | >> | ip-172-31-8-103.ap-northeast-1.compute.internal | 10236 | 10228 >> | | online/quorum vote ignored | >> >> +------------------------------------------------------------------------------------------------------------+ >> # >> >> >> 【確認したいこと】 >> googleで調べて出てきたサイトを参考に上記のようにインストール、設定しましたが、 >> DRBD02のstateがOKにならずに困っております。 >> DRBD02を追加する時点でDBusのエラーが出ているのですが、そのエラーもどこを確認してよいか >> 分からずに困っております。 >> お手数ですが、stateをOKにするためにはどこを調査したら良いのかのアドバイスをいただけないでしょうか。 >> >> >> _______________________________________________ >> Linux-ha-japan mailing list >> Linux****@lists***** >> http://lists.osdn.me/mailman/listinfo/linux-ha-japan >> >> >> >> _______________________________________________ >> Linux-ha-japan mailing list >> Linux****@lists***** >> http://lists.osdn.me/mailman/listinfo/linux-ha-japan >> > > > _______________________________________________ > Linux-ha-japan mailing list > Linux****@lists***** > http://lists.osdn.me/mailman/listinfo/linux-ha-japan >
Fork