Re: [ClusterLabs] Reliability questions on the new QDevices in uneven node count Setups

On 25/07/16 16:27, Klaus Wenninger wrote: > On 07/25/2016 04:56 PM, Thomas Lamprecht wrote: >> Thanks for the fast reply :) >> >> >> On 07/25/2016 03:51 PM, Christine Caulfield wrote: >>> On 25/07/16 14:29, Thomas Lamprecht wrote: >>>> Hi all,

Re: [ClusterLabs] Reliability questions on the new QDevices in uneven node count Setups

On 25/07/16 14:51, Christine Caulfield wrote: > On 25/07/16 14:29, Thomas Lamprecht wrote: >> Hi all, >> >> I'm currently testing the new features of corosync 2.4, especially >> qdevices. >> First tests show quite nice results, like having quorum on a single

Re: [ClusterLabs] Reliability questions on the new QDevices in uneven node count Setups

On 25/07/16 14:29, Thomas Lamprecht wrote: > Hi all, > > I'm currently testing the new features of corosync 2.4, especially > qdevices. > First tests show quite nice results, like having quorum on a single node > left out of a three node cluster. > > But what I'm a bit worrying about is what

Re: [ClusterLabs] Antw: Re: corosync just listening on 127.0.0.1

On 04/07/16 10:35, Christine Caulfield wrote: > On 04/07/16 10:28, Ulrich Windl wrote: >>>>> Christine Caulfield <ccaul...@redhat.com> schrieb am 04.07.2016 um 09:26 >>>>> in >> Nachricht <577a0f98.5020...@redha

Re: [ClusterLabs] corosync just listening on 127.0.0.1

On 01/07/16 18:31, Lentes, Bernd wrote: > Hi, > > i'm currently establishing a two-node cluster and i'm playing around with it. > I have two nodes, both have a bond-device. It is intended for DRBD, MySQL > replication and the inter-cluster-communication. > Each bond has a private IP-address

Re: [ClusterLabs] DLM standalone without crm ?

On 27/06/16 15:27, Lentes, Bernd wrote: > > - Am 27. Jun 2016 um 9:04 schrieb Christine Caulfield ccaul...@redhat.com: > >> On 26/06/16 14:47, Lentes, Bernd wrote: >>> >>> >>> - Am 26. Jun 2016 um 7:59 schrieb Ferenc Wágner wf...@niif.hu: >&g

Re: [ClusterLabs] DLM standalone without crm ?

On 26/06/16 14:47, Lentes, Bernd wrote: > > > - Am 26. Jun 2016 um 7:59 schrieb Ferenc Wágner wf...@niif.hu: > >> "Lentes, Bernd" writes: >> >>> wf...@niif.hu writes: >>> "Lentes, Bernd" writes: > is it

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

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, &g

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

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 rele

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

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 rele

[ClusterLabs] [Announce] libqb 1.0 release

I am very pleased to announce the 1.0 release of libqb This release is identical to 1.0rc4 but with the doxygen generation fixed. Huge thanks you to all of the people who have contributed to this release. Chrissie The current release tarball is here:

[ClusterLabs] [Announce] libqb 10.rc4 release

This is a bugfix release and a potential 1.0 candidate. There are no actual code changes in this release, most of the patches are to the build system. Thanks to Jan Pokorný for, er, all of them. I've bumped the library soname to 0.18.0 which should really have happened last time. Changes from

Re: [ClusterLabs] [Announce] libqb 10.rc3 release

On 26/02/16 07:58, Jan Pokorný wrote: > On 26/02/16 14:27 +0900, Keisuke MORI wrote: >> As of libqb-1.0rc3, Pacemaker fails to build upon it with the gcc >> warnings as below. >> There was no such a problem until 1.0rc2, and it seems that the >> changes in the pull request #175 is related. >> >>

[ClusterLabs] [Announce] libqb 10.rc3 release

I am pleased to announce the third 1.0 release candidate release of libqb. Huge thanks to all those who have contributed to this release. There are a couple of tiny things to tidy up before 1.0 so I'm going to try and close the release off by the end of next week (5th march) unless anything

