El 08/10/2012 20:56, Andreas Kurz escribió: > On 10/08/2012 09:42 PM, Nicolás wrote: >> El 28/09/2012 20:42, Nicolás escribió: >>> Hi all! >>> >>> I'm new to this list, I've been looking to get some info about this but >>> I haven't seen anything, so I'm trying this way. >>> >>> I've successfully configured a 2-node cluster with DRBD + Heartbeat + >>> Pacemaker. It works as expected. >>> >>> The problem comes when both nodes are down. Having this, after powering >>> on one of the nodes, I can see it configuring the network but after this >>> I never see the console for this machine. So I try to connect via SSH >>> and realize that Heartbeat is not running. After I run it manually I can >>> see the console for this node. This only happens when BOTH nodes are >>> down. When just one is, everything goes right as Heartbeat starts >>> automatically on the powering-on node. >>> >>> I see nothing relevant in logs, my conf is as follows: >>> >>> root@cluster1:~# cat /etc/ha.d/ha.cf | grep -e ^[^#] >>> logfacility local0 >>> ucast eth1 192.168.0.91 >>> ucast eth0 192.168.20.51 >>> auto_failback on >>> node cluster1.gamez.es cluster2.gamez.es >>> use_logd yes >>> crm on >>> autojoin none >>> >>> Any ideas on what am I doing wrong? > [...] > > For a new cluster use Corosync and not Heartbeat,disable DRBD init > script and configure it as a Pacemaker master-slave resource. >
Thanks for this! Once I disabled DRBD init script it worked as it should. Regards, Nicolás _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
