<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.12.0">
</HEAD>
<BODY>
I think I got it, and for the forum, here's what I did. I'm guessing that somehow I wound up with a split brain condition within DRBD. Though I could influence the cs state by starting drbd on each node in a different order (which led me to conclude they WERE talking, just refusing to connect), they would not complete the connection. I found on the man page for drbdsetup, under the NET command, the option -D, and the key phrase "nodes refuse to connect" ;)<BR>
<BR>
The command I used was:<BR>
<BR>
<TT>drbdsetup /dev/drbd0 NET 10.4.4.5 10.4.4.4 C -D</TT><BR>
<BR>
The partitions are now connected and resyncing. <BR>
<BR>
Doug<BR>
<BR>
On Fri, 2007-05-04 at 15:43 +0200, Lars Ellenberg wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">On Fri, May 04, 2007 at 09:32:30AM -0400, Doug Knight wrote:</FONT>
<FONT COLOR="#000000">> Does anyone know what could cause the two drbd processes to not connect? I</FONT>
<FONT COLOR="#000000">> managed to get a reboot in on the other server, and still they are not</FONT>
<FONT COLOR="#000000">> connecting and synching. The drbd mirrored pair has been down almost 16 hours</FONT>
<FONT COLOR="#000000">> now.</FONT>
<FONT COLOR="#000000">there should be something in your kernel logs...</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>