My issue was entirely due to a dns issue.<div><br></div><div>DRBD is working as expected now.<br><br><div class="gmail_quote">On Tue, Mar 23, 2010 at 8:24 AM, Cameron Smith <span dir="ltr"><<a href="mailto:velvetpixel@gmail.com">velvetpixel@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">From the user guide:<div><br></div><div>"<span style="font-size:15px;font-weight:bold">Dealing with
temporary primary node failure</span><p><a></a>
From DRBD's standpoint, failure of the primary node is
almost identical to a failure of the secondary node. The
surviving node detects the peer node's failure, and switches
to disconnected mode. DRBD does <span><em>not</em></span>
promote the surviving node to the primary role; it is the
cluster management application's responsibility to do
so.</p><p>When the failed node is repaired and returns to the
cluster, it does so in the secondary role, thus, as outlined
in the previous section, no further manual intervention is
necessary. Again, DRBD does not change the resource role back,
it is up to the cluster manager to do so (if so configured).
</p><p>DRBD ensures block device consistency in case of a primary
node failure by way of a special mechanism. For a detailed
discussion, refer to <a href="http://www.drbd.org/users-guide/s-activity-log.html" title="The
Activity Log" target="_blank">the section called “The Activity Log”</a>."</p><p><br></p><p>There are no instructions on what to tell the cluster manager to do.</p><p>When node1 (primary) goes down how do I get heartbeat to promote secondary to primary so that the filesystem at /dev/drbd1 on node2 can become mountable?</p>
<p>When node1 comes back up how to I configure heartbeat to tell node1 to become primary after it has been updated (synced) with the data from node2 that was created during node1's downtime?</p><div><div></div><div class="h5">
<p><br></p><br><div class="gmail_quote">
On Tue, Mar 23, 2010 at 8:07 AM, Cameron Smith <span dir="ltr"><<a href="mailto:velvetpixel@gmail.com" target="_blank">velvetpixel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thank you for the response!<div>Here is the output of cat /proc/drbd for both node1 and node2 before and after node1(primary) gets rebooted.</div><div><br></div><div><br></div><div>Before reboot:</div><div><div>[root@node1 ~]# cat /proc/drbd</div>
<div>version: 8.0.16 (api:86/proto:86)</div><div>GIT-hash: d30881451c988619e243d6294a899139eed1183d build by mockbuild@v20z-x86-64.home.local, 2009-08-22 13:26:57</div><div><br></div><div> 1: cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate C r---</div>
<div> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0</div><div><span style="white-space:pre"> </span>resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0</div><div><span style="white-space:pre"> </span>act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0</div>
<div><br></div><div><div>[root@node2 ~]# cat /proc/drbd</div><div>version: 8.0.16 (api:86/proto:86)</div><div>GIT-hash: d30881451c988619e243d6294a899139eed1183d build by mockbuild@v20z-x86-64.home.local, 2009-08-22 13:26:57</div>
<div><br></div><div> 1: cs:Connected st:Secondary/Primary ds:UpToDate/UpToDate C r---</div><div> ns:0 nr:4493035 dw:4493035 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0</div><div><span style="white-space:pre"> </span>resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0</div>
<div><span style="white-space:pre"> </span>act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0</div><div><br></div><div><br></div><div>After reboot of node1:</div><div><div>[root@node1 ~]# cat /proc/drbd</div>
<div>version: 8.0.16 (api:86/proto:86)</div><div>GIT-hash: d30881451c988619e243d6294a899139eed1183d build by mockbuild@v20z-x86-64.home.local, 2009-08-22 13:26:57</div><div><br></div><div> 1: cs:WFConnection st:Secondary/Unknown ds:UpToDate/DUnknown C r---</div>
<div> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0</div><div><span style="white-space:pre"> </span>resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0</div><div><span style="white-space:pre"> </span>act_log: used:0/127 hits:0 misses:0 starving:0 dirty:0 changed:0</div>
<div><br></div><div><div>[root@node2 ~]# cat /proc/drbd</div><div>version: 8.0.16 (api:86/proto:86)</div><div>GIT-hash: d30881451c988619e243d6294a899139eed1183d build by mockbuild@v20z-x86-64.home.local, 2009-08-22 13:26:57</div>
<div><br></div><div> 1: cs:StandAlone st:Secondary/Unknown ds:UpToDate/DUnknown r---</div><div> ns:0 nr:4493035 dw:4493043 dr:85 al:1 bm:1 lo:0 pe:0 ua:0 ap:0</div><div><span style="white-space:pre"> </span>resync: used:0/61 hits:0 misses:0 starving:0 dirty:0 changed:0</div>
<div><span style="white-space:pre"> </span>act_log: used:0/127 hits:1 misses:1 starving:0 dirty:0 changed:1</div><div><br></div><div><br></div><div>I am using heartbeat and this is my haresources contents:</div>
<div><a href="http://node1.example.com" target="_blank">node1.example.com</a> drbddisk::r0 Filesystem::/dev/drbd1::/data::ext3 10.10.2.21 mysqld httpd</div><div><br></div><div>Should there be anything else in the haresources file that forces node1 to primary on reboot?</div>
<div><br></div><div>Thank you,</div><div>Cameron</div><div><br></div></div><div><br></div></div></div><div><div></div><div><div><br></div><br><div class="gmail_quote">On Sun, Mar 21, 2010 at 6:14 PM, Reindy <span dir="ltr"><<a href="mailto:reindy@gmail.com" target="_blank">reindy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi, what is your current status? please brief us the details so that we can help you.<div><br></div><div>Example: give your output of "cat /proc/drbd"</div>
<div><br></div><div>you need to make sure that both of your nodes are sync and in WFConnection status,.. I still don't have the clear picture on your current situation, please let us know therefore we would able to help you.</div>
<div><br></div><div>Thanks!<br><div><br><div class="gmail_quote"><div><div></div><div>On Fri, Mar 19, 2010 at 12:50 AM, Cameron Smith <span dir="ltr"><<a href="mailto:velvetpixel@gmail.com" target="_blank">velvetpixel@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div>
I have two nodes.<div><br></div><div>Node one I set to proimary with:</div><div>drbdadm -- --overwrite-data-of-peer primary r0</div><div><br></div><div>That command does not survive a reboot of node1 so How do get get node1 to regain primary status after it comes back online?</div>
<div><br></div><div>When node1 comes back online will node2 write the data to node1 that was written during the downtime for node1?</div><div><br></div><div>Thanks!</div><div>Cameron</div>
<br></div></div><div>_______________________________________________<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/mailman/listinfo/drbd-user</a><br>
<br></div></blockquote></div><br></div></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br></div>