[ClusterLabs] [Announce] clufter-0.50.0 released

I am happy to announce that clufter-0.50.0, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key): https://people.redhat.com/jpokorny/pkgs/clufter/clufter-0.50.0.tar.gz

Re: [ClusterLabs] Antw: Re: Antw: Delayed first monitoring

On 13/08/15 10:38 +0200, Ulrich Windl wrote: Miloš Kozák milos.ko...@lejmr.com schrieb am 13.08.2015 um 09:56 in Nachricht 55cc4daa.4020...@lejmr.com: Dne 13.8.2015 v 09:26 Andrei Borzenkov napsal(a): On Thu, Aug 13, 2015 at 10:01 AM, Miloš Kozák milos.ko...@lejmr.com wrote: However,

Re: [ClusterLabs] Cluster.conf

On 24/08/15 17:52 +, Streeter, Michelle N wrote: If I have a cluster.conf file in /etc/cluster, my cluster will not start. Pacemaker 1.1.11, Corosync 1.4.7, cman 3.0.12, But if I do not have a cluster.conf file then my cluster does start with my current configuration. I don't think

Re: [ClusterLabs] [ClusterLabs Developers] Resource Agent language discussion

Hello, [adding users list as I think there's an overlap] On 07/08/15 12:09 +0200, Jehan-Guillaume de Rorthais wrote: Now, I would like to discuss about the language used to write a RA in Pacemaker. I never seen discussion or page about this so far. it wasn't in such a heretic :) tone, but I

Re: [ClusterLabs] Single quotes in values for 'crm resource rsc param set'

On 14/08/15 18:22 +0300, Vladislav Bogdanov wrote: I need to pass a command-line with semicolons in one of parameters which is run with eval in the resource agent. Backslashed double-quoting does not work in this case, but single-quotes work fine. Hmm, another data point to the recent shell

Re: [ClusterLabs] starting of resources

On 11/08/15 09:14 -0500, Ken Gaillot wrote: On 08/11/2015 02:12 AM, Vijay Partha wrote: After you start pacemaker and then type pcs status, we get the output that there are nodes online and the list of resources are empty. We then add resources to the nodes. Now what i want is after starting

Re: [ClusterLabs] [Question] About deletion of SysVStartPriority.

On 06/08/15 15:42 +0900, renayama19661...@ybb.ne.jp wrote: We have a question for the next correction.  * https://github.com/ClusterLabs/pacemaker/commit/a97c28d75347aa7be76092aa22459f0f56a220ff We understand it that this obeyed a correction of systemd. In Pacemaker1.1.13,

[ClusterLabs] [Announce] clufter-0.50.1 released

I am happy to announce that clufter-0.50.1, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key): https://people.redhat.com/jpokorny/pkgs/clufter/clufter-0.50.1.tar.gz

Re: [ClusterLabs] VIP monitoring failing with Timed Out error

On 29/10/15 15:27 +0530, Pritam Kharat wrote: > When I ran ocf-tester to test IPaddr2 agent > > ocf-tester -n sc_vip -o ip=192.168.20.188 -o cidr_netmask=24 -o nic=eth0 > /usr/lib/ocf/resource.d/heartbeat/IPaddr2 > > I got this error - ERROR: Setup problem: couldn't find command: ip > in

Re: [ClusterLabs] VIP monitoring failing with Timed Out error

On 29/10/15 14:10 +0100, Jan Pokorný wrote: > On 29/10/15 15:27 +0530, Pritam Kharat wrote: >> When I ran ocf-tester to test IPaddr2 agent >> >> ocf-tester -n sc_vip -o ip=192.168.20.188 -o cidr_netmask=24 -o nic=eth0 >> /usr/lib/ocf/resource.d/heartbeat/IPaddr2 >

Re: [ClusterLabs] multiple action= lines sent to STDIN of fencing agents - why?

On 15/10/15 12:25 +0100, Adam Spiers wrote: > I inserted some debugging into fencing.py and found that stonithd > sends stuff like this to STDIN of the fencing agents it forks: > > action=list > param1=value1 > param2=value2 > param3=value3 > action=list > > where paramX and

Re: [ClusterLabs] Automatic IPC buffer adjustment in Pacemaker 1.1.11?

