Hi,
I know this kind of problem has been posted numerous times but my google-fu
doesn't seem to gather anything interesting and I'm really stuck.
I have this 2 node cluster with multiple drbd resources in active/passive mode
(only one primary allowed) and every time one primary drbd resource gets
Hi,
* christine caulfield [20191121 03:19]:
> On 18/11/2019 21:31, Jean-Francois Malouin wrote:
> > Hi,
> >
> > Maybe not directly a pacemaker question but maybe some of you have seen this
> > problem:
> >
> > A 2 node pacemaker cluster running corosync-
d one didn't do the job...
thanks,
jf
* Jean-Francois Malouin [20191118
16:31]:
> Hi,
>
> Maybe not directly a pacemaker question but maybe some of you have seen this
> problem:
>
> A 2 node pacemaker cluster running corosync-3.0.1 with dual communication ring
> som
Hi,
Maybe not directly a pacemaker question but maybe some of you have seen this
problem:
A 2 node pacemaker cluster running corosync-3.0.1 with dual communication ring
sometimes reports errors like this in the corosync log file:
[KNET ] pmtud: PMTUD link change for host: 2 link: 0 from 470 to
* Jean-Francois Malouin [20191029
09:49]:
> * Roger Zhou [20191029 06:18]:
> >
> > On 10/29/19 12:30 PM, Andrei Borzenkov wrote:
> > >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Activating volume
> > >> group vg0
> > >> Oct 28 14:4
* Roger Zhou [20191029 06:18]:
>
> On 10/29/19 12:30 PM, Andrei Borzenkov wrote:
> >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Activating volume group
> >> vg0
> >> Oct 28 14:42:56 node2 LVM(p_lvm_vg0)[8775]: INFO: Reading all physical
> >> volumes. This may take a while... Found volu
Hi,
Is there any new magic that I'm unaware of that needs to be added to a
pacemaker cluster using a DRBD nested setup? pacemaker 2.0.x and DRBD 8.4.10 on
Debian/Buster on a 2-node cluster with stonith.
Eventually this will host a bunch of Xen VMs.
I had this sort of thing running for years with
Regards,
> Strahil NikolovOn Oct 28, 2019 19:00, Jean-Francois Malouin
> wrote:
> >
> > Hi,
> >
> > Building a new pacemaker cluster using corosync 3.0 and pacemaker 2.0.1 on
> > Debian/Buster 10
> > I get this error when trying to insert a order const
* Andrei Borzenkov [20191028 13:14]:
> 28.10.2019 20:00, Jean-Francois Malouin пишет:
> > Hi,
> >
> > Building a new pacemaker cluster using corosync 3.0 and pacemaker 2.0.1 on
> > Debian/Buster 10
> > I get this error when trying to insert a order constraint
Hi,
Building a new pacemaker cluster using corosync 3.0 and pacemaker 2.0.1 on
Debian/Buster 10
I get this error when trying to insert a order constraint in the CIB to first
promote drbd to primary
then start/scan LVM. It used to work in previous versions of pacemaker so
I'm looking at the doc r
* Jean-Francois Malouin [20170607
13:09]:
> Hi,
..snip...
> I'm having some difficulties understanding the fencing_topology syntax.
> Making the changes adapted for my local configuration I get the error
> when trying to add the fence topology:
>
> ~# crm configure f
Hi,
Thanks for the info. More inline below.
* Marek Grac [20170607 04:10]:
> Hi,
>
> On Tue, Jun 6, 2017 at 3:52 PM, Jean-Francois Malouin <
> jean-francois.malo...@bic.mni.mcgill.ca> wrote:
>
> > Hi,
> >
> > Starting to configure a two-nodes cluste
Hi,
Starting to configure a two-nodes cluster, runnning Debian Jessie 8.8
Stack: corosync, pacemaker version 1.1.15-e174ec8.
I'm confused with the different fencing agents related to IMPI, it seems
that there are a few: external/ipmi, fence_ipmilan, ipmilan. Right now
I'm using external/ipmi whi
13 matches
Mail list logo
