On Nov 28, 2007, at 5:41 AM, Amos Shapira wrote:
Hello,
I've been trying to follow the instructions in
http://wiki.centos.org/HowTos/Ha-Drbd to setup a basic DRBD test
cluster on top of a couple of Xen guests.
In case this matters, both Xen guests and Xen Dom0 run CentOS 5 which
comes with Heartbeat 2.1.2-3 and DRBD 8.0.6.
Another point is that my colleague is setting up a test on another
couple of tests so I am careful not to use broadcast on the default
port (either using a different port or using mcast).
What I see is that the primary node comes up but never sees the
secondary one.
Here is /etc/ha.d/ha.cf so far (not resources configured yet in CRM):
----8
<
---------------------------------------------------------------------------
keepalive 2
deadtime 30
warntime 10
initdead 120
udpport 695
bcast eth0
node drbd01.test
node drbd02.test
crm yes
----8
<
---------------------------------------------------------------------------
And when I start heartbeat and crm_mon it shows (after about a
minute):
----8
<
---------------------------------------------------------------------------
Refresh in 1s...
============
Last updated: Thu Nov 29 02:25:55 2007
Current DC: drbd01.test (580f615c-2921-4ba6-b03e-9a6e179d9ae2)
1 Nodes configured.
0 Resources configured.
============
Node: drbd01.test (580f615c-2921-4ba6-b03e-9a6e179d9ae2): online
----8
<
---------------------------------------------------------------------------
The instructions in the above-mentioned link say that both nodes
should have been displayed (of course I copied the files over to the
other node and started heartbeat on it as well).
The other node never gets out of a state of "Not connected: Refresh
in 2s..."
I see the traffic going between the nodes in tcpdump. There is no
firewall on the hosts.
Both host names resolve properly.
What am I missing?
logs from the other node that might allow us to see what the problem is
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
