- Original Message -
> From: "Julien Cornuwel"
> To: "The Pacemaker cluster resource manager"
> Sent: Wednesday, July 18, 2012 4:06:55 AM
> Subject: [Pacemaker] Trouble with ocf:Squid resource agent
>
> Hi,
>
> I'm setting up a proxy cluster on OpenSuSE 12.1. Squid starts OK on
> both
On 2012-07-18 15:57, Ulrich Leodolter wrote:
> hi,
>
> after adding a second ring to corosync.conf
> the problem seems to be gone.
>
> after killing corosync the node is fenced by
> the other node. after reboot the cluster is
> fully operational.
>
> is this essential to have at least 2 rings?
hi,
after adding a second ring to corosync.conf
the problem seems to be gone.
after killing corosync the node is fenced by
the other node. after reboot the cluster is
fully operational.
is this essential to have at least 2 rings?
maybe there is a network timing problem (but can't see
error mes
Our current monitor action tests the availability of the mysql database.
However, the monitor fails if mysql is doing recovery processing. And the
recovery processing can take a long time. Do you know if there is a way to
programmatically determine if mysql is in recovery mode (and is proc
Hi,
I'm setting up a proxy cluster on OpenSuSE 12.1. Squid starts OK on
both servers when called from the lsb script. I stopped it and here is
the configuration I set up :
# crm configure show
node corsen-a
node corsen-b
primitive Proxy ocf:heartbeat:Squid \
params squid_exe="/usr/sbin/sq
Hi!
I read here, that the crm documentation currently online is not very recent any
more.
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained
does not cover crm at all but instead explaines how the cib works internally
(does anyone here really modify the cib by hand???)