On Fri, Apr 18, 2008 at 6:56 PM, Luis Motta Campos
<[EMAIL PROTECTED]> wrote:
> Hoy, HA people.
>
> Little help here, please.
>
> I have two HA Clusters, which I call "Master" and "Slave".
>
> I've been through a lot of trouble with an older version of heartbeat,
> as you may remember from my previous posts in the list.
>
> Now, I'm using
>
> heartbeat.x86_64 2.1.3-21.1
> heartbeat-common.x86_64 2.1.3-21.1
> heartbeat-resources.x86_64 2.1.3-21.1
> pacemaker-heartbeat.x86_64 0.6.2-14.1
>
> I have two different clusters, each one with almost the same
> configuration. I call them "Master" and "Slave" (because they run my
> database replication master and slave, respectively). Please find both
> CIB configurations attached (master.xml, slave.xml).
>
> I have a strange behaviour: on Master, resources do stick to the
> current host, as requested; on Slave, doesn't matter what I do,
> resources do *not* stick. It's driving me crazy, and must be something
> quite simple.
They're not going to stay on db-sql2.ripe.net because you're also
telling them that they _must_ be running with the master drbd instance
(which is running on db-sql4.ripe.net).
>
> Please find the hb_report run for both the Slave Cluster machines,
> with the last attempt to make the resources "jump" to a healthy machine
> and stay there when the initial host recover from failure.
>
> I was simulating server crashes with "service heartbeat restart",
> maybe that's not the best option, but it works for the Master Cluster.
>
> Many many thanks in advance for any help you can give me.
> Kindest regards.
> --
> Luis Motta Campos (a.k.a. Monsieur Champs) is a software engineer,
> Perl fanatic evangelist, and amateur {cook, photographer}
>
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