On 19/10/15 18:40 +0200, Ferenc Wagner wrote: > The http://www.ultrabug.fr/tuning-pacemaker-for-large-clusters/ blog > post states that "Pacemaker v1.1.11 should come with a feature which > will allow the IPC layer to adjust the PCMK_ipc_buffer automagically". > However, I failed to identify this

Re: [ClusterLabs] OCF Pound

On 20/10/15 11:25 -0400, Tim Bourne wrote: > I recently installed a cluster (2 nodes) that is pretty simple. It > just has a few IP addresses and an instance of Pound. I was having > issues getting pound to start correctly. The error I received was: > > ERROR:

Re: [ClusterLabs] Fencing questions.

On 19/10/15 10:51 -0400, Digimer wrote: > On 19/10/15 06:53 AM, Arjun Pandey wrote: >> 2. Fencing test cases. >> Based on the internet queries i could find , apart from plugging out >> the dedicated cable. The only other case suggested is killing corosync >> process on one of the nodes. >> Are

Re: [ClusterLabs] Cluster node loss detection.

On 16/10/15 12:51 -0400, Digimer wrote: > On 16/10/15 12:37 PM, Vallevand, Mark K wrote: >> So, it looks like setting the corosync parameters in cluster.conf >> has some effect. Cman seems to pass them to corosync. > > Yes, never configure corosync directly when using cman, only use >

[ClusterLabs] [Announce] clufter-0.50.5 released

I am happy to announce that clufter-0.50.5, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] Antw: crm_report consumes all available RAM

On 06/10/15 10:28 +0200, Dejan Muhamedagic wrote: > On Mon, Oct 05, 2015 at 07:00:18PM +0300, Vladislav Bogdanov wrote: >> 14.09.2015 02:31, Andrew Beekhof wrote: >>> On 8 Sep 2015, at 10:18 pm, Ulrich Windl wrote: >>> Vladislav Bogdanov

Re: [ClusterLabs] will rgmanager/ccs support the vm RA's new migrate-setspeed?

On 05/10/15 22:36 -0400, Digimer wrote: > Re: https://github.com/ClusterLabs/resource-agents/pull/629 > > I'd love to support this in the current gen Anvil!. Would it be hard to > add support to ccs for this? All depends on the capabilities of vm.sh resource agent for rgmanager. When the

Re: [ClusterLabs] crm_mon memory leak

On 09/11/15 13:11 +, Karthikeyan Ramasamy wrote: > root 13405 1 0 13:42 ?00:00:00 /usr/sbin/crm_mon -p > /tmp/ClusterMon_SNMP_10.64.109.36.pid -d -i 15 -E > /opt/occ/CXP_902_0588_R13B2370/tools/PCSESA.sh -h > /tmp/ClusterMon_SNMP_10.64.109.36.html > root 13566 13405 0

Re: [ClusterLabs] Cannot use upstart resources

On 28/09/15 14:01 +0200, dan wrote: > If I do pcs resource standards > I get: > ocf > lsb > service > upstart > stonith > > But if I do pcs resource create upstart:yyy > I get: > Error: Unable to create resource 'upstart:yyy', it is not installed on this > system (use --force to override)

[ClusterLabs] [Announce] clufter-0.50.4 released

I am happy to announce that clufter-0.50.4, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] Need bash instead of /bin/sh

