Klaus Wenninger writes:
> On 06/15/2016 06:11 PM, Ferenc Wágner wrote:
>
>> Please find some random notes about my adventures testing the new alert
>> system.
>>
>> The first alert example in the documentation has no recipient:
>>
>>
>>
>> In the example above, the cluster will call my-s
On 06/16/2016 11:05 AM, Ferenc Wágner wrote:
> Klaus Wenninger writes:
>
>> On 06/15/2016 06:11 PM, Ferenc Wágner wrote:
>>
>>> Please find some random notes about my adventures testing the new alert
>>> system.
>>>
>>> The first alert example in the documentation has no recipient:
>>>
>>>
>>
I am pleased to announce the latest maintenance release of Corosync
2.3.6 available immediately from our website at
http://build.clusterlabs.org/corosync/releases/.
This release contains mostly fixes of known bugs.
Also please note that this is last version without qdevice. Qdevice is
complete
Hi,
16.06.2016 14:09, Jan Friesse wrote:
I am pleased to announce the latest maintenance release of Corosync
2.3.6 available immediately from our website at
http://build.clusterlabs.org/corosync/releases/.
[...]
Christine Caulfield (9):
[...]
Add some more RO keys
Is there a strong
On 16/06/16 13:22, Vladislav Bogdanov wrote:
> Hi,
>
> 16.06.2016 14:09, Jan Friesse wrote:
>> I am pleased to announce the latest maintenance release of Corosync
>> 2.3.6 available immediately from our website at
>> http://build.clusterlabs.org/corosync/releases/.
> [...]
>> Christine Caulfield (
Klaus Wenninger writes:
> On 06/16/2016 11:05 AM, Ferenc Wágner wrote:
>
>> Klaus Wenninger writes:
>>
>>> On 06/15/2016 06:11 PM, Ferenc Wágner wrote:
>>>
I think the default timestamp should contain date and time zone
specification to make it unambigous.
>>>
>>> Idea was to have a tr
16.06.2016 15:28, Christine Caulfield wrote:
On 16/06/16 13:22, Vladislav Bogdanov wrote:
Hi,
16.06.2016 14:09, Jan Friesse wrote:
I am pleased to announce the latest maintenance release of Corosync
2.3.6 available immediately from our website at
http://build.clusterlabs.org/corosync/releases/
On 16/06/16 13:54, Vladislav Bogdanov wrote:
> 16.06.2016 15:28, Christine Caulfield wrote:
>> On 16/06/16 13:22, Vladislav Bogdanov wrote:
>>> Hi,
>>>
>>> 16.06.2016 14:09, Jan Friesse wrote:
I am pleased to announce the latest maintenance release of Corosync
2.3.6 available immediately
On 16/06/16 13:54, Vladislav Bogdanov wrote:
> 16.06.2016 15:28, Christine Caulfield wrote:
>> On 16/06/16 13:22, Vladislav Bogdanov wrote:
>>> Hi,
>>>
>>> 16.06.2016 14:09, Jan Friesse wrote:
I am pleased to announce the latest maintenance release of Corosync
2.3.6 available immediately
16.06.2016 16:04, Christine Caulfield wrote:
On 16/06/16 13:54, Vladislav Bogdanov wrote:
16.06.2016 15:28, Christine Caulfield wrote:
On 16/06/16 13:22, Vladislav Bogdanov wrote:
Hi,
16.06.2016 14:09, Jan Friesse wrote:
I am pleased to announce the latest maintenance release of Corosync
2.3
On 16/06/16 14:09, Vladislav Bogdanov wrote:
> 16.06.2016 16:04, Christine Caulfield wrote:
>> On 16/06/16 13:54, Vladislav Bogdanov wrote:
>>> 16.06.2016 15:28, Christine Caulfield wrote:
On 16/06/16 13:22, Vladislav Bogdanov wrote:
> Hi,
>
> 16.06.2016 14:09, Jan Friesse wrote:
>
Hello everyone,
we run a 3 node Pacemaker (1.1.14) / Corosync (2.3.5) cluster for a couple of
months successfully and we have started seeing a faulty ring with unexpected
127.0.0.1 binding that we cannot reset via "corosync-cfgtool -r".
We have had this once before and only restarting Corosync (
Martin Schlegel napsal(a):
Hello everyone,
we run a 3 node Pacemaker (1.1.14) / Corosync (2.3.5) cluster for a couple of
months successfully and we have started seeing a faulty ring with unexpected
127.0.0.1 binding that we cannot reset via "corosync-cfgtool -r".
This is problem. Bind to 127
Hi Jan
Thanks for your super quick response !
We do not use a Network Manager - it's all static on these Ubuntu 14.04 nodes
(/etc/network/interfaces).
I do not think we did an ifdown on the network interface manually. However, the
IP-Addresses are assigned to bond0 and bond1 - we use 4x physica
14 matches
Mail list logo