Re: [ClusterLabs] [Announce] libqb 1.0rc2 release (fixed subject)

On 03/02/16 17:45, Jan Pokorný wrote: > On 02/02/16 11:05 +0000, Christine Caulfield wrote: >> I am pleased to announce the second 1.0 release candidate release of >> libqb. Huge thanks to all those who have contributed to this release. > > IIUIC, good news is that s

[ClusterLabs] [Announce] libqb 10.rc2 release

I am pleased to announce the second 1.0 release candidate release of libqb. Huge thanks to all those who have contributed to this release. This is a bugfix release and I hope to work towards a full 1.0 release in late February or early March depending on feedback. Changes from 1.0rc2 are mainly

[ClusterLabs] [Announce] libqb 10.rc1 release

I am pleased to announce the 1.0rc1 release of libqb This is a bugfix release and I hope to work towards a full 1.0 release in February or March depending on feedback. Changes from 0.17.2 Improvements to build process includes: Fix format string for C++11 ipc: Prevent fd and memory

Re: [ClusterLabs] Anyone successfully install Pacemaker/Corosync on Freebsd?

On 21/12/15 16:12, Ken Gaillot wrote: > On 12/19/2015 04:56 PM, mike wrote: >> Hi All, >> >> just curious if anyone has had any luck at one point installing >> Pacemaker and Corosync on FreeBSD. I have to install from source of >> course and I've run into an issue when running ./configure while

Re: [ClusterLabs] required nodes for quorum policy

On 09/11/15 22:20, Radoslaw Garbacz wrote: > Hi, > > I have a question regarding the policy to check for cluster quorum for > corosync+pacemaker. > > As far as I know at present it is always (excpected_votes)/2 + 1. Seems > like "qdiskd" has an option to change it, but it is not clear to me if >

Re: [ClusterLabs] Wireshark dissector for corosync/totem packes.

On 20/10/15 21:20, Vallevand, Mark K wrote: > OK, I guess that the data is encrypted in the corosync/token packet. > IIRC you can tell wireshark what the encryption key is and it will decrypt the packets for you. later: https://github.com/masatake/wireshark-plugin-rhcs Chrissie > >

Re: [ClusterLabs] Odd clvmd error - clvmd: Unable to create DLM lockspace for CLVM: Address already in use

On 25/09/15 00:09, Digimer wrote: > I had a RHEL 6.7, cman + rgmanager cluster that I've built many times > before. Oddly, I just hit this error: > > > [root@node2 ~]# /etc/init.d/clvmd start > Starting clvmd: clvmd could not connect to cluster manager > Consult syslog for more information >

Re: [ClusterLabs] EL6, cman, rrp, unicast and iptables

On 15/09/15 01:01, Digimer wrote: > On 14/09/15 10:46 AM, Noel Kuntze wrote: >> >> Hello Christine, >> >> I googled a bit and some doc[1] says that TC_PRIO_INTERACTIVE maps to value >> 6, whatever that is. >> Assuming that value of 6 is the same as the "priority value", Corosync >> traffic

Re: [ClusterLabs] EL6, cman, rrp, unicast and iptables

On 14/09/15 12:45, Noel Kuntze wrote: > > Hello Christine, > >> I think it's worth mentioning here that corosync already sets its >> packets to TC_INTERACTIVE (which DLM does not), so they should not need >> too much messing around with in iptables/qdisc > > If that is the case, then why do the

Re: [ClusterLabs] Cluster.conf

On 25/08/15 14:14, Streeter, Michelle N wrote: I am using pcs but it does nothing with the cluster.conf file. Also, I am currently required to use rhel6.6. I have not been able to find any documentation on what is required in the cluster.conf file under the newer versions of pacemaker

[ClusterLabs] [Announce] libqb v0.17.2 release

This is mainly a bug fix release, but also includes a new split-logging feature. Changes v0.17.1 - v0.17.2 Implement extended information logging (aka split logging) switch libtool soname versioning from -version-number to -version-info High: loop: fixes resource starvation in

<    1   2