Re: [Pacemaker] [RPMs] clusterlabs.org and epel-6 ?

Re, How many nano-seconds has centos-6 been out for? Not much I agree. I didn't want to be offensive, don't read me wrong. But because the repo exists for a while (3 months or so) and scientific linux 6 and oracle linux 6 were out as well I was wondering if this was going to be used or not.

[Pacemaker] [RPMs] clusterlabs.org and epel-6 ?

Hi, On clusterlabs.org, there are 2 repositories epel-5 and epel-6. However the epel-6 repository [1] is empty. Do you guys plan to use it or should we build our own RPMs because it's never going to happen ? I believe, like many, with (finally) Centos 6 out we would like to start to upgrade

Re: [Pacemaker] dampen / pingd - how to be sure pingd will be updated

Hey, >> This may be dumb or obvious but it took me a long time to understand why my >> pingd with >> dampen never got updated! So I think that this may be useful for everybody >> to share. >> In short: >> >> " You MUST define a monitor interval HIGHER than the the dampen delay. " > Which versi

[Pacemaker] dampen / pingd - how to be sure pingd will be updated

Hey guys, This may be dumb or obvious but it took me a long time to understand why my pingd with dampen never got updated! So I think that this may be useful for everybody to share. In short: " You MUST define a monitor interval HIGHER than the the dampen delay. " An example is better than

[Pacemaker] [RPM] ldirectord on clusterlabs.org (epel5)

Hey guys, I am using ldirectord and pacemaker from the clusterlabs epel5 repo. However the latest ldirectord 1.0.3 can't be installed on a el5 (centos5 in my case). Yum whinges about the following : ERROR with rpm_check_debug vs depsolve: heartbeat-ldirectord conflicts with ldirectord-1.0

Re: [Pacemaker] [PING] ping, pingd and CIB updates, pick your poison :)

Hi Andrew, First thanks for remembering my issue and looking into it :) Jul 30 11:37:50 [..] Yes but... See the time line pasted below. (at 11:37, it starts to do something) 11:20AM : cluster is up and running 11:25AM : shutdown the IP 11:30AM : force a refresh with attrd_updater (because p

Re: [Pacemaker] [PING] ping, pingd and CIB updates, pick your poison :)

Re, > [..] I can provide a hb_report if necessary. See in attachment a report for the simple config below. Note that I dumbly erased the conf before doing the report but I paste it below. I've done a very simple cluster. 2 nodes running a dummy resource with 2 cloned pings testing a virtual I

Re: [Pacemaker] [PING] ping, pingd and CIB updates, pick your poison :)

Hey, How long did you wait? dampen="121" means that attrd will wait just over 2 minutes before updating the CIB 10min. Thomas ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Ho

[Pacemaker] [PING] ping, pingd and CIB updates, pick your poison :)

Hey, As much as I like pacemaker I hate these ping tests which don't update the CIB. After reading a lot on the mailing list I see that people are still a lot confused. So can one of the main developers give an example that should work like "how to check your connectivity" ? (the wiki still t

Re: [Pacemaker] Problem: No space left on device.

Hi Kees, touch: cannot touch `testfile': No space left on device I definitely think that it isn't a pacemaker issue :) I believe you have no more inodes even if you can see free space left. Try: df -i. And then google about your (common) system issue. Cheers, Thomas

Re: [Pacemaker] ha-clustering repo?

Hey Erich, Did I miss an announcement? Are they to be found somewhere else? I see the pacemaker-mgmt rpms there too, but not the regular pacemaker rpms. Repo. is : Repository is also announced in the Install doco :

Re: [Pacemaker] Announce: Pacemaker 1.0.7 (stable) Released

Hey, Pre-built packages for Pacemaker and it s immediate dependancies are currently building and will be available for openSUSE, SLES, Fedora, RHEL, CentOS from the ClusterLabs Build Area (http://www.clusterlabs.org/rpm) shortly. Thanks Andrew. I'll move from 1.0.6 + patch to 1.0.7 at the end

Re: [Pacemaker] Error on compiling Pacemaker-GUI

Hi, I got the follow error after untar the tar ball of Pacemaker GUI: [..] aclocal:configure.in:57: warning: macro `AM_PO_SUBDIRS' not found in library Do a : autoreconf -ifs See thread: "[RPM] pacemaker-mgmt for corosync 1.1.2 and pacemaker 1.0.6" Thomas _

[Pacemaker] [RPM] Corosync 1.2.0 spec file

ndir}/man8/logsys_overview.8* %{_mandir}/man8/votequorum_overview.8* %{_mandir}/man8/coroipc_overview.8* +%{_mandir}/man8/sam_overview.8.gz %changelog +* Fri Jan 08 2010 Thomas Guthmann - 1.2.0-1 +- New upstream release +- spec file updates: + * New Simple Availability Manager (SAM) + * Fri Oct 23 20

[Pacemaker] [BUG] crm_mon different output

Hi, I notice a small issue when using crm_mon. Indeed the following command don't output the same information about the inactives resources : * "crm_mon -r -n -1" * "crm_mon -r -n -h /tmp/tom.html" More info: Cheers, Thomas _

Re: [Pacemaker] [BUG] Clone + group = orphan(s) ?

Hi Andrew, Can you log a bug for that please? ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Re: [Pacemaker] [BUG] Clone + group = orphan(s) ?

Re, I've just had 2 orphans (tom-DNS:2,tom-DNS:3) for a clone containing 2 groups (tom-DNS:0, tom-DNS:1). Anyway the situation is far better than before, no more craziness during cleanups. I will dig and test more tomorrow and give you an update to see if I can reproduce the issue. 1. I was wo

Re: [Pacemaker] [BUG] Clone + group = orphan(s) ? :: crm shell

Hey Dejan, [..] Does "updated" mean deleted now ? :) "update" doesn't sound like "delete" to me :) It was a jibe :) That's really strange since crm doesn't depend on any internal business of CRM. Remember, I'm using the latest pacemaker version as suggested by Andrew to fix some of my clone

Re: [Pacemaker] [BUG] Clone + group = orphan(s) ?

Re, Any chance you could download the latest tarball and try that? http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/1aa7cf1450e4.tar.bz2 Awesome! No more orphans ! \o/ Almost actually :( I've just had 2 orphans (tom-DNS:2,tom-DNS:3) for a clone containing 2 groups (tom-DNS:0, to

Re: [Pacemaker] [BUG] Clone + group = orphan(s) ?

Hi Andrew Any chance you could download the latest tarball and try that? http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/1aa7cf1450e4.tar.bz2 Awesome! No more orphans ! \o/ Everything is working now, it's clean and tidy. *But* ... there is a small regression in the crm tool. When I

Re: [Pacemaker] [BUG] Clone + group = orphan(s) ?

Re, So cloned groups are not fun and side effects are random :) I will do more tests without IPAddr2 which seems a bit fancy and dodgy. I've just tried to clone a group tom-TEST containing 2 simple primitives (ocf:homemade:named and ocf:pacemaker:Dummy). The group runs fine but when I ask pa

[Pacemaker] [BUG] IPaddr2 - default clusterhash value

Hey, When you use IPaddr2 in a clone, it will use a clusterip mechanism. The default value for the hash is sourceip-sourceport. But this won't work and will trigger errors because the line 281 is : IP_CIP_HASH="${OCF_RESKEY_clusterip_hash:-'sourceip-sourceport'}" and I think that should

[Pacemaker] [BUG] Clone + group = orphan(s) ?

Hi, I noticed weird stuff with pacemaker when I ask it to clone a group. Let's say that I have a group containing 4 primitives (1 named process + 3 IPAddr2 to load on lo). I want to clone the group tom-DNS twice. crm configure clone tom-DNS-clone tom-DNS meta clone-max=2 If the group is

[Pacemaker] [RPM] pacemaker-mgmt for corosync 1.1.2 and pacemaker 1.0.6

Heya, I know that not everybody does like GUI but sometimes it's handy to see the big picture. So here is a corosync compatible version of pacemaker-mgmt. I didn't do much except changing the Requires: in the .spec file. All credits still goes to ygao at novell.com for all the packaging effor

Re: [Pacemaker] Asymmetrical cluster : should it probe resources that won't be installed on a node ?

Hi Andrew, no, 1 isn't the default, IIRC its -1 (ie. keep them all) Indeed, I saw that in hb_gui _but_ in the documentation it's written that it's 1. So I prefered to quote what the doco said instead of hb_gui. See :

Re: [Pacemaker] Asymmetrical cluster : should it probe resources that won't be installed on a node ?

Hi Andrew, First thanks for your time, your responsiveness and the great piece of software you're providing us. "Thank you!". The logging could probably be toned down in such cases though. Hmm, I don't know how to do that. Is it possible from my side or did you said that as a remark (for the

[Pacemaker] Asymmetrical cluster : should it probe resources that won't be installed on a node ?

Hi, I was wondering why pacemaker is throwing errors about program not installed when it is normal that is not. For instance, on a loadbalancer node (ed-lb2) we don't want to host named (DNS daemon). The cluster is working so far even if pacemaker seems not happy because it still tries to see