On Fri, 12 Oct 2012 09:22:13 +0200 Florian Haas
wrote:
> For most people, this issue doesn't occur on system boot, as libvirtd
> would normally start before corosync, or corosync/pacemaker isn't part
> of the system bootup sequence at all (the latter is preferred for
> two-node clusters to prevent
Hello,
I have two nodes set up in a cluster to provide a MySQL server (mysqld)
in HA on a virtual IP address. This was working fine until I had to
reboot the servers. All I did was change the interface each node uses
for its primary IP address (changed from eth1 to eth0 on each node).
Now
Hi Andrew,
Thanks, I'll compile Pacemaker 1.1.8 and Corosync 1.4.4. Can I leave
cluster-glue and resource-agents at the default versions provided with Ubuntu
12.04 (1.0.8 and 3.9.2 respectively), or do I need to upgrade them as well?
Andrew
- Original Message -
From: "Andrew Beek
On Fri, Oct 12, 2012 at 3:18 AM, Andrew Beekhof wrote:
> This has been a topic that has popped up occasionally over the years.
> Unfortunately we still don't have a good answer for you.
>
> The "least worst" practice has been to have the RA return OCF_STOPPED
> for non-recurring monitor operations