On 23/09/15 15:38 +0200, Ulrich Windl wrote: Vladislav Bogdanov schrieb am 23.09.2015 um 15:24 >> 23.09.2015 15:42, dan wrote: >>> Did a small test: >>> ---test.sh >>> controld_start() { >>> local addr_list=$(echo AF_INET 10.1.1.1

[ClusterLabs] [Announce] clufter-0.55.0 released

I am happy to announce that clufter-0.55.0, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] OCF Resource Agent for Galera

On 29/11/15 21:32 +0530, Mayank Katyal wrote: > I am facing error with the following OCF resource agent for Galera using it > with Pacemaker and Heartbeat for setting up High Availability with MariaDB > database server with multi Master on Debian Wheezy: > > Galera Resource Agent >

Re: [ClusterLabs] Can't get nfs4 to work.

On 02/06/16 02:35 +0200, Dennis Jacobfeuerborn wrote: > On 01.06.2016 20:25, Stephano-Shachter, Dylan wrote: >> I have just finished setting up my HA nfs cluster and I am having a small >> problem. I would like to have nfs4 working but whenever I try to mount I >> get the following message, >> >>

Re: [ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command

Hello Nikhil, On 03/06/16 16:33 +0530, Nikhil Utane wrote: > The node is up alright. > > [root@airv_cu pcs]# pcs cluster status > Cluster Status: > Stack: corosync > Current DC: airv_cu (version 1.1.14-5a6cdd1) - partition WITHOUT quorum > Last updated: Fri Jun 3 11:01:32 2016 Last

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

Re: [ClusterLabs] fence_sanlock and pacemaker

[adding sanlock-devel ML into the loop as deemed appropriate] On 18/05/16 12:49 +, Da Shi Cao wrote: > After some try and error, fence_sanlock can be used as a stonith > resource in pacemaker+corosync. > 1. Add a "monitor" action, which is exactly the same action as > "status". Per

Re: [ClusterLabs] Pacemaker 1.1.15 - Release Candidate 3

On 27/05/16 16:21 -0500, Ken Gaillot wrote: > The third release candidate for Pacemaker version 1.1.15 is now > available at: > > https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.15-rc3 Once gain, to check this release candidate out using Fedora/EPEL builds, there's a COPR

Re: [ClusterLabs] Alert notes

On 15/06/16 18:45 +0200, Klaus Wenninger wrote: > On 06/15/2016 06:11 PM, Ferenc Wágner wrote: >> Did you think about filtering the environment variables passed to the >> alert scripts? NOTIFY_SOCKET probably shouldn't be present, and PATH >> probably shouldn't contain sbin directories; I guess

Re: [ClusterLabs] DLM not working on my GFS2/pacemaker cluster

On 18/01/16 21:47 -0500, dan...@benoy.name wrote: > Here's the exact same command run twice. First, on a very similarly > configured cluster (which is currently running): > # cat /sys/kernel/config/dlm/cluster/comms/169446438/addrcat > cat: /sys/kernel/config/dlm/cluster/comms/169446438/addr:

Re: [ClusterLabs] Fwd: dlm not starting

On 05/02/16 14:22 -0500, nameless wrote: > Hi Hello >nameless<, technical aspect aside, it goes without saying that engaging in a community assumes some level of cultural and social compatibility. Otherwise there is a danger the cluster will partition, and that would certainly be unhelpful.

Re: [ClusterLabs] fence agent and using it with pacemaker

On 10/02/16 15:20 +0100, Stanislav Kopp wrote: > I have general, clarification question about how fence agents work > with pacemaker (crmsh in particular). As far I understood STDIN > arguments can be used within pacemaker resources and command line > arguments in terminal (for testing and

Re: [ClusterLabs] Cluster resources migration from CMAN to Pacemaker

On 09/02/16 15:34 +0530, jaspal singla wrote: > Hi Jan/Digiman, (as a matter of fact, Digimer, from Digital Mermaid :-) > Thanks for your replies. Based on your inputs, I managed to configure these > values and results were fine but still have some doubts for which I would > seek your help. I

[ClusterLabs] [Announce] clufter-0.56.0 released

I am happy to announce that clufter-0.56.0, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key, expiration of which was prolonged just a few days back so you may want to consult key servers first):

Re: [ClusterLabs] Cluster resources migration from CMAN to Pacemaker

On 27/01/16 19:41 +0100, Jan Pokorný wrote: > On 27/01/16 11:04 -0600, Ken Gaillot wrote: >> On 01/27/2016 02:34 AM, jaspal singla wrote: >>> 1) In CMAN, there was meta attribute - autostart=0 (This parameter disables >>> the start of all services when RGManage

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

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. > > https://github.com/ClusterLabs/libqb/pull/175

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

On 26/02/16 08:58 +0100, 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 p

Re: [ClusterLabs] pacemakerd --version display bug?

On 23/02/16 22:07 +, Jeremy Matthews wrote: > I recently installed pacemaker on a system and found it interesting > that pacemaker -version and yum info pacemaker give different > versions, 1.1.11 and 1.1.12, respectively: > > > [root@g5se-f5c56a rc3.d]# pacemakerd --version > Pacemaker

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

On 25/02/16 13:24 +, Christine Caulfield wrote: > 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. Once again, there are EPEL/Fedora builds for convenient testing:

Re: [ClusterLabs] Cluster resources migration from CMAN to Pacemaker

On 24/01/16 16:54 +0530, jaspal singla wrote: > Thanks Digimer for letting me about the tool. I was unaware of any such > tools!! And because of that I was able to search clufter-cli tool for the > migration. > > Thanks a lot John for explaining each and everything in detailed manner. I > am

Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

On 14/01/16 14:46 +0100, Kristoffer Grönlund wrote: > Joakim Hansson writes: >> When adding the Delay RA it starts throwing a bunch of errors and the >> cluster starts fencing the nodes one by one. >> >> The error's I get with "pcs status": >> >> Failed Actions: >> *

Re: [ClusterLabs] Pacemaker license

On 12/01/16 11:27 +1100, Andrew Beekhof wrote: >> On 6 Oct 2015, at 9:39 AM, santosh_bidara...@dell.com wrote: >> As per the given link http://clusterlabs.org/wiki/License, it is >> mentioned that “Pacemaker programs are licensed under the GPLv2+ >> (version 2 or later of the GPL) and its headers

Re: [ClusterLabs] Sudden stop of pacemaker functions

On 17/02/16 14:10 +0200, Klechomir wrote: > Having strange issue lately. > I have two node cluster with some cloned resources on it. > One of my nodes suddenly starts reporting all its resources down (some of > them are actually running), stops logging and reminds in this this state > forever,

Re: [ClusterLabs] Freezing/Unfreezing in Pacemaker ?

On 07/04/16 09:12 -0500, Ken Gaillot wrote: > On 04/07/2016 06:40 AM, jaspal singla wrote: >> As we have clusvcadm -U and clusvcadm -Z >> to freeze and unfreeze resource in CMAN. Would really appreciate if >> someone please give some pointers for freezing/unfreezing a resource in >> Pacemaker

[ClusterLabs] [Announce] clufter-0.56.2 released

I am happy to announce that clufter-0.56.2, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key, expiration of which was prolonged just a few days back so you may want to consult key servers first):

Re: [ClusterLabs] Error creating a fence mechanism

On 22/03/16 09:31 +0100, Tomas Jelinek wrote: > Dne 21.3.2016 v 21:17 Douglas Restrepo napsal(a): >> The problem what Im having is that I don't have a physical PDU, so I >> have to simulate one. You don't have to, there are fencing mechanism beyond power switching (fence_ifmib for controlling

Re: [ClusterLabs] pacemakerd: undefined symbol: crm_procfs_process_info

On 23/03/16 18:40 +0100, philipp.achmuel...@arz.at wrote: > $ sudo pacemakerd -V > pacemakerd: symbol lookup error: pacemakerd: undefined symbol: > crm_procfs_process_info For a start, please provide output of: ls -l $(rpm -E %{_libdir})/libcrmcommon.so* ldd $(rpm -E %{_sbindir})/pacemakerd

Re: [ClusterLabs] Antwort: Re: Antwort: Re: pacemakerd: undefined symbol: crm_procfs_process_info

On 24/03/16 14:38 +0100, philipp.achmuel...@arz.at wrote: > Jan Pokorný <jpoko...@redhat.com> schrieb am 24.03.2016 12:48:44: > >> Von: Jan Pokorný <jpoko...@redhat.com> >> An: Cluster Labs - All topics related to open-source clustering >> welcomed <users@c

Re: [ClusterLabs] Coming in 1.1.15: recurring stop operations

On 01/04/16 11:41 -0500, Ken Gaillot wrote: > In current versions of Pacemaker, trying to configure a stop operation > with a time interval results in a warning about an "invalid configuration." > > A popular request from the community has been to enable this feature, > and I am proud to announce

Re: [ClusterLabs] [Announce] libqb 1.0 release

On 01/04/16 13:59 +0100, Christine Caulfield wrote: > I am very pleased to announce the 1.0 release of libqb > > [...] > > The current release tarball is here: > https://github.com/ClusterLabs/libqb/releases/download/v1.0/libqb-1.0.tar.gz One should preferably start at

Re: [ClusterLabs] Corosync do not send traffic

On 30/03/16 17:09 +0200, Roberto Munoz Gomez wrote: > I am trying to migrate the bindnetaddr option from corosync.conf to > cluster.conf but couldn't make it work. I want to use this interface for > corosync traffic. > > inet addr:10.76.125.236 Bcast:10.76.125.239 Mask:255.255.255.240 Looking

Re: [ClusterLabs] fence_scsi no such device

On 21/03/16 09:46 -0500, Ken Gaillot wrote: > You need more attributes, such as "devices" to specify which SCSI > devices to cut off, and either "key" or "nodename" to specify the > node key for SCSI reservations. Hmm, I keep lamenting that by extending agents metadata with inline RelaxNG grammar

Re: [ClusterLabs] Pacemaker 1.1.15 - Release Candidate 1

On 22/04/16 17:54 -0500, Ken Gaillot wrote: > ClusterLabs is happy to announce the first release candidate for > Pacemaker version 1.1.15. Source code is available at: > > https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.15-rc1 To check this release candidate out using

Re: [ClusterLabs] cluster stops randomly

On 21/05/16 04:46 +, H Yavari wrote: > I have a cluster and it works good, but I see sometimes cluster is > stopped on all nodes and I should start manually. pcsd service is > running but cluster is stopped.I see the pacemaker log but I > couldn't find any warning or error. what is the issue?

Re: [ClusterLabs] Pacemaker 1.1.15 - Release Candidate 2

On 16/05/16 10:48 -0500, Ken Gaillot wrote: > The second release candidate for Pacemaker version 1.1.15 is now > available at: > > https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.15-rc2 > > The most interesting changes since 1.1.15-rc1 are: > > * With the new "alerts"

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

On 06/05/16 14:52 +0100, Jim Rippon wrote: > Thank you guys, > > I've taken your advice onboard and checked out 1.1.15-rc1 including the > patches Lars mentions as Jan suggested - I see another warning with fatal > warnings enabled: > > gmake[2]: Entering directory

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

On 06/05/16 13:31 +0200, Lars Ellenberg wrote: > On Fri, May 06, 2016 at 11:51:25AM +0100, Jim Rippon wrote: >> I'm new to the list so apologies if I'm way off base, but I wonder >> if someone can help me please? >> >> I'm looking to build private RPMs for pacemaker and any dependencies >> for

Re: [ClusterLabs] libqb 0.17.1 - segfault at 1b8

Hello Radoslaw, On 02/05/16 11:47 -0500, Radoslaw Garbacz wrote: > When testing pacemaker I encountered a start error, which seems to be > related to reported libqb segmentation fault. > - cluster started and acquired quorum > - some nodes failed to connect to CIB, and lost membership as a result

Re: [ClusterLabs] Clusvcadm -Z substitute in Pacemaker

On 13/07/16 12:50 +0200, emmanuel segura wrote: > using pcs resource unmanage leave the monitoring resource actived, I > usually set the monitor interval=0 :) Some time ago, I've filed a bug against pcs for it to perform these two steps in one go: https://bugzilla.redhat.com/1303969 This slowly

Re: [ClusterLabs] Pacemaker in puppet with cib.xml?

On 21/07/16 13:52 -0500, Ken Gaillot wrote: > On 07/21/2016 01:35 PM, Stephano-Shachter, Dylan wrote: >> I want to put the pacemaker config for my two node cluster in puppet >> but, since it is just one cluster, it seems overkill to use the corosync >> module. If I just have puppet push cib.xml to

[ClusterLabs] [Announce] clufter v0.59.2 released

Hello , I am happy to announce that clufter, a tool/library for transforming and analyzing cluster configuration formats, got its version 0.59.1 tagged and released (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

On 09/08/16 20:20 +, Jason A Ramsey wrote: > Here’s the output I now get out of pip install pywsman: > > < stupiderrormessage > > > # pip install pywsman > DEPRECATION: Python 2.6 is no longer supported by the Python core team, > please upgrade your Python. A future version of pip will drop

[ClusterLabs] [Announce] clufter v0.59.4 released

I am happy to announce that clufter, a tool/library for transforming and analyzing cluster configuration formats, got its version 0.59.4 tagged and released (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

On 10/08/16 16:52 +, Jason A Ramsey wrote: > Installing the openwsman-python package doesn’t work. Configure’ing > the fence-agents source tree fails because it still can’t find the > pywsman module. I thought that it might be because it’s looking in > /usr/lib/python-x/site-packages rather

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

On 10/08/16 20:50 +0200, Jan Pokorný wrote: > On 10/08/16 16:52 +, Jason A Ramsey wrote: >> Installing the openwsman-python package doesn’t work. Configure’ing >> the fence-agents source tree fails because it still can’t find the >> pywsman module. I thought that it

Re: [ClusterLabs] Unable to Build fence-agents from Source on RHEL6

On 10/08/16 10:12 -0500, Dmitri Maziuk wrote: > On 2016-08-10 10:04, Jason A Ramsey wrote: > >> Traceback (most recent call last): >> >> File "eps/fence_eps", line 14, in >> >> if sys.version_info.major > 2: >> >> AttributeError: 'tuple' object has no attribute 'major' > > > Replace with

Re: [ClusterLabs] agent ocf:pacemaker:controld

> On 18/07/16 07:59, Da Shi Cao wrote: >> dlm_controld is very tightly coupled with cman. Wrong assumption. In fact, support for shipping ocf:pacemaker:controld has been explicitly restricted to cases when CMAN logic (specifically the respective handle-all initscript that is in turn, in that

[ClusterLabs] [Announce] clufter v0.58.0 released

I am happy to announce that clufter, a tool/library for transforming and analyzing cluster configuration formats, got its version 0.58.0 released and published (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] [Announce] clufter-0.57.0 (+0.56.3) released

(somehow I managed to mangle the changelog, also in the tag message where I just copied the lines from, so to reconcile that, modifications inline below) On 01/07/16 22:57 +0200, Jan Pokorný wrote: > Changelog highlights for v0.56.3: > - this is a bug fix release > -

Re: [ClusterLabs] [Announce] clufter-0.57.0 (+0.56.3) released

On 07/07/16 15:16 +0200, Jan Pokorný wrote: > (somehow I managed to mangle the changelog, also in the tag message > where I just copied the lines from, so to reconcile that, > modifications inline below) (gotta switch from holiday mode again) > On 01/07/16 22:57 +0200, Jan P

[ClusterLabs] [Announce] clufter v0.59.5 released

I am happy to announce that clufter, a tool/library for transforming and analyzing cluster configuration formats, got its version 0.59.5 tagged and released (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] Pacemaker in puppet with cib.xml?

On 21/07/16 21:51 +0200, Jan Pokorný wrote: > Yes, it's counterintuitive to have this asymmetry and it could be > made to work with some added effort at the side of pcs with > the original, disapproved, sequence as-is, but that's perhaps > sound of the future per the referenced pcs bu

Re: [ClusterLabs] Antw: Doing reload right

On 01/07/16 09:23 +0200, Ulrich Windl wrote: Ken Gaillot schrieb am 30.06.2016 um 18:58 in Nachricht > <57754f9f.8070...@redhat.com>: >> I've been meaning to address the implementation of "reload" in Pacemaker >> for a while now, and I think the next release will

[ClusterLabs] [Announce] clufter-0.57.0 (+0.56.3) released

I am happy to announce that clufter-0.57.0, a tool/library for transforming/analyzing cluster configuration formats, has been released and published (incl. signature using my 60BCBB4F5CD7F9EF key, expiration of which was prolonged just a few days back so you may want to consult key servers first):

Re: [ClusterLabs] Antw: Re: lrmd segfault

On 31/01/17 10:16 +0100, Ulrich Windl wrote: >>> Kristoffer Grönlund schrieb am 31.01.2017 um 07:34 >>> in Nachricht <87mve768lx@suse.com>: > > [...] >> Just from looking at the core dump, it looks like your processor doesn't >> support the SSE extensions used by the

Re: [ClusterLabs] Antw: Re: lrmd segfault

On 31/01/17 15:04 +0100, Jan Pokorný wrote: > On 31/01/17 10:16 +0100, Ulrich Windl wrote: >>>> Kristoffer Grönlund <deceive...@gmail.com> schrieb am 31.01.2017 um 07:34 >>>> in Nachricht <87mve768lx@suse.com>: >> >> [...] >>> Just

Re: [ClusterLabs] pcsd 99% CPU

On 03/02/17 16:08 -0500, Scott Greenlese wrote: > Over the past few days, I noticed that pcsd and ruby process is pegged at > 99% CPU, and commands such as pcs status pcsd take up to 5 minutes to > complete. > On all active cluster nodes, top shows: > > PID USER PR NI VIRT

Re: [ClusterLabs] corosync dead loop in segfault handler

On 15/02/17 15:13 +, Christine Caulfield wrote: > On 15/02/17 14:50, Jan Friesse wrote: >>> Hi all, >>> >>> Corosync Cluster Engine, version '2.3.4' >>> Copyright (c) 2006-2009 Red Hat, Inc. >>> >>> Today I found corosync consuming 100% cpu. Strace showed following: >>> >>> write(7,

Re: [ClusterLabs] corosync dead loop in segfault handler

On 15/02/17 18:04 +0100, Jan Pokorný wrote: > On 15/02/17 15:13 +, Christine Caulfield wrote: >> On 15/02/17 14:50, Jan Friesse wrote: >>>> Hi all, >>>> >>>> Corosync Cluster Engine, version '2.3.4' >>>> Copyright (c) 2006-2009 Red

[ClusterLabs] [Announce] clufter v0.59.8 released

I am happy to announce that clufter, a tool/library for transforming and analyzing cluster configuration formats, got its version 0.59.8 tagged and released (incl. signature using my 60BCBB4F5CD7F9EF key):

Re: [ClusterLabs] Entire Group stop on stopping of single Resource

On 19/08/16 23:09 +0530, jaspal singla wrote: > I have an resource group (ctm_service) comprise of various resources. Now > the requirement is when one of its resource stops for soem time (10-20) > seconds, I want entire group will be stopped. Note that if resource is stopped _just_ for this

Re: [ClusterLabs] What cib_stats line means in logfile

On 25/08/16 17:55 +0200, Sébastien Emeriau wrote: > When i check my corosync.log i see this line : > > info: cib_stats: Processed 1 operations (1.00us average, 0% > utilization) in the last 10min > > What does it mean (cpu load or just information) ? These are just periodically (10 minutes

Re: [ClusterLabs] What cib_stats line means in logfile

On 05/09/16 21:26 +0200, Jan Pokorný wrote: > On 25/08/16 17:55 +0200, Sébastien Emeriau wrote: >> When i check my corosync.log i see this line : >> >> info: cib_stats: Processed 1 operations (1.00us average, 0% >> utilization) in the last 10min >> >&

Re: [ClusterLabs] pcs cluster auth returns authentication error

On 26/08/16 02:14 +, Jason A Ramsey wrote: > Well, I got around the problem, but I don’t understand the solution… > > I edited /etc/pam.d/password-auth and commented out the following line: > > authrequiredpam_tally2.so onerr=fail audit silent > deny=5

Re: [ClusterLabs] Pacemaker quorum behavior

On 08/09/16 10:20 -0400, Scott Greenlese wrote: > Correction... > > When I stopped pacemaker/corosync on the four (powered on / active) > cluster node hosts, I was having an issue with the gentle method of > stopping the cluster (pcs cluster stop --all), Can you elaborate on what went wrong

Re: [ClusterLabs] Pacemaker quorum behavior

On 09/09/16 14:13 -0400, Scott Greenlese wrote: > You had mentioned this command: > > pstree -p | grep -A5 $(pidof -x pcs) > > I'm not quite sure what the $(pidof -x pcs) represents?? This is a "command substitution" shell construct (new, blessed form of `backtick` notation) that in this

Re: [ClusterLabs] Failed to retrieve meta-data for custom ocf resource

On 28/09/16 16:55 -0500, Ken Gaillot wrote: > On 09/28/2016 04:04 PM, Christopher Harvey wrote: >> My corosync/pacemaker logs are seeing a bunch of messages like the >> following: >> >> Sep 22 14:50:36 [1346] node-132-60 crmd: info: >> action_synced_wait: Managed

Re: [ClusterLabs] Failed to retrieve meta-data for custom ocf resource

Hello , On 29/09/16 12:41 -0400, Christopher Harvey wrote: > I think something is failing at the execvp() level. I'm seeing > useful looking trace logs in the code, but can't enable them right > now. I have: > PCMK_debug=yes > PCMK_logfile=/tmp/pacemaker.log > PCMK_logpriority=debug >

Re: [ClusterLabs] Pacemaker quorum behavior

On 28/09/16 16:30 -0400, Scott Greenlese wrote: > Also, I have tried simulating a failed cluster node (to trigger a > STONITH action) by killing the corosync daemon on one node, but all > that does is respawn the daemon ... causing a temporary / transient > failure condition, and no fence takes

Re: [ClusterLabs] Virtual ip resource restarted on node with down network device

On 19/09/16 09:15 +, Auer, Jens wrote: > After the restart ifconfig still shows the device bond0 to be not RUNNING: > MDA1PFP-S01 09:07:54 2127 0 ~ # ifconfig > bond0: flags=5123 mtu 1500 > inet 192.168.120.20 netmask 255.255.255.255 broadcast 0.0.0.0

[ClusterLabs] Authoritative corosync's location (Was: corosync-quorum tool, output name key on Name column if set?)

On 21/09/16 09:16 +0200, Jan Friesse wrote: > Thomas Lamprecht napsal(a): >> I have also another, organizational question. I saw on the GitHub page from >> corosync that pull request there are preferred, and also that the > > True At this point, it's worth noting that ClusterLabs/corosync is

Re: [ClusterLabs] Virtual ip resource restarted on node with down network device

On 16/09/16 11:01 -0500, Ken Gaillot wrote: > On 09/16/2016 10:43 AM, Auer, Jens wrote: >> thanks for the help. >> >>> I'm not sure what you mean by "the device the virtual ip is attached >>> to", but a separate question is why the resource agent reported that >>> restarting the IP was

Re: [ClusterLabs] RFC: allowing soft recovery attempts before ignore/block/etc.

On 21/09/16 10:51 +1000, Andrew Beekhof wrote: > On Wed, Sep 21, 2016 at 6:25 AM, Ken Gaillot wrote: >> Our first proposed approach would add a new hard-fail-threshold >> operation property. If specified, the cluster would first try restarting >> the resource on the same

Re: [ClusterLabs] pacemakerd quits after few seconds with some errors

On 23/08/16 07:23 +0200, Gabriele Bulfon wrote: > Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the > "--with-corosync". > How is Corosync looking for his own version? The situation may be as easy as building corosync from GitHub-provided automatic tarball, which is never a good

Re: [ClusterLabs] converting configuration

Hello , [First, please note that your email sending application does not treat plaintext part of what is sent correctly -- formatting, at least new lines, are lost, which impacts readability in both text-only email clients and on ClusterLabs users ML archive pages:

Re: [ClusterLabs] Pacemaker remote - invalid message detected, endian mismatch

On 30/09/16 11:28 -0500, Radoslaw Garbacz wrote: > I have posted a question about this error attached to another thread, but > because it was old and there is no answer I thought it could have been > missed, so I am sorry for repeating it. > > Regarding the problem. > I have a cluster, and when

Re: [ClusterLabs] Authoritative corosync's location

On 22/09/16 09:05 +0200, Jan Friesse wrote: > Jan Pokorný napsal(a): >> On 21/09/16 09:16 +0200, Jan Friesse wrote: >>> Thomas Lamprecht napsal(a): >>>> I have also another, organizational question. I saw on the GitHub page from >>>> corosync that

Re: [ClusterLabs] Pacemaker 1.1.16 - Release Candidate 1

On 03/11/16 11:08 -0500, Ken Gaillot wrote: > ClusterLabs is happy to announce the first release candidate for > Pacemaker version 1.1.16. Source code is available at: > > https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.16-rc1 > > [...] As usual, there are COPR builds (using

[ClusterLabs] [Announce] clufter v0.59.6 released

I am happy to announce that clufter, a tool/library for transforming and analyzing cluster configuration formats, got its version 0.59.6 tagged and released (incl. signature using my 60BCBB4F5CD7F9EF key):

  1   2   3   4   >