Re: [ClusterLabs] Different pacemaker versions split cluster

On 06/07/2016 02:26 PM, DacioMF wrote: > Ken, > > I clear all logs in /var/log/corosync and reboot the cluster (this is the > test environment, but i want to upgrade the production). > > I attach the output of the command crm_report --from "2016-06-07 0:0:0" after > the reboot. > > The

Re: [ClusterLabs] dovecot RA

On 06/08/2016 09:11 AM, Ken Gaillot wrote: > On 06/08/2016 03:26 AM, Jan Pokorný wrote: >> On 07/06/16 14:48 -0500, Dimitri Maziuk wrote: >>> next question: I'm on centos 7 and there's no more /etc/init.d/>> anything>. With lennartware spreading, is there a coherent plan to deal >>> with former

Re: [ClusterLabs] pacemaker_remoted XML parse error

No recent network changes. Will check for abnormal traffic using wireshark. I also notice that the XML lines are partial (no ending '>', closing " and sometimes partial words) in logs. Any lines > 472 characters are truncated to 472 characters. Wondering is it due to anyother limitations. I can

Re: [ClusterLabs] Minimum configuration for dynamically adding a node to a cluster

Nikhil Utane writes: > Would like to know the best and easiest way to add a new node to an already > running cluster. > > Our limitation: > 1) pcsd cannot be used since (as per my understanding) it communicates over > ssh which is prevented. > 2) No manual editing of

Re: [ClusterLabs] dovecot RA

On 06/08/2016 10:11 AM, Dmitri Maziuk wrote: > On 2016-06-08 09:11, Ken Gaillot wrote: >> On 06/08/2016 03:26 AM, Jan Pokorný wrote: > >>> Pacemaker can drive systemd-managed services for quite some time. >> >> This is as easy as changing lsb:dovecot to systemd:dovecot. > > Great! Any chance

Re: [ClusterLabs] dovecot RA

On 2016-06-08 09:11, Ken Gaillot wrote: On 06/08/2016 03:26 AM, Jan Pokorný wrote: Pacemaker can drive systemd-managed services for quite some time. This is as easy as changing lsb:dovecot to systemd:dovecot. Great! Any chance that could be mentioned on

Re: [ClusterLabs] pacemaker_remoted XML parse error

On 06/08/2016 06:14 AM, Narayanamoorthy Srinivasan wrote: > I have a pacemaker cluster with two pacemaker remote nodes. Recently the > remote nodes started throwing below errors and SDB started self-fencing. > Appreciate if someone throws light on what could be the issue and the fix. > > OS -

Re: [ClusterLabs] Minimum configuration for dynamically adding a node to a cluster

On 06/08/2016 06:54 AM, Jehan-Guillaume de Rorthais wrote: > > > Le 8 juin 2016 13:36:03 GMT+02:00, Nikhil Utane > a écrit : >> Hi, >> >> Would like to know the best and easiest way to add a new node to an >> already >> running cluster. >> >> Our limitation: >> 1)

Re: [ClusterLabs] dovecot RA

On 06/08/2016 03:26 AM, Jan Pokorný wrote: > On 07/06/16 14:48 -0500, Dimitri Maziuk wrote: >> next question: I'm on centos 7 and there's no more /etc/init.d/> anything>. With lennartware spreading, is there a coherent plan to deal >> with former LSB agents? > > Pacemaker can drive

[ClusterLabs] Minimum configuration for dynamically adding a node to a cluster

Hi, Would like to know the best and easiest way to add a new node to an already running cluster. Our limitation: 1) pcsd cannot be used since (as per my understanding) it communicates over ssh which is prevented. 2) No manual editing of corosync.conf So what I am thinking is, the first node

[ClusterLabs] pacemaker_remoted XML parse error

I have a pacemaker cluster with two pacemaker remote nodes. Recently the remote nodes started throwing below errors and SDB started self-fencing. Appreciate if someone throws light on what could be the issue and the fix. OS - SLES 12 SP1 Pacemaker Remote version -

Re: [ClusterLabs] dovecot RA

On 07/06/16 14:48 -0500, Dimitri Maziuk wrote: > next question: I'm on centos 7 and there's no more /etc/init.d/ anything>. With lennartware spreading, is there a coherent plan to deal > with former LSB agents? Pacemaker can drive systemd-managed services for quite some time. Provided that the