On 01/15/2016 11:08 AM, Ken Gaillot wrote:
>> Jan 13 19:33:00 [4291] oranacib: info:
>> cib_process_replace: Replacement 0.4.0 from kamet not applied to
>> 0.74.1: current epoch is greater than the replacement
>> Jan 13 19:33:00 [4291] oranacib: warning:
>> cib_process_request
On 01/15/2016 05:02 AM, Arjun Pandey wrote:
> Based on corosync logs from orana ( The node that did the actual
> fencing and is the current master node)
>
> I also tried looking at pengine outputs based on crm_simulate. Uptil
> the fenced node rejoins things look good.
>
> [root@ucc1 orana]# cr
Hi everyone,
In June of last year, I released Release Candidate 3 of crmsh 2.2.0,
and I honestly expected to have the final version ready no more than a
few weeks later. Well, it took around 6 months, but now it is finally
here!
The source code can be downloaded from Github:
* https://github.com
Hi,
On Fri, Jan 15, 2016 at 04:54:37PM +0900, yuta takeshita wrote:
> Hi,
>
> Tanks for responding and making a patch.
>
> 2016-01-14 19:16 GMT+09:00 Dejan Muhamedagic :
>
> > On Thu, Jan 14, 2016 at 11:04:09AM +0100, Dejan Muhamedagic wrote:
> > > Hi,
> > >
> > > On Thu, Jan 14, 2016 at 04:20:
On 2015-10-08 21:20, Ken Gaillot wrote:
On 10/08/2015 10:16 AM, priyanka wrote:
Hi,
We are trying to build a HA setup for our servers using DRBD +
Corosync
+ pacemaker stack.
Attached is the configuration file for corosync/pacemaker and drbd.
A few things I noticed:
* Don't set become-pri
On 2015-10-08 21:05, Digimer wrote:
On 08/10/15 11:16 AM, priyanka wrote:
fencing resource-only;
This needs to be 'fencing resource-and-stonith;'.
I did set the suggested parameter but error persists. Apparently node
which comes back after fail-over is not able to detect res_e
On 2015-10-08 20:52, emmanuel segura wrote:
please check if you drbd is configured to call fence-handler
https://drbd.linbit.com/users-guide/s-pacemaker-fencing.html
yes.
2015-10-08 17:16 GMT+02:00 priyanka :
Hi,
We are trying to build a HA setup for our servers using DRBD +
Corosync +
pa
Based on corosync logs from orana ( The node that did the actual
fencing and is the current master node)
I also tried looking at pengine outputs based on crm_simulate. Uptil
the fenced node rejoins things look good.
[root@ucc1 orana]# crm_simulate -S --xml-file
./pengine/pe-input-1450.bz2 -u k
