<div dir="ltr"><div>Hello to all,</div><div><br></div><div>I have now completely reinstalled my servers according <a href="https://alteeve.ca/w/AN!Cluster_Tutorial_2">https://alteeve.ca/w/AN!Cluster_Tutorial_2</a> on Centos 7 modified by some OS differences.</div><div>Anyway, it seems that I won't understand what I'm doing wrong?</div><div>As you could see res_drbd_1_stop on.... 'not installed' is returned. The last whole day spending on findinding my needle in the haystack wont make it better.</div><div><br></div><div>Any hints?,</div><div>Thanks</div><div><br></div><div><br></div><div><br></div><div>OUTPUT1:</div><div>crm_mon</div><div>Last updated: Wed Feb 4 09:59:01 2015</div><div>Last change: Wed Feb 4 05:18:41 2015 via crmd on at01srv01</div><div>Stack: corosync</div><div>Current DC: at01srv02 (167772162) - partition with quorum</div><div>Version: 1.1.10-32.el7_0.1-368c726</div><div>2 Nodes configured</div><div>4 Resources configured</div><div><br></div><div><br></div><div>Node at01srv01 (167772161): standby</div><div>Online: [ at01srv02 ]</div><div><br></div><div> Master/Slave Set: ms_drbd_1 [res_drbd_1]</div><div> res_drbd_1 (ocf::linbit:drbd): FAILED at01srv02 (unmanaged)</div><div> Stopped: [ at01srv01 ]</div><div>stonith_fence_pcmk_1 (stonith:fence_pcmk): Started at01srv02</div><div><br></div><div>Failed actions:</div><div> res_drbd_1_stop_0 on at01srv02 'not installed' (5): call=120, status=complete, last-rc-change='Wed Feb 4 09:3</div><div>5:43 2015', queued=15118ms, exec=0ms</div><div><br></div><div><br></div><div><br></div><div><br></div><div>OUTPUT2:</div><div><div>[root@at01srv02 linbit]# systemctl status drbd.service</div><div>drbd.service - DRBD -- please disable. Unless you are NOT using a cluster manager.</div><div> Loaded: loaded (/usr/lib/systemd/system/drbd.service; disabled)</div><div> Active: failed (Result: exit-code) since Mit 2015-02-04 09:57:06 CET; 2min 51s ago</div><div> Process: 8544 ExecStart=/sbin/drbdadm adjust-with-progress all (code=exited, status=1/FAILURE)</div><div> Process: 8540 ExecStartPre=/sbin/drbdadm sh-nop (code=exited, status=0/SUCCESS)</div><div> Main PID: 8544 (code=exited, status=1/FAILURE)</div><div><br></div><div>Feb 04 09:57:06 at01srv02 drbdadm[8544]: [</div><div>Feb 04 09:57:06 at01srv02 drbdadm[8544]: adjust net: r0:failed(net-options:20)</div><div>Feb 04 09:57:06 at01srv02 drbdadm[8544]: ]</div><div>Feb 04 09:57:06 at01srv02 systemd[1]: drbd.service: main process exited, code=exited, status=1/FAILURE</div><div>Feb 04 09:57:06 at01srv02 systemd[1]: Failed to start DRBD -- please disable. Unless you are NOT using a c...ger..</div><div>Feb 04 09:57:06 at01srv02 systemd[1]: Unit drbd.service entered failed state.</div><div>Hint: Some lines were ellipsized, use -l to show in full.</div></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-02-02 20:46 GMT+01:00 Digimer <span dir="ltr"><<a href="mailto:lists@alteeve.ca" target="_blank">lists@alteeve.ca</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 02/02/15 02:44 PM, Ivan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm not sure that two (or more) LUKS partitions are identical given<br>
exactly the same cleartext content and the same keys. There must be some<br>
kind of sector randomization when writing data to make cryptoanalysis<br>
harder, so it makes me think that it's not the case (that would require<br>
testing though).<br>
If I'm right, I don't see how DRBD could work in that setup. (or maybe I<br>
just need more sleep).<br>
</blockquote>
<br>
LUKS is working on the LV, which will be backed by the PV on DRBD. DRBD<br>
doesn't know data, so it will simply replicate the LUKS structure<br>
faithfully to both nodes.<br>
<br>
Remember, for all intent and purpose, there is only one device/luks<br>
partition. DRBD is really no different from LUKS on /dev/mdX devices in<br>
this regard.<br>
</blockquote>
<br>
ah that's right - indeed more sleep needed. I've skipped the "clustered<br>
LVM" part and was thinking about two luks partitions.<br>
<br>
sorry for the noise.<br>
</blockquote>
<br></span>
No worries at all. When you ask a question like this, you have a chance to learn a system better, so it's good. :)<span class="im HOEnZb"><br>
<br>
-- <br>
Digimer<br>
Papers and Projects: <a href="https://alteeve.ca/w/" target="_blank">https://alteeve.ca/w/</a><br>
What if the cure for cancer is trapped in the mind of a person without access to education?<br></span><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
drbd-user mailing list<br>
<a href="mailto:drbd-user@lists.linbit.com" target="_blank">drbd-user@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" target="_blank">http://lists.linbit.com/<u></u>mailman/listinfo/drbd-user</a><br>
</div></div></blockquote></div><br></div>