<html><head></head><body><p dir="ltr">I have been getting the same problem. Fresh install from Proxmox 4.2 DRBD9. I get the dreaded DBus error. I can't get the secondary to work at all the DBUS errors on everything using dbus. Been waiting for a resolution for a long time from DRBD9 developers. I think they just gave up. DRBD9 is not ready for use yet. I suggest you move to ceph. I am working on doing that as well. Proxmox decided to rip out the stable DRBD 8.x version to put in 9. I got it working once and after a reboot it never worked again. </p>
<p dir="ltr">So I wouldn't put DRBD9 into anything critical. I even had their DRBD9 staff try to resolve it. Glad I didn't have it in production. </p>
<p dir="ltr"><!-- tmjah_g_1299s -->--Jaso<!-- tmjah_g_1299e -->n</p>
<div class="gmail_quote" >On Jun 7, 2016, at 3:10 PM, Michele Rossetti <<a href="mailto:rossetti@sardi.it" target="_blank">rossetti@sardi.it</a>> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="blue">Thanks, Roland,<br><br>but it seems impossible to configure with drbdmanage a complete mesh <br>configuration with 2 interfaces (cross patch) for each node.<br>Here below the mails with Petra Trunner that confirmed me the manual <br>config is right. Must I connect the 3 nodes with only 1 interfaces <br>and the use of switches?<br>Regards,<br>Michele<br><br>Subject: Re: DRBD - your request<br>From: Petra Trunner <Petra.trunner@linbit.com><br><br>Hi Michele,<br><br>yes, that's the right way how you've done it.<br><br>To your last question: not yet, but very soon.<br><br>Did you know? We have a DRBD mailing list <br><a href="http://lists.linbit.com/mailman/listinfo/drbd-user">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br><br>There, you can register and also take a look at the linked archive.<br><br><br>Regards,<br><br>Petra<br><br><br>Am 17.05.16 um 10:16 schrieb Michele Rossetti:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex;
border-left: 1px solid #729fcf; padding-left: 1ex;">Re: DRBD - your request<br>Dear Petra,<br>thank you for your reply, and I'm sorry to disturb you again, but in <br>the userguide you suggested I cannot find how to configure the <br>connection as indicated in DRBD9 userguide PDF at point 5.8 for <br>complete mash (I have 3 servers each one with 2 NICs dedicated to <br>DRBD, connected with cross cables.<br><br>Must I modify manually the drbdctrl.res created by DRBDmanage, adding:<br><br># mpve1-2 have crossover links like 192.168.65.x<br>connection {<br>host mpve1 address <a href="http://192.168.65.135">192.168.65.135</a> port 7012;<br>host mpve2 address <a href="http://192.168.65.136">192.168.65.136</a> port 7021;<br>}<br># mpve1-3 have crossover links like 192.168.67.x<br>connection {<br>host mpve1 address <a href="http://192.168.67.135">192.168.67.135</a> port 7013;<br>host mpve3 address <a href="http://192.168.67.137">192.168.67.137</a> port 7031;<br>}<br># mpve2-3 have
crossover links like 192.168.66.x<br>connection {<br>host mpve2 address <a href="http://192.168.66.136">192.168.66.136</a> port 7023;<br>host mpve3 address <a href="http://192.168.66.137">192.168.66.137</a> port 7032;<br>}<br>or there is a method with DRBDmanage (not clearly specified in the manual?<br><br>Thanks again for your kindness,<br>have a nice day,<br>Michele<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">Dear Michele,<br><br>I wouldn't create such cluster's config by hand, therefor we created<br>DRBDmanage. Have a look at the setup guide, it makes adding those nodes<br>to your cluster much easier than it was before:<br><a href="https://www.drbd.org/en/doc/users-guide-90/ch-admin-drbdmanage">https://www.drbd.org/en/doc/users-guide-90/ch-admin-drbdmanage</a><br><br>Kind regards,<br>Petra<br><br>--<br>Petra Trunner<br>DRBD - Corosync - Pacemaker<br><br>Dear Michele,<br><br>I wouldn't create such
cluster's config by hand, therefor we created<br>DRBDmanage. Have a look at the setup guide, it makes adding those nodes<br>to your cluster much easier than it was before:<br><a href="https://www.drbd.org/en/doc/users-guide-90/ch-admin-drbdmanage">https://www.drbd.org/en/doc/users-guide-90/ch-admin-drbdmanage</a><br><br>Kind regards,<br>Petra<br>--<br></blockquote></blockquote>Petra Trunner<br><br>At 14:24 +0200 07.06.2016, Roland Kammerer wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On Tue, Jun 07, 2016 at 01:22:03PM +0200, Michele Rossetti wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Hi all,<br> Here below the drbdctrl.res, manually configurated regarding connections:<br></blockquote><br>No. You are not supposed to touch any resource files drbdmanage<br>generates, especially not the one it uses for its cluster
database (aka<br>the control volume). These files get overwritten.<br><br>nodea:$ drbdmanage init IP_OF_INTERFACE_FOR_CLUSTER_COMMUNICATION<br><br>nodea:$ drbdmanage new-node nodeb NODEBIP<br>nodea:$ drbdmanage new-node nodec NODECIP<br><br>If you want to make life easy, ssh-copy-id nodea's ssh key to nodeb and<br>nodec.<br><br>Regards, rck<br><hr><br>drbd-user mailing list<br>drbd-user@lists.linbit.com<br><a href="http://lists.linbit.com/mailman/listinfo/drbd-user">http://lists.linbit.com/mailman/listinfo/drbd-user</a><br></blockquote><br></pre></blockquote></div></body></html>