pacemaker@oss.clusterlabs.org
On Thu, Mar 14, 2013 at 10:18 AM, Andrew Beekhof wrote: > On Wed, Mar 13, 2013 at 8:55 PM, matonb wrote: >> Andrew Beekhof writes: >> >>> >>> On Wed, Mar 13, 2013 at 5:55 PM, matonb wrote: >>> > Andrew Beekhof writes: >>> > >>> >> >>> >> On Wed, Mar 13, 2013 at 3:59 AM, matonb wrote: >>> >> > Hi List, >>> >> > >>> >> > I've just upgraded a CentOS 6.3 server to 6.4, other than the >>> > disappearance >>> >> > of the crm shell tools, one thing I've noticed which is a minor >> annoyance >>> >> > rather than a problem is that users which are members of the haclient >>> > group >>> >> > can't use the crm tools any more: >>> > >>> > The 6.3 RPMS came from the CentOS base repository, any user that was a >> member >>> > of the haclient group could execute and connect to the cluster using >> commands >>> > such as crm_mon (the most frequently used). >>> >>> Ah, thats not the ACLs Lars was talking about. >>> What you're talking about should still work, nothing should have >>> changed in that area between 6.3 and 6.4. >>> I will investigate. >> >> Thanks :-) > > Ah. Hmmm, well this is embarrassing. > 6.4 uses a different IPC system than 6.3 and in the conversion we > unintentionally lost the ability to do what you're attempting. > It seems you're the first person to notice in the year since we > switched upstream :-( > > I'm going to set about fixing this now but I'm not yet sure if I'll be > able to get the fix into 6.4. > In the meantime, adding people to the root group (yes, I'm aware how > horrible that is) would return the capability in some form. I believe this should make everyone happy: https://github.com/beekhof/pacemaker/commit/3c9275e Are you able to test it? > Once I have restored the capability, I'll post updated RHEL RPMs to > clusterlabs.org/rpm-next > >> I think the ACL's got roped in because I tried to implement them to solve >> the problem. Which as you've both mentioned aren't in the release I'm >> using. >> >> >> >> >> ___ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [openais]when openais disappear
On 03/14/2013 04:33 AM, Andrew Beekhof wrote: On Wed, Mar 13, 2013 at 8:55 PM, zhuyj wrote: On 03/13/2013 05:46 PM, Andrew Beekhof wrote: On Wed, Mar 13, 2013 at 8:13 PM, zhuyj wrote: hi, all I have a problem. When does openais disappear? who replace the function of openais? pacemaker or corosync? The interesting parts were spun off to create corosync. The SAF APIs were deemed to be not very useful and set on a course to be deprecated. Hi, thanks for your reply. I have a problem. How does pacemaker manage resource ? I mean that how pacemaker cleanup resource when resource is obsolete. It uses scripts called resource agents. http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/ch05.html Thanks a lot. I found a bug of openais. where can I commit this patch? ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Writing RAs - Parameters per node
On Thu, Mar 14, 2013 at 6:22 AM, Riccardo Bicelli wrote: > > Hello, > >> This is possible (you can have rules for the instance attributes), > > Could you provide me an example? This should do it: http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/_using_rules_to_control_resource_options.html > >> *but* it is a really bad idea for administrative reasons. It'll be a >> nightmare to remember, and bite you in every single script. It's usually a >> lot better to rename the ports via udev/ipaddr rules. Not sure how to do >> that for IB > > In this case is not possible (or is more nightmare than defining parameter > in RA), because is the target created by SCST, that is not mapped to a > device but only creates control interface under sysfs. > Each port has a specific GUID. > I need to control where to migrate the scsi target, because "different > boards do different things". > > Regards, > Riccardo > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [Question]About "sequential" designation of resource_set.
Hi Andrew, > In "colocation", I used "resource_set". > However, a result did not include the change. Please, about the result that I tried, give me comment. Best Regards, Hideo Yamauchi. --- On Thu, 2013/3/7, renayama19661...@ybb.ne.jp wrote: > Hi Andrew, > > > > You use the resource sets _instead_ of a group. > > > If you want group.ordered=false, then use a colocation set (with > > > sequential=true). > > In "colocation", I used "resource_set". > However, a result did not include the change. > > Will this result be a mistake of my setting? > > Case 1) sequential=false > (snip) > > > > > > > > > (sip) > [root@rh63-heartbeat2 ~]# grep "Initiating action" /var/log/ha-log > Mar 8 00:20:52 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 2: probe_complete probe_complete on rh63-heartbeat1 - no > waiting > Mar 8 00:20:52 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 3: probe_complete probe_complete on rh63-heartbeat2 (local) > - no waiting > Mar 8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 4: monitor vip-master_monitor_0 on rh63-heartbeat1 > Mar 8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 7: monitor vip-master_monitor_0 on rh63-heartbeat2 (local) > Mar 8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 5: monitor vip-rep_monitor_0 on rh63-heartbeat1 > Mar 8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 8: monitor vip-rep_monitor_0 on rh63-heartbeat2 (local) > Mar 8 00:20:55 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 6: probe_complete probe_complete on rh63-heartbeat2 (local) > - no waiting > Mar 8 00:20:56 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 3: probe_complete probe_complete on rh63-heartbeat1 - no > waiting > Mar 8 00:20:56 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 5: start vip-master_start_0 on rh63-heartbeat1 > Mar 8 00:20:58 rh63-heartbeat2 crmd: [22372]: info: te_rsc_command: > Initiating action 1: stop vip-master_stop_0 on rh63-heartbeat1 > > > Case 2) sequential=true > (snip) > > > > > > > > > (snip) > [root@rh63-heartbeat2 ~]# grep "Initiating action" /var/log/ha-log > Mar 7 23:54:44 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 2: probe_complete probe_complete on rh63-heartbeat1 - no > waiting > Mar 7 23:54:44 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 3: probe_complete probe_complete on rh63-heartbeat2 (local) > - no waiting > Mar 7 23:54:48 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 4: monitor vip-master_monitor_0 on rh63-heartbeat1 > Mar 7 23:54:48 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 7: monitor vip-master_monitor_0 on rh63-heartbeat2 (local) > Mar 7 23:54:48 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 5: monitor vip-rep_monitor_0 on rh63-heartbeat1 > Mar 7 23:54:48 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 8: monitor vip-rep_monitor_0 on rh63-heartbeat2 (local) > Mar 7 23:54:48 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 6: probe_complete probe_complete on rh63-heartbeat2 (local) > - no waiting > Mar 7 23:54:49 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 3: probe_complete probe_complete on rh63-heartbeat1 - no > waiting > Mar 7 23:54:49 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 5: start vip-master_start_0 on rh63-heartbeat1 > Mar 7 23:54:51 rh63-heartbeat2 crmd: [4]: info: te_rsc_command: > Initiating action 1: stop vip-master_stop_0 on rh63-heartbeat1 > > > Best Regards, > Hideo Yamauchi. > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
pacemaker@oss.clusterlabs.org
On Wed, Mar 13, 2013 at 8:55 PM, matonb wrote: > Andrew Beekhof writes: > >> >> On Wed, Mar 13, 2013 at 5:55 PM, matonb wrote: >> > Andrew Beekhof writes: >> > >> >> >> >> On Wed, Mar 13, 2013 at 3:59 AM, matonb wrote: >> >> > Hi List, >> >> > >> >> > I've just upgraded a CentOS 6.3 server to 6.4, other than the >> > disappearance >> >> > of the crm shell tools, one thing I've noticed which is a minor > annoyance >> >> > rather than a problem is that users which are members of the haclient >> > group >> >> > can't use the crm tools any more: >> > >> > The 6.3 RPMS came from the CentOS base repository, any user that was a > member >> > of the haclient group could execute and connect to the cluster using > commands >> > such as crm_mon (the most frequently used). >> >> Ah, thats not the ACLs Lars was talking about. >> What you're talking about should still work, nothing should have >> changed in that area between 6.3 and 6.4. >> I will investigate. > > Thanks :-) Ah. Hmmm, well this is embarrassing. 6.4 uses a different IPC system than 6.3 and in the conversion we unintentionally lost the ability to do what you're attempting. It seems you're the first person to notice in the year since we switched upstream :-( I'm going to set about fixing this now but I'm not yet sure if I'll be able to get the fix into 6.4. In the meantime, adding people to the root group (yes, I'm aware how horrible that is) would return the capability in some form. Once I have restored the capability, I'll post updated RHEL RPMs to clusterlabs.org/rpm-next > I think the ACL's got roped in because I tried to implement them to solve > the problem. Which as you've both mentioned aren't in the release I'm > using. > > > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [BULK] Re: Problem on creating CIB entry in CRM
Yes. Running as root. Original message From: Dejan Muhamedagic Date: To: The Pacemaker cluster resource manager Subject: [BULK] Re: [Pacemaker] Problem on creating CIB entry in CRM Hi, On Wed, Mar 13, 2013 at 09:43:09AM +, Paul Sun wrote: > I have seen some ppl has the problem in the archives, how I can solve this > problem? > > crm(live)# cib new testing > INFO: testing shadow CIB created > ERROR: testing: no such shadow CIB > crm(live)# Are you running this as root? Thanks, Dejan ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [BULK] Re: Problem on creating CIB entry in CRM
How I can create the bug ticket? In the meantime, any resolution? downgrade the corosync or pacemaker or crmsh?? Original message From: Dejan Muhamedagic Date: To: The Pacemaker cluster resource manager Subject: [BULK] Re: [Pacemaker] Problem on creating CIB entry in CRM On Wed, Mar 13, 2013 at 10:41:13AM +, Paul Sun wrote: > Hi > > I did not see the post is in the forum. But I found more information on this. > Any idea? I am running Centos6.3 x86_64. > > #crm_shadow -d > Segmentation fault (core dumped) Should probably open a bugzilla for this one. Thanks, Dejan > #rpm -q crmsh > crmsh-1.2.5-55.2.x86_64 > > # rpm -q corosync > corosync-1.4.1-15.el6.x86_64 > > # rpm -q pacemaker > pacemaker-1.1.8-7.el6.x86_64 > > > > -Original Message- > From: Paul Sun > Sent: Wednesday, March 13, 2013 5:43 PM > To: The Pacemaker cluster resource manager > Subject: Problem on creating CIB entry in CRM > > I have seen some ppl has the problem in the archives, how I can solve this > problem? > > crm(live)# cib new testing > INFO: testing shadow CIB created > ERROR: testing: no such shadow CIB > crm(live)# > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] mysql/drbd on wheezy active/passive setup issues
Thanks, I'll have a go with that. -C On Wed, 2013-03-13 at 22:58 +0100, emmanuel segura wrote: > Hello > > Use ocf-tester to debug your resource > > 2013/3/13 christopher barry > Greetings all, > > I'm almost there, and figure I just have something small out > of place. Wondering if you can view my setup here: > > > https://zerobin.permutation.net/?d8664af27a7de3be#Bh3fBAupeEw3RhBWOlvDomyPkoOzvD5ajTCk6+a1MW0= > > and let me know what you think. > > If you need more data to understand what could be wrong, > please let me know. > > Thanks, > Christopher > > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > > > > > -- > esta es mi vida e me la vivo hasta que dios quiera > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] mysql/drbd on wheezy active/passive setup issues
Hello Use *ocf-tester *to debug your resource 2013/3/13 christopher barry > ** > Greetings all, > > I'm almost there, and figure I just have something small out of place. > Wondering if you can view my setup here: > > > https://zerobin.permutation.net/?d8664af27a7de3be#Bh3fBAupeEw3RhBWOlvDomyPkoOzvD5ajTCk6+a1MW0= > > and let me know what you think. > > If you need more data to understand what could be wrong, please let me > know. > > Thanks, > Christopher > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > > -- esta es mi vida e me la vivo hasta que dios quiera ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] mysql/drbd on wheezy active/passive setup issues
Greetings all, I'm almost there, and figure I just have something small out of place. Wondering if you can view my setup here: https://zerobin.permutation.net/?d8664af27a7de3be#Bh3fBAupeEw3RhBWOlvDomyPkoOzvD5ajTCk6+a1MW0= and let me know what you think. If you need more data to understand what could be wrong, please let me know. Thanks, Christopher ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [openais]when openais disappear
On Wed, Mar 13, 2013 at 8:55 PM, zhuyj wrote: > On 03/13/2013 05:46 PM, Andrew Beekhof wrote: >> >> On Wed, Mar 13, 2013 at 8:13 PM, zhuyj wrote: >>> >>> hi, all >>> >>> I have a problem. When does openais disappear? who replace the function >>> of >>> openais? pacemaker or corosync? >> >> The interesting parts were spun off to create corosync. >> The SAF APIs were deemed to be not very useful and set on a course to >> be deprecated. >> > Hi, > thanks for your reply. > I have a problem. How does pacemaker manage resource ? I mean that how > pacemaker cleanup resource when resource is obsolete. It uses scripts called resource agents. http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/ch05.html ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Writing RAs - Parameters per node
Hello, This is possible (you can have rules for the instance attributes), Could you provide me an example? *but* it is a really bad idea for administrative reasons. It'll be a nightmare to remember, and bite you in every single script. It's usually a lot better to rename the ports via udev/ipaddr rules. Not sure how to do that for IB In this case is not possible (or is more nightmare than defining parameter in RA), because is the target created by SCST, that is not mapped to a device but only creates control interface under sysfs. Each port has a specific GUID. I need to control where to migrate the scsi target, because "different boards do different things". Regards, Riccardo ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Writing RAs - Parameters per node
On 2013-03-13T19:38:57, Riccardo Bicelli wrote: > Hello, > does anyone know if it is possible to have, in CIB declaration, a set of > parameters with different value per node? Yes. > For example, I have an RA which is dealing with SCSI target on infiniband > HCA card. > > on node1 the port I want to use is port1 of Infiniband card 1 > on node2 the the port I want to use is port2 of Infiniband Card 2 > > Is there any way to declare parameters "per host" both on a standard and > cloned resource? This is possible (you can have rules for the instance attributes), *but* it is a really bad idea for administrative reasons. It'll be a nightmare to remember, and bite you in every single script. It's usually a lot better to rename the ports via udev/ipaddr rules. Not sure how to do that for IB, but it's possible for everything else. Of course, it's even better to plug everything into the same ports ;-) That makes working on the hardware less confusing. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Writing RAs - Parameters per node
Hello, does anyone know if it is possible to have, in CIB declaration, a set of parameters with different value per node? For example, I have an RA which is dealing with SCSI target on infiniband HCA card. on node1 the port I want to use is port1 of Infiniband card 1 on node2 the the port I want to use is port2 of Infiniband Card 2 Is there any way to declare parameters "per host" both on a standard and cloned resource? And how to deal with it into the RA script? Or in this case have I to do this mapping on local files end reading from them? Thank you :) ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] A couple of SendArp resource changes
Hi,
On Sat, Mar 09, 2013 at 07:53:34PM +, Tim Small wrote:
> Hi,
>
> I've been using the ocf:heartbeat:SendArp script and notice a couple of
> issues - some problems with starting and monitoring the service, and
> also a file descriptor leak in the binary (which would cause it to
> terminate).
>
> I've detailed the problems and supplied some patches:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701913
Cannot just replace the whole RA. Sorry. If you could split the
patch we can consider them on a one-by-one basis. Otherwise, I
found some patch in my local queue, which never got pushed for
some reason. Don't know if that would help (attached).
> and
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701914
Can you try the attached send_arp.libnet.c patch. It does first
packet build then reuses them.
Cheers,
Dejan
> ... they're not perfect, but an improvement I think.
>
> HTH,
>
> Tim.
>
> --
> South East Open Source Solutions Limited
> Registered in England and Wales with company number 06134732.
> Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
> VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
>
>
> ___
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>From 9dae34616ef62b98b762a1f821f9e1ee749e6315 Mon Sep 17 00:00:00 2001
From: Dejan Muhamedagic
Date: Wed, 13 Mar 2013 18:19:10 +0100
Subject: [PATCH] Medium: tools: send_arp.libnet: reuse ARP packets
---
tools/send_arp.libnet.c | 174
1 file changed, 115 insertions(+), 59 deletions(-)
diff --git a/tools/send_arp.libnet.c b/tools/send_arp.libnet.c
index 71148bb..2abeecb 100644
--- a/tools/send_arp.libnet.c
+++ b/tools/send_arp.libnet.c
@@ -49,17 +49,18 @@
#ifdef HAVE_LIBNET_1_0_API
# define LTYPE struct libnet_link_int
+ static u_char *mk_packet(u_int32_t ip, u_char *device, u_char *macaddr, u_char *broadcast, u_char *netmask, u_short arptype);
+ static int send_arp(struct libnet_link_int *l, u_char *device, u_char *buf);
#endif
#ifdef HAVE_LIBNET_1_1_API
# define LTYPE libnet_t
+ static libnet_t *mk_packet(libnet_t* lntag, u_int32_t ip, u_char *device, u_char macaddr[6], u_char *broadcast, u_char *netmask, u_short arptype);
+ int send_arp(libnet_t* lntag);
#endif
#define PIDDIR HA_VARRUNDIR "/" PACKAGE
#define PIDFILE_BASE PIDDIR "/send_arp-"
-static int send_arp(LTYPE* l, u_int32_t ip, u_char *device, u_char mac[6]
-, u_char *broadcast, u_char *netmask, u_short arptype);
-
static char print_usage[]={
"send_arp: sends out custom ARP packet.\n"
" usage: send_arp [-i repeatinterval-ms] [-r repeatcount] [-p pidfile] \\\n"
@@ -135,7 +136,6 @@ main(int argc, char *argv[])
char* netmask;
u_int32_t ip;
u_char src_mac[6];
- LTYPE* l;
int repeatcount = 1;
int j;
long msinterval = 1000;
@@ -143,6 +143,13 @@ main(int argc, char *argv[])
charpidfilenamebuf[64];
char*pidfilename = NULL;
+#ifdef HAVE_LIBNET_1_0_API
+ LTYPE* l;
+ u_char *request, *reply;
+#elif defined(HAVE_LIBNET_1_1_API)
+ LTYPE *request, *reply;
+#endif
+
CL_SIGNAL(SIGTERM, byebye);
CL_SIGINTERRUPT(SIGTERM, 1);
@@ -201,6 +208,24 @@ main(int argc, char *argv[])
return EXIT_FAILURE;
}
+ if (!strcasecmp(macaddr, AUTO_MAC_ADDR)) {
+ if (get_hw_addr(device, src_mac) < 0) {
+ cl_log(LOG_ERR, "Cannot find mac address for %s",
+ device);
+ unlink(pidfilename);
+ return EXIT_FAILURE;
+ }
+ }
+ else {
+ convert_macaddr((unsigned char *)macaddr, src_mac);
+ }
+
+/*
+ * We need to send both a broadcast ARP request as well as the ARP response we
+ * were already sending. All the interesting research work for this fix was
+ * done by Masaki Hasegawa and his colleagues.
+ */
+
#if defined(HAVE_LIBNET_1_0_API)
#ifdef ON_DARWIN
if ((ip = libnet_name_resolve((unsigned char*)ipaddr, 1)) == -1UL) {
@@ -219,49 +244,65 @@ main(int argc, char *argv[])
unlink(pidfilename);
return EXIT_FAILURE;
}
+ request = mk_packet(ip, (unsigned char*)device, src_mac
+ , (unsigned char*)broadcast, (unsigned char*)netmask
+ , ARPOP_REQUEST);
+ reply = mk_packet(ip, (unsigned char*)device, src_mac
+ , (unsigned char *)broadcast
+ , (unsigned char *)netmask, ARPOP_REPLY);
+ if (!request || !reply) {
+ cl_log(LOG_ERR, "could not create packets");
+ unlink(pidfilename);
+ return EXIT_FAILURE;
+ }
+ for (j=0; j < repeatcount; ++j) {
+ c = send_arp(l, (unsigned char*)device, request);
+ if (c < 0) {
+ break;
+ }
+ mssleep(msinterval / 2);
+ c = send_arp(l, (unsigned char*)device, reply);
+ if (c < 0) {
+ break;
+ }
+ if (j != repeatcount-1) {
+ mssleep(msinterval / 2);
+ }
+ }
#elif defined(HAVE_LIBNET_1_1_API)
- if ((l=libnet_init(LIBNET_LINK, device, errbuf)
Re: [Pacemaker] Problem on creating CIB entry in CRM
Hi, On Wed, Mar 13, 2013 at 09:43:09AM +, Paul Sun wrote: > I have seen some ppl has the problem in the archives, how I can solve this > problem? > > crm(live)# cib new testing > INFO: testing shadow CIB created > ERROR: testing: no such shadow CIB > crm(live)# Are you running this as root? Thanks, Dejan ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Problem on creating CIB entry in CRM
On Wed, Mar 13, 2013 at 10:41:13AM +, Paul Sun wrote: > Hi > > I did not see the post is in the forum. But I found more information on this. > Any idea? I am running Centos6.3 x86_64. > > #crm_shadow -d > Segmentation fault (core dumped) Should probably open a bugzilla for this one. Thanks, Dejan > #rpm -q crmsh > crmsh-1.2.5-55.2.x86_64 > > # rpm -q corosync > corosync-1.4.1-15.el6.x86_64 > > # rpm -q pacemaker > pacemaker-1.1.8-7.el6.x86_64 > > > > -Original Message- > From: Paul Sun > Sent: Wednesday, March 13, 2013 5:43 PM > To: The Pacemaker cluster resource manager > Subject: Problem on creating CIB entry in CRM > > I have seen some ppl has the problem in the archives, how I can solve this > problem? > > crm(live)# cib new testing > INFO: testing shadow CIB created > ERROR: testing: no such shadow CIB > crm(live)# > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [PATCH] change timeouts, startup behaviour ocf:heartbeat:ManageVE (OpenVZ VE cluster resource)
On Tue, Mar 12, 2013 at 12:58:44PM +, Tim Small wrote: > The attached patch changes the behaviour of the OpenVZ virtual machine > cluster resource agent, so that: > > 1. The default resource stop timeout is greater than the hardcoded Just for the record: where is this hardcoded actually? Is it also documented? > timeout in "vzctl stop" (after this time, vzctl forcibly stops the > virtual machine) (since failure to stop a resource can lead to the > cluster node being evicted from the cluster entirely - and this is > generally a BAD thing). Agreed. > 2. The start operation now waits for resource startup to complete i.e. > for the VE to "boot up" (so that the cluster manager can detect VEs > which are hanging on startup, and also throttle simultaneous startups, > so as not-to overburden the node in question). Since the start > operation now does a lot more, the default start operation timeout has > been increased. I'm not sure if we can introduce this just like that. It changes significantly the agent's behaviour. BTW, how does vzctl know when the VE is started? > 3. Backs off the default timeouts and intervals for various operations > to less aggressive values. Please make patches which are self-contained, but can be described in a succinct manner. If the description above matches the code modifications, then there should be three instead of one patch. Please continue the discussion at linux-ha-dev, that's where RA development discussions take place. Cheers, Dejan > > Cheers, > > Tim. > > > n.b. There is a bug in the Debian 6.0 (Squeeze) OpenVZ kernel such that > "vzctl start --wait" hangs. The bug doesn't impact the > OpenVZ.org kernels (and hence won't impact Debian 7.0 Wheezy either). > > -- > South East Open Source Solutions Limited > Registered in England and Wales with company number 06134732. > Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ > VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309 > > --- ManageVE.old 2010-10-22 05:54:50.0 + > +++ ManageVE 2013-03-12 11:39:47.895102380 + > @@ -26,12 +26,15 @@ > # > # > # Created 07. Sep 2006 > -# Updated 18. Sep 2006 > +# Updated 12. Mar 2013 > # > -# rev. 1.00.3 > +# rev. 1.00.4 > # > # Changelog > # > +# 12/Mar/13 1.00.4 Wait for VE startup to finish, lengthen default start > timeout. > +# Default stop timeout to longer than the vzctl stop > 'polite' > +# interval. > # 12/Sep/06 1.00.3 more cleanup > # 12/Sep/06 1.00.2 fixed some logic in start_ve > # general cleanup all over the place > @@ -67,7 +70,7 @@ > > > > - 1.00.3 > + 1.00.4 > > > This OCF complaint resource agent manages OpenVZ VEs and thus requires > @@ -87,12 +90,12 @@ > > > > - > - > - > - > - > - > + > + > + > + > + > + > > > END > @@ -127,7 +130,7 @@ > return $retcode >fi > > - $VZCTL start $VEID >& /dev/null > + $VZCTL start $VEID --wait >& /dev/null >retcode=$? > >if [[ $retcode != 0 && $retcode != 32 ]]; then > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Problem on creating CIB entry in CRM
Hi I did not see the post is in the forum. But I found more information on this. Any idea? I am running Centos6.3 x86_64. #crm_shadow -d Segmentation fault (core dumped) #rpm -q crmsh crmsh-1.2.5-55.2.x86_64 # rpm -q corosync corosync-1.4.1-15.el6.x86_64 # rpm -q pacemaker pacemaker-1.1.8-7.el6.x86_64 -Original Message- From: Paul Sun Sent: Wednesday, March 13, 2013 5:43 PM To: The Pacemaker cluster resource manager Subject: Problem on creating CIB entry in CRM I have seen some ppl has the problem in the archives, how I can solve this problem? crm(live)# cib new testing INFO: testing shadow CIB created ERROR: testing: no such shadow CIB crm(live)# ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
pacemaker@oss.clusterlabs.org
Andrew Beekhof writes: > > On Wed, Mar 13, 2013 at 5:55 PM, matonb wrote: > > Andrew Beekhof writes: > > > >> > >> On Wed, Mar 13, 2013 at 3:59 AM, matonb wrote: > >> > Hi List, > >> > > >> > I've just upgraded a CentOS 6.3 server to 6.4, other than the > > disappearance > >> > of the crm shell tools, one thing I've noticed which is a minor annoyance > >> > rather than a problem is that users which are members of the haclient > > group > >> > can't use the crm tools any more: > > > > The 6.3 RPMS came from the CentOS base repository, any user that was a member > > of the haclient group could execute and connect to the cluster using commands > > such as crm_mon (the most frequently used). > > Ah, thats not the ACLs Lars was talking about. > What you're talking about should still work, nothing should have > changed in that area between 6.3 and 6.4. > I will investigate. Thanks :-) I think the ACL's got roped in because I tried to implement them to solve the problem. Which as you've both mentioned aren't in the release I'm using. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [openais]when openais disappear
On 03/13/2013 05:46 PM, Andrew Beekhof wrote: On Wed, Mar 13, 2013 at 8:13 PM, zhuyj wrote: hi, all I have a problem. When does openais disappear? who replace the function of openais? pacemaker or corosync? The interesting parts were spun off to create corosync. The SAF APIs were deemed to be not very useful and set on a course to be deprecated. Hi, thanks for your reply. I have a problem. How does pacemaker manage resource ? I mean that how pacemaker cleanup resource when resource is obsolete. Thanks Zhuyj ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [openais]when openais disappear
On Wed, Mar 13, 2013 at 8:13 PM, zhuyj wrote: > hi, all > > I have a problem. When does openais disappear? who replace the function of > openais? pacemaker or corosync? The interesting parts were spun off to create corosync. The SAF APIs were deemed to be not very useful and set on a course to be deprecated. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] Problem on creating CIB entry in CRM
I have seen some ppl has the problem in the archives, how I can solve this problem? crm(live)# cib new testing INFO: testing shadow CIB created ERROR: testing: no such shadow CIB crm(live)# ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] [openais]when openais disappear
hi, all I have a problem. When does openais disappear? who replace the function of openais? pacemaker or corosync? Thanks a lot. Zhuyj ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [pacemaker][openais]the intention of /etc/init.d/openais stop
Hi, I have another problem. https://bugzilla.redhat.com/show_bug.cgi?id=706289 how to fix it? Thanks a lot. Zhuyj On 03/13/2013 04:45 PM, Andrew Beekhof wrote: Thats a package version, not the name of a distribution (eg. fedora) On Wed, Mar 13, 2013 at 4:30 PM, zhuyj wrote: openais-1.1.4 On 03/13/2013 08:47 AM, Andrew Beekhof wrote: Which distro is this? On Tue, Mar 12, 2013 at 2:05 PM, zhuyj wrote: Hi, all I am using the linux cluster. When I run "/etc/init.d/openais stop", I found that it just checks the status of corosync, if corosync exists, then it will return. Who can tell me why? openais does not make corosync exit? Thanks a lot. Zhu Yanjun ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] [pacemaker][openais]the intention of /etc/init.d/openais stop
Thats a package version, not the name of a distribution (eg. fedora) On Wed, Mar 13, 2013 at 4:30 PM, zhuyj wrote: > openais-1.1.4 > > > > On 03/13/2013 08:47 AM, Andrew Beekhof wrote: >> >> Which distro is this? >> >> On Tue, Mar 12, 2013 at 2:05 PM, zhuyj wrote: >>> >>> Hi, all >>> >>> I am using the linux cluster. When I run "/etc/init.d/openais stop", I >>> found >>> that >>> it just checks the status of corosync, if corosync exists, then it will >>> return. >>> >>> Who can tell me why? openais does not make corosync exit? >>> >>> Thanks a lot. >>> Zhu Yanjun >>> >>> ___ >>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>> >>> Project Home: http://www.clusterlabs.org >>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>> Bugs: http://bugs.clusterlabs.org >> >> ___ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> > ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
pacemaker@oss.clusterlabs.org
On Wed, Mar 13, 2013 at 5:55 PM, matonb wrote: > Andrew Beekhof writes: > >> >> On Wed, Mar 13, 2013 at 3:59 AM, matonb wrote: >> > Hi List, >> > >> > I've just upgraded a CentOS 6.3 server to 6.4, other than the > disappearance >> > of the crm shell tools, one thing I've noticed which is a minor annoyance >> > rather than a problem is that users which are members of the haclient > group >> > can't use the crm tools any more: >> >> "any more"? >> > > The 6.3 RPMS came from the CentOS base repository, any user that was a member > of the haclient group could execute and connect to the cluster using commands > such as crm_mon (the most frequently used). Ah, thats not the ACLs Lars was talking about. What you're talking about should still work, nothing should have changed in that area between 6.3 and 6.4. I will investigate. > With 6.4, only root and the > hacluster user can connect... > >> Where did you get your 6.3 rpms? >> Because ACL support was not enabled in 6.3 (or earlier versions) either. > > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
