On 06/08/2016 11:21 AM, Ken Gaillot wrote:
> There's a big box at the top of every page on that wiki :)
I know. Somebody should tell google that a search for "pacemaker
resource agent" should return a link to "pacemaker explained for
pacemaker 1.1 and corosync 2.x" instead:
> http://clusterlabs.
Don't see any issues in network traffic.
Some more logs where the XML tags are incomplete:
2016-06-09T03:06:03.096449+05:30 d18-fb-7b-18-f1-8e
pacemaker_remoted[6153]:error: Partial
2016-06-09T03:06:03.097797+05:30 d18-fb-7b-18-f1-8e
pacemaker_remoted[6153]:error: Partial
2016-06-09T03:
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 corosyn
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 LSB
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 p
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 corosync.conf
If you use IPv
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 that
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
http://www.linux-ha.org/wiki/Resour
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 - SLES
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) pcsd cannot be used since (as
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 systemd-managed
Also below messages are seen in logs before self-fencing.
2016-06-08T14:11:46.124825+05:30 d18-fb-7b-18-f1-8e
pacemaker_remoted[6190]:error: crm_remote_header: Triggered assert at
remote.c:119 : endian == ENDIAN_LOCAL
2016-06-08T14:11:46.124924+05:30 d18-fb-7b-18-f1-8e
pacemaker_remoted[6190]:
Hi all,
for those interested in Galera, I'm pleased to announce that support
for garbd - the Galera arbitrator - has landed in resource-agents
repository.
The garbd RA is useful for managing a 2-nodes Galera cluster in pacemaker
with an additional node (or pacemaker_remote node) acting as an arbi
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) pcsd cannot be used since (as per my understanding) it communicates
>over
>ssh which is prevented.
As far as i
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 will
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 - pacemaker-remote-1.1.13-14.7.x86_
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 pr
Andrew Beekhof wrote:
> On Wed, Jun 8, 2016 at 12:11 AM, Adam Spiers wrote:
> > Ken Gaillot wrote:
> >> On 06/06/2016 05:45 PM, Adam Spiers wrote:
> >> > Adam Spiers wrote:
> >> >> Andrew Beekhof wrote:
> >> >>> On Tue, Jun 7, 2016 at 8:29 AM, Adam Spiers wrote:
> >> Ken Gaillot wrote:
18 matches
Mail list logo
