On 1/26/2012 8:12 PM, gustavo panizzo wrote:
crm_mon says it is starting mysqld on mysql01.
(I think it actually stopped and restarted mysqld on mysql01 but
haven't been able to verify yet. Seems gratuitous, but I can live
with that though.)
do not start clustered services from init
this is n
On 1/25/2012 11:29 PM, Florian Haas wrote:
Well if you just want to restart Corosync by administrative
intervention (i.e. in a planned, controlled fashion), then why not put
the cluster in maintenance mode before you restart Corosync? Cheers,
Florian
Good point. My concern was about whether th
On 1/26/12 5:25 AM, Dan Frincu wrote:
Hi,
On Thu, Jan 26, 2012 at 1:43 AM, Peter Scott wrote:
> Hello. Our problem is that a Corosync restart on the idle machine in a
> 2-node cluster shuts down the mysqld process there and we need it to stay
> up for replication. We are ve
Hello. Our problem is that a Corosync restart on the idle machine in a
2-node cluster shutds down the mysqld process there and we need it to
stay up for replication. We are very new to Corosync and Pacemaker and
have been slogging through every tutorial and document we can find.
Here's the d