Re: [ClusterLabs] Access denied when using Floating IP

2017-01-06 Thread Erick Ocrospoma
On 6 January 2017 at 14:37, Ken Gaillot wrote: > On 12/26/2016 12:03 AM, Kaushal Shriyan wrote: > > Hi, > > > > I have set up Highly Available HAProxy Servers with Keepalived and > > Floating IP. I have the below details > > > > *Master Node keepalived.conf* > > > >

Re: [ClusterLabs] Status and help with pgsql RA

2017-01-06 Thread Jehan-Guillaume de Rorthais
On Fri, 6 Jan 2017 13:47:34 -0600 Ken Gaillot wrote: > On 12/28/2016 02:24 PM, Nils Carlson wrote: > > Hi, > > > > I am looking to set up postgresql in high-availability and have been > > comparing the guide at > > http://wiki.clusterlabs.org/wiki/PgSQL_Replicated_Cluster

Re: [ClusterLabs] centos 7 drbd fubar

2017-01-06 Thread Dimitri Maziuk
On 01/06/2017 01:41 PM, Ken Gaillot wrote: > That is disconcerting. Since no one here seems to know, have you tried > asking on the drbd list? It sounds like an issue with the drbd kernel > module. AFAIK at least a couple of linbit people are on this list too. I have another pair that fails

Re: [ClusterLabs] Status and help with pgsql RA

2017-01-06 Thread Ken Gaillot
On 12/28/2016 02:24 PM, Nils Carlson wrote: > Hi, > > I am looking to set up postgresql in high-availability and have been > comparing the guide at > http://wiki.clusterlabs.org/wiki/PgSQL_Replicated_Cluster with the > contents of the pgsql resource agent on github. It seems that there have >

Re: [ClusterLabs] centos 7 drbd fubar

2017-01-06 Thread Ken Gaillot
On 12/27/2016 03:08 PM, Dimitri Maziuk wrote: > I ran centos 7.3.1611 update over the holidays and my drbd + nfs + imap > active-passive pair locked up again. This has now been consistent for at > least 3 kernel updates. This time I had enough consoles open to run > fuser & lsof though. > > The

Re: [ClusterLabs] Access denied when using Floating IP

2017-01-06 Thread Ken Gaillot
On 12/26/2016 12:03 AM, Kaushal Shriyan wrote: > Hi, > > I have set up Highly Available HAProxy Servers with Keepalived and > Floating IP. I have the below details > > *Master Node keepalived.conf* > > global_defs { > # Keepalived process identifier > #lvs_id haproxy_DH > } > # Script used to

Re: [ClusterLabs] Galera 10.1 cluster

2017-01-06 Thread Oscar Segarra
Hi, I get errors like the following: 017-01-06 11:25:47 139902389713152 [ERROR] WSREP: failed to open gcomm backend connection: 131: invalid UUID: (FATAL) at gcomm/src/pc.cpp:PC():267 2017-01-06 11:25:47 139902389713152 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():208:

Re: [ClusterLabs] Galera 10.1 cluster

2017-01-06 Thread Oscar Segarra
Hi, In my environment I'm not able to bootstrap the cluster after a crash and I thought it could be a configuration problem at cluster level and I wanted to know if anybody has been able to configure it. Thanks a lot. 2017-01-06 9:34 GMT+01:00 Damien Ciabrini : > Hey

Re: [ClusterLabs] Galera 10.1 cluster

2017-01-06 Thread Damien Ciabrini
Hey Oscar, - Original Message - > Hi, > > Anybody has been able to set up a Galera cluster with the latest available > version of Galera? > > Can anybody paste the configuration? > > I have tested it but I have not been able to make it run resiliently. > Can you be more specific on