Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the "--with-corosync". How is Corosync looking for his own version? Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com

[ClusterLabs] corosync.log is 5.1GB in a short period

Hello: I has a problem about corosync log, my corosync log is increase to 5.1GB in a short time. Then I check the corosync log, it’s show me the same message in short period,like the attachment. What happened about corosync? Thank you! my corosync and pacemaker is:corosync-2.3.4-7.el7.x86_64

Re: [ClusterLabs] Which cluster HA package to choose

On 22/08/16 11:40 AM, Ron Gilad wrote: > Hi, > > I have encountered with several cluster High Availability packages: > > - Pacemaker + Corosync > > - Red Hat Enterprise Linux Cluster > > Which package do you think is the best to choose? > > Do you know if the latest ver is

Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

On 08/23/2016 12:20 AM, Ken Gaillot wrote: > On 08/22/2016 12:17 PM, Gabriele Bulfon wrote: >> Hi, >> >> I built corosync/pacemaker for our XStreamOS/illumos : corosync starts >> fine and log correctly, pacemakerd quits after some seconds with the >> attached log. >> Any idea where is the issue? >

[ClusterLabs] Which cluster HA package to choose

Hi, I have encountered with several cluster High Availability packages: - Pacemaker + Corosync - Red Hat Enterprise Linux Cluster Which package do you think is the best to choose? Do you know if the latest ver is stable? And which companies are using it? Thanks in advance, Ron

Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

On 08/22/2016 12:17 PM, Gabriele Bulfon wrote: > Hi, > > I built corosync/pacemaker for our XStreamOS/illumos : corosync starts > fine and log correctly, pacemakerd quits after some seconds with the > attached log. > Any idea where is the issue? Pacemaker is not able to communicate with corosync

[ClusterLabs] pacemakerd quits after few seconds with some errors

Hi, I built corosync/pacemaker for our XStreamOS/illumos : corosync starts fine and log correctly, pacemakerd quits after some seconds with the attached log. Any idea where is the issue? Thanks, Gabriele

Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

On 08/22/2016 07:24 AM, Attila Megyeri wrote: > Hi Andrei, > > I waited several hours, and nothing happened. And actually, we can see from the configuration you provided that cluster-recheck-interval is 2 minutes. I don't see anything about stonith; is it enabled and tested? This looks like a

Re: [ClusterLabs] Entire Group stop on stopping of single Resource

On 19/08/16 23:09 +0530, jaspal singla wrote: > I have an resource group (ctm_service) comprise of various resources. Now > the requirement is when one of its resource stops for soem time (10-20) > seconds, I want entire group will be stopped. Note that if resource is stopped _just_ for this

Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

Hi Andrei, I waited several hours, and nothing happened. I assume that the RA does not treat this case properly. Mysql was running, but the "show slave status" command returned something that the RA was not prepared to parse, and instead of reporting a non-readable attribute, it returned some

Re: [ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

On Mon, Aug 22, 2016 at 12:18 PM, Attila Megyeri wrote: > Dear community, > > > > A few days ago we had an issue in our Mysql M/S replication cluster. > > We have a one R/W Master, and a one RO Slave setup. RO VIP is supposed to be > running on the slave if it is not

[ClusterLabs] Mysql slave did not start replication after failure, and read-only IP also remained active on the much outdated slave

Dear community, A few days ago we had an issue in our Mysql M/S replication cluster. We have a one R/W Master, and a one RO Slave setup. RO VIP is supposed to be running on the slave if it is not too much behind the master, and if any error occurs, RO VIP is moved to the master. Something