Re: [ClusterLabs] Alert notes

2016-06-16 Thread Ferenc Wágner
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

Re: [ClusterLabs] Alert notes

2016-06-16 Thread Klaus Wenninger
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: >>> >>> >>

[ClusterLabs] Corosync 2.3.6 is available at corosync.org!

2016-06-16 Thread Jan Friesse
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

Re: [ClusterLabs] Corosync 2.3.6 is available at corosync.org!

2016-06-16 Thread Vladislav Bogdanov
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

Re: [ClusterLabs] Corosync 2.3.6 is available at corosync.org!

2016-06-16 Thread Christine Caulfield
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 (

Re: [ClusterLabs] Alert notes

2016-06-16 Thread Ferenc Wágner
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

Re: [ClusterLabs] Corosync 2.3.6 is available at corosync.org!

2016-06-16 Thread Vladislav Bogdanov
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/

Re: [ClusterLabs] Corosync 2.3.6 is available at corosync.org!

2016-06-16 Thread Christine Caulfield
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

Re: [ClusterLabs] Corosync 2.3.6 is available at corosync.org!

2016-06-16 Thread Christine Caulfield
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

Re: [ClusterLabs] Corosync 2.3.6 is available at corosync.org!

2016-06-16 Thread Vladislav Bogdanov
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

Re: [ClusterLabs] Corosync 2.3.6 is available at corosync.org!

2016-06-16 Thread Christine Caulfield
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: >

[ClusterLabs] Corosync with passive rrp, udpu - Unable to reset after "Marking ringid 1 interface 127.0.0.1 FAULTY"

2016-06-16 Thread Martin Schlegel
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 (

Re: [ClusterLabs] Corosync with passive rrp, udpu - Unable to reset after "Marking ringid 1 interface 127.0.0.1 FAULTY"

2016-06-16 Thread Jan Friesse
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

Re: [ClusterLabs] Corosync with passive rrp, udpu - Unable to reset after "Marking ringid 1 interface 127.0.0.1 FAULTY"

2016-06-16 Thread Martin Schlegel
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