[Pacemaker] unmanaged resource - cluster influence - ocf:heartbeat:Filesystem
Hello, I'm using ocf:heartbeat:Filesystem to mount a cifs share. Additionally I enabled OCF_CHECK_LEVEL 20 to read/write from the cifs-share during monitor operation: If I block the connection to the cifs-server with iptables, the monitor operation times out. After several tries, a restart of the resource is initiated. The resource fails to stop (another timeout) so it ends up in a INFINITY and the resource is unmanaged: Jun 17 13:49:21 node1 lrmd: [15029]: WARN: p_cifs_pictures:monitor process (PID 18444) timed out (try 1). Killing with signal SIGTERM (15). Jun 17 13:49:21 node1 lrmd: [15029]: WARN: operation monitor[43] on p_cifs_pictures for client 15032: pid 18444 timed out Jun 17 13:49:21 node1 Filesystem2[18750]: INFO: Running stop for //cifs/share/pictures on /srv/cifs/pictures Jun 17 13:49:21 node1 Filesystem2[18750]: INFO: Trying to unmount /srv/cifs/pictures Jun 17 13:49:41 node1 lrmd: [15029]: WARN: p_cifs_pictures:stop process (PID 18750) timed out (try 1). Killing with signal SIGTERM (15). Jun 17 13:49:41 node1 crmd: [15032]: WARN: status_from_rc: Action 5 (p_cifs_pictures_stop_0) on node1 failed (target: 0 vs. rc: -2): Error Jun 17 13:49:41 node1 crmd: [15032]: WARN: update_failcount: Updating failcount for p_cifs_pictures on node1 after failed stop: rc=-2 (update=INFINITY, time=1403005781) Jun 17 13:49:41 node1 pengine: [15031]: WARN: common_apply_stickiness: Forcing p_cifs_pictures away from node1 after 100 failures (max=100) So far so bad. How can I avoid a timeout during the recover? I mean what is the read/write check all about if it leaves the resource unmanaged at the end? I fully understand, that if the resource is not securely shut down and stonith is not active, it should be unmanaged. Thank you. Stefan ___ 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] first monitor action after start of ressource fails - ends up in ressource restart
-Ursprüngliche Nachricht- Von: Andrew Beekhof [mailto:and...@beekhof.net] Sounds like apache is saying done for the start action before its actually started. I believe more recent versions of the agent behave correctly. I have now set start-delay=5 in the resource section. Seems to fix it. Is this a legitimate use for this parameter? Stefan ___ 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] first monitor action after start of ressource fails - ends up in ressource restart
Dear Users/Developers, I'm running a pacemaker/corosync cluster on Debian 7: Pacemaker 1.1.7.1 Corosync 1.4.2-3 Everything is smooth but the first monitor action after the start action on my apache2 ressource fails - hence it ends up in a restart. How can this be avoided? Log attached. Thanks Stefan Jun 17 08:16:49 node1 crmd: [5544]: info: te_rsc_command: Initiating action 41: start p_apache_start_0 on node1 (local) Jun 17 08:16:49 node1 lrmd: [5541]: info: rsc:p_apache start[32] (pid 19175) Jun 17 08:16:49 node1 lrmd: [5541]: info: RA output: (p_apache:start:stdout) Starting web server: apache2 Jun 17 08:16:49 node1 lrmd: [5541]: info: RA output: (p_apache:start:stdout) . Jun 17 08:16:49 node1 lrmd: [5541]: info: operation start[32] on p_apache for client 5544: pid 19175 exited with return code 0 Jun 17 08:16:49 node1 crmd: [5544]: info: process_lrm_event: LRM operation p_apache_start_0 (call=32, rc=0, cib-update=58, confirmed=true) ok Jun 17 08:16:49 node1 crmd: [5544]: info: te_rsc_command: Initiating action 42: monitor p_apache_monitor_1 on node1 (local) Jun 17 08:16:49 node1 lrmd: [5541]: info: rsc:p_apache monitor[33] (pid 19224) Jun 17 08:16:49 node1 lrmd: [5541]: info: operation monitor[33] on p_apache for client 5544: pid 19224 exited with return code 7 (mapped from 3) Jun 17 08:16:49 node1 crmd: [5544]: info: process_lrm_event: LRM operation p_apache_monitor_1 (call=33, rc=7, cib-update=59, confirmed=false) not running Jun 17 08:16:49 node1 crmd: [5544]: WARN: status_from_rc: Action 42 (p_apache_monitor_1) on node1 failed (target: 0 vs. rc: 7): Error Jun 17 08:16:49 node1 crmd: [5544]: WARN: update_failcount: Updating failcount for p_apache on node1 after failed monitor: rc=7 (update=value++, time=1402985809) Jun 17 08:16:49 node1 crmd: [5544]: info: abort_transition_graph: match_graph_event:277 - Triggered transition abort (complete=0, tag=lrm_rsc_op, id=p_apache_last_failure_0, magic=0:7;42:0:0:2b25e917-fb1e-45fa-a377-2c08f4a76d26, cib=0.199.104) : Event failed Jun 17 08:16:49 node1 attrd: [5542]: notice: attrd_trigger_update: Sending flush op to all hosts for: fail-count-p_apache (1) Jun 17 08:16:49 node1 attrd: [5542]: notice: attrd_perform_update: Sent update 27: fail-count-p_apache=1 Jun 17 08:16:49 node1 attrd: [5542]: notice: attrd_trigger_update: Sending flush op to all hosts for: last-failure-p_apache (1402985809) Jun 17 08:16:49 node1 crmd: [5544]: info: abort_transition_graph: te_update_diff:176 - Triggered transition abort (complete=0, tag=nvpair, id=status-node1-fail-count-p_apache, name=fail-count-p_apache, value=1, magic=NA, cib=0.199.105) : Transient attribute: update Jun 17 08:16:49 node1 attrd: [5542]: notice: attrd_perform_update: Sent update 30: last-failure-p_apache=1402985809 Jun 17 08:16:49 node1 crmd: [5544]: info: abort_transition_graph: te_update_diff:176 - Triggered transition abort (complete=0, tag=nvpair, id=status-node1-last-failure-p_apache, name=last-failure-p_apache, value=1402985809, magic=NA, cib=0.199.106) : Transient attribute: update Jun 17 08:16:49 node1 pengine: [5543]: WARN: unpack_rsc_op: Processing failed op p_apache_last_failure_0 on node1: not running (7) Jun 17 08:16:49 node1 pengine: [5543]: notice: common_apply_stickiness: p_apache can fail 99 more times on node2 before being forced off Jun 17 08:16:49 node1 pengine: [5543]: notice: common_apply_stickiness: p_apache can fail 99 more times on node1 before being forced off Jun 17 08:16:49 node1 pengine: [5543]: notice: LogActions: Recover p_apache#011(Started node1) Jun 17 08:16:49 node1 crmd: [5544]: info: te_rsc_command: Initiating action 2: stop p_apache_stop_0 on node1 (local) Jun 17 08:16:49 node1 lrmd: [5541]: info: cancel_op: operation monitor[33] on p_apache for client 5544, its parameters: crm_feature_set=[3.0.6] depth=[0] CRM_meta_name=[monitor] CRM_meta_interval=[1] CRM_meta_timeout=[2] CRM_meta_depth=[0] cancelled Jun 17 08:16:49 node1 lrmd: [5541]: info: rsc:p_apache stop[36] (pid 19258) Jun 17 08:16:49 node1 crmd: [5544]: info: process_lrm_event: LRM operation p_apache_monitor_1 (call=33, status=1, cib-update=0, confirmed=true) Cancelled Jun 17 08:16:49 node1 lrmd: [5541]: info: RA output: (p_apache:stop:stdout) Stopping web server: apache2 Jun 17 08:16:49 node1 lrmd: [5541]: info: RA output: (p_apache:stop:stdout) ... waiting Jun 17 08:16:50 node1 lrmd: [5541]: info: RA output: (p_apache:stop:stdout) . Jun 17 08:16:50 node1 lrmd: [5541]: info: operation stop[36] on p_apache for client 5544: pid 19258 exited with return code 0 Jun 17 08:16:50 node1 crmd: [5544]: info: process_lrm_event: LRM operation p_apache_stop_0 (call=36, rc=0, cib-update=64, confirmed=true) ok Jun 17 08:16:50 node1 crmd: [5544]: info: te_rsc_command: Initiating action 46: start p_apache_start_0 on node1 (local) Jun 17 08:16:50 node1 lrmd: [5541]: info: rsc:p_apache start[37] (pid 19282) Jun 17 08:16:50 node1 lrmd: [5541]: info: RA
[Pacemaker] display order in crm_mon output
Hi List, we've recovered a cluster after a failure and used a previously exported cib.xml. Everything is back to normal state. The strange thing is, that the order in the output of crm_mon is not like before. Can anyone bring some light into this please? What is affecting the order of the displayed ressources? Can we rearrange it somehow? Before the failure: Resource Group: cluster1 p_bond0(ocf::heartbeat:IPaddr2): Started node1 p_vlan100 (ocf::heartbeat:IPaddr2): Started node1 p_vlan200 (ocf::heartbeat:IPaddr2): Started node1 p_route (ocf::heartbeat:Route): Started node1 p_conntrackd (lsb:conntrackd-sync): Started node1 Clone Set: pingclone [p_ping] Started: [ node1 ] Stopped: [ p_ping:1 ] p_vpn_B (ocf::heartbeat:anything): Started node1 p_vpn_C(ocf::heartbeat:anything): Started node1 p_vpn_H(ocf::heartbeat:anything): Started node1 p_vpn_K(ocf::heartbeat:anything): Started node1 p_vpn_L1 (ocf::heartbeat:anything): Started node1 p_vpn_LS (ocf::heartbeat:anything): Started node1 p_vpn_M(ocf::heartbeat:anything): Started node1 After the recovery: p_vpn_H(ocf::heartbeat:anything): Started node1 p_vpn_K(ocf::heartbeat:anything): Started node1 p_vpn_L1 (ocf::heartbeat:anything): Started node1 p_vpn_LS (ocf::heartbeat:anything): Started node1 p_vpn_M(ocf::heartbeat:anything): Started node1 Resource Group: cluster1 p_bond(ocf::heartbeat:IPaddr2): Started node1 p_vlan100 (ocf::heartbeat:IPaddr2): Started node1 p_vlan200 (ocf::heartbeat:IPaddr2): Started node1 p_route (ocf::heartbeat:Route): Started node1 p_conntrackd (lsb:conntrackd-sync): Started node1 Clone Set: pingclone [p_ping] Started: [ node1 ] Stopped: [ p_ping:1 ] p_vpn_B (ocf::heartbeat:anything): Started node1 p_vpn_C(ocf::heartbeat:anything): Started node1 Stefan ___ 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] Howto check if the current node is active?
Hi Jorge, that looks good. Thank you! Stefan Von: Jorge Armando Medina [mailto:jmed...@qindel.com] Gesendet: Dienstag, 7. Januar 2014 18:49 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] Howto check if the current node is active? We used this in a postgres cluster # Run drbdadm verify every saturday 3 am 00 03 * * 06 root [ $(/usr/sbin/crm_resource -Q -r g_postgres -W ) = $(hostname) ] /sbin/drbdadm verify all I hope you can use it. ___ 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] Howto check if the current node is active?
Hi Folks! How can i check if the current node i'm connected to is the active? It should be parseable because i want to use it in a script. We want to use this to trigger a cronjob on the active. Stefan ___ 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] pcs ping connectivity rule
May i ask, how your configuration snippet look like? Thank you Stefan -Ursprüngliche Nachricht- Von: Martin Ševčík [mailto:sev...@esys.cz] Gesendet: Freitag, 6. Dezember 2013 12:26 An: pacemaker@oss.clusterlabs.org Betreff: Re: [Pacemaker] pcs ping connectivity rule I installed crmsh and configured it via crm commands. best regards, m. ___ 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] Ressources not moving to node with better connectivity - pingd
Hi List, even though following well known documentations about a ping clone resource my resources are not moving to the node with the better connectivity: 2 Nodes configured, 2 expected votes 6 Resources configured. Online: [ debian6-n2 debian6-n1 ] Resource Group: cluster1 p_eth0 (ocf::heartbeat:IPaddr2): Started debian6-n2 p_alias0 (ocf::heartbeat:IPaddr2): Started debian6-n2 p_openvpn (lsb:openvpn): Started debian6-n2 p_conntrackd (lsb:conntrackd-sync): Started debian6-n2 Clone Set: pingclone [p_ping] Started: [ debian6-n1 debian6-n2 ] Node Attributes: * Node debian6-n2: + pingd : 150 : Connectivity is degraded (Expected=300) * Node debian6-n1: + pingd : 300 I would expect the resources to move to N1. Resource-stickiness is set to 100. 2 Pinghosts are configured - n2 can right now only reach a single pinghost. Resource Score Node Stickiness #Fail Migration-Threshold p_alias0 700 debian6-n2 1000 p_alias0 -INFINITY debian6-n1 1000 p_conntrackd 100 debian6-n2 1000 p_conntrackd -INFINITY debian6-n1 1000 p_eth01650 debian6-n2 1000 p_eth0300 debian6-n1 1000 p_openvpn 300 debian6-n2 1000 p_openvpn -INFINITY debian6-n1 1000 p_ping:0 100 debian6-n1 1000 p_ping:0 -INFINITY debian6-n2 1000 p_ping:1 0 debian6-n1 1000 p_ping:1 100 debian6-n2 1000 Anybody see what the problem could be? To be honest I did not fully understood the deeper function of how the scores are calculated. Thank you. Stefan ___ 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] Ressources not moving to node with better connectivity - pingd
Pardon! node debian6-n1 node debian6-n2 primitive p_alias0 ocf:heartbeat:IPaddr2 \ params ip=4.5.6.7 cidr_netmask=24 nic=eth0 \ op start interval=0 timeout=20 \ op stop interval=0 timeout=30 \ op monitor interval=20 primitive p_conntrackd lsb:conntrackd-sync \ op monitor interval=30s primitive p_eth0 ocf:heartbeat:IPaddr2 \ params ip=10.0.2.250 cidr_netmask=24 nic=eth0 \ op start interval=0 timeout=20 \ op stop interval=0 timeout=30 \ op monitor interval=20 primitive p_openvpn lsb:openvpn \ op start interval=0 timeout=20 \ op stop interval=0 timeout=30 \ op monitor interval=20 primitive p_ping ocf:pacemaker:ping \ params host_list=7.4.5.6 127.0.0.1 multiplier=150 dampen=5s \ op start interval=0 timeout=60 \ op stop interval=0 timeout=20 \ op monitor interval=20 timeout=60 group cluster1 p_eth0 p_alias0 p_openvpn p_conntrackd \ meta target-role=Started clone pingclone p_ping \ meta interleave=true location groupwithping cluster1 \ rule $id=groupwithping-rule pingd: defined pingd colocation cluster inf: p_eth0 p_alias0 p_openvpn p_conntrackd property $id=cib-bootstrap-options \ dc-version=1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff \ cluster-infrastructure=openais \ expected-quorum-votes=2 \ no-quorum-policy=ignore \ stonith-enabled=false rsc_defaults $id=rsc-options \ resource-stickiness=100 Stefan Von: emmanuel segura [mailto:emi2f...@gmail.com] Gesendet: Montag, 9. Dezember 2013 11:22 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] Ressources not moving to node with better connectivity - pingd where is your config? 2013/12/9 Bauer, Stefan (IZLBW Extern) stefan.ba...@iz.bwl.demailto:stefan.ba...@iz.bwl.de Hi List, even though following well known documentations about a ping clone resource my resources are not moving to the node with the better connectivity: 2 Nodes configured, 2 expected votes 6 Resources configured. Online: [ debian6-n2 debian6-n1 ] Resource Group: cluster1 p_eth0 (ocf::heartbeat:IPaddr2): Started debian6-n2 p_alias0 (ocf::heartbeat:IPaddr2): Started debian6-n2 p_openvpn (lsb:openvpn): Started debian6-n2 p_conntrackd (lsb:conntrackd-sync): Started debian6-n2 Clone Set: pingclone [p_ping] Started: [ debian6-n1 debian6-n2 ] Node Attributes: * Node debian6-n2: + pingd : 150 : Connectivity is degraded (Expected=300) * Node debian6-n1: + pingd : 300 I would expect the resources to move to N1. Resource-stickiness is set to 100. 2 Pinghosts are configured - n2 can right now only reach a single pinghost. Resource Score Node Stickiness #Fail Migration-Threshold p_alias0 700 debian6-n2 1000 p_alias0 -INFINITY debian6-n1 1000 p_conntrackd 100 debian6-n2 1000 p_conntrackd -INFINITY debian6-n1 1000 p_eth01650 debian6-n2 1000 p_eth0300 debian6-n1 1000 p_openvpn 300 debian6-n2 1000 p_openvpn -INFINITY debian6-n1 1000 p_ping:0 100 debian6-n1 1000 p_ping:0 -INFINITY debian6-n2 1000 p_ping:1 0 debian6-n1 1000 p_ping:1 100 debian6-n2 1000 Anybody see what the problem could be? To be honest I did not fully understood the deeper function of how the scores are calculated. Thank you. Stefan ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.orgmailto: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
Re: [Pacemaker] Ressources not moving to node with better connectivity - pingd
Hi Michael, so that means, either increasing one value or lower the other right? Or is lowering resource_stickiness the only reasonable way? I tried a multiplier of 1000 but no change in the behavior. Stefan -Ursprüngliche Nachricht- Von: Michael Schwartzkopff [mailto:m...@sys4.de] You resource_stickiness is too high in respect to the pingd points. You resource earns 700 points staying there where it is and only 300 points for moving. Reduce your resource_stickiness to a reasonable amount. BTW: I hope 127.0.0.1 in the config of the ping resource is only for obfuscation on the list and no real configuration. -- Mit freundlichen Grüßen, Michael Schwartzkopff ___ 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] Ressources not moving to node with better connectivity - pingd
Why are some resources listed more than once in the output? What is the difference between group_color and native_color? If a resource has a value of -INFINITY is it because the cluster already decided that this resource should not run on this host or it can not run on this host due to other reasons? I'm not quite sure, how a resource stickiness interferes with the internal decicions taken to migrate. Stefan -Ursprüngliche Nachricht- Von: Michael Schwartzkopff [mailto:m...@sys4.de] Test your config. check the points by # crm_simulate -s -L and adjust your scoring system accordingly. Mit freundlichen Grüßen, ___ 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] Ressources not moving to node with better connectivity - pingd
Thank you for your time! It works now :) Stefan -Ursprüngliche Nachricht- Von: Michael Schwartzkopff [mailto:m...@sys4.de] Gesendet: Montag, 9. Dezember 2013 14:26 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] Ressources not moving to node with better connectivity - pingd Am Montag, 9. Dezember 2013, 13:06:04 schrieb Bauer, Stefan: Why are some resources listed more than once in the output? What is the difference between group_color and native_color? If a resource has a value of -INFINITY is it because the cluster already decided that this resource should not run on this host or it can not run on this host due to other reasons? I'm not quite sure, how a resource stickiness interferes with the internal decicions taken to migrate. Everything is points. stickiness is points. constraints result in points. With every event the cluster calculates the matrix from all nodes and all resources. A resource will run on that node it can collect most points. Beware of impicit constraints that give points. I.e. a colocation col col_A_with_B inf: A B will result in -inf points for the resource B on all nodes where A is not running. Look at the output of crm_simulate -s -L, write down the matrix and understand it. -- Mit freundlichen Grüßen, Michael Schwartzkopff -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein ___ 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] howto group resources without having an order
Hi Michael, i already have your book but i can't find anything related to the way, you define constraint sets like stated here: -- As Lars already noted. Or make a constraint set, as Florian already noted: colocation c-set inf: (OVPN1 OVPN2 ...) myGroup -- What is the behavior of the brackets for example? Stefan ___ 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] howto group resources without having an order
Thank you Michael for pointing that out. I now use colocation cluster inf: (p_openvpn1 p_openvpn2) cluster Now the openvpn resources can be stopped independently - but still depend on ressources from the cluster-group. Is that the expected behavior? I'm a bit confused as I expected the other way around. If the group is (after) openvpn in the list, it should depend on openvpn. Like I would read from left to right. Stefan ___ 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] howto group resources without having an order
Hi, thank you for your input - unfortunately i want to go another path if possible to not not have to change more parts of my configuration: I have setup so far: group cluster1 p_eth0 p_conntrackd location groupwithping cluster1 \ rule id=groupwithping-rule pingd: defined pingd colocation cluster inf: p_eth0 p_conntrackd Now I cannot simply add p_openvpn1 + openvpn2 to the above colocation because then the order is active. Why is colocation even taking care of the order of the resources?! If I change it to: Colocation cluster inf: p_eth0 p_conntrackd p_openvpn1 p_openvpn2 - I cannot start openvpn2 without having openvpn1 up. This is not what I want. Thank you. Stefan -Ursprüngliche Nachricht- Von: Florian Crouzat [mailto:gen...@floriancrouzat.net] Use resources sets (both for ordering[1] and collocation[2]). And play with the value of parameters sequential= and require-all=. ___ 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] howto group resources without having an order
The thing is, that resource sets are not configurable without editing the xml directly. True? Crm configure only knows group order and colocation. Isn't it possible to define an order like: order testorder 0: p_openvpn1 p_openvpn2 and link it to an existing group or colocation? I just don't want to mess with the raw xml files if there are other options. Stefan -Ursprüngliche Nachricht- Von: Florian Crouzat [mailto:gen...@floriancrouzat.net] Gesendet: Dienstag, 26. November 2013 10:32 An: pacemaker@oss.clusterlabs.org Betreff: Re: [Pacemaker] howto group resources without having an order Le 26/11/2013 10:19, Bauer, Stefan (IZLBW Extern) a écrit : Hi, thank you for your input - unfortunately i want to go another path if possible to not not have to change more parts of my configuration: So basically you want to fix your non-working configuration without changing your (non-working) configuration ? Right, that seems reasonnable. I have setup so far: group cluster1 p_eth0 p_conntrackd location groupwithping cluster1 \ rule id=groupwithping-rule pingd: defined pingd colocation cluster inf: p_eth0 p_conntrackd Now I cannot simply add p_openvpn1 + openvpn2 to the above colocation because then the order is active. Why is colocation even taking care of the order of the resources?! No you cannot. If I change it to: Colocation cluster inf: p_eth0 p_conntrackd p_openvpn1 p_openvpn2 - I cannot start openvpn2 without having openvpn1 up. This is not what I want. What you want, I already told you. Thank you. Stefan -- Cheers, Florian Crouzat ___ 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] howto group resources without having an order
Hi Lars, thank you for your answer. I'm not sure, why you think, that p_conntrackd should be started before my interface eth0. I like the idea of linking p_openvpn1 + 2 to cluster1. That should work and I will instantly give it a try. Stefan -Ursprüngliche Nachricht- Von: Lars Marowsky-Bree [mailto:l...@suse.com] This colocation is redundant, since the group already implies it. True. That's not what you want. Also, your colocations are the wrong way around (you want to place p_conntrackd where p_eth0 is, not the other way around). The easiest way is to split them into separate colocations: colocation c-1 inf: p_openvpn1 cluster1 colocation c-2 inf: p_openvpn2 cluster1 ___ 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] howto group resources without having an order
Hi, What does the resource p_eth0 do exactly? - It simply adds an alias ocf:heartbeat:IPadr2 What does the conntractd resource exactly do? netfilter connection tracking. Shouldn't this be master on one node and slave on the other node? - No, that is correct, i handle this with an init-skript, that takes care of the session sync at the correct time. This is working and has been tested. Colocate the openvpn resources with the resource that they really depend on, i.e. the interface. No order collocation needs to be involved, but would be nice. - That sounds good. Best: You tell us what you want to achieve and we tell you how. - Build a openvpn server with 20 vpn tunnels. If one vpn tunnel is not working, restart it - but restart only this openvpn process and not all openvpn processes. (default behavior if openvpn lsb script is in use). I want to setup for each tunnel/configuration an independent resource in the cluster. Stefan ___ 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] howto group resources without having an order
What do you mean by alias. The ocf:heartbeat:IPaddr2 adds a secondary IP address to a interface. - Alias is he original term used from the ocf:heartbeat:IPaddr2 manpage for the function. -Description -This Linux-specific resource manages IP alias IP addresses. It can add an IP alias, or remove one. In addition, it can implement Cluster Alias IP functionality if invoked as a clone resource. As Lars already noted. Or make a constraint set, as Florian already noted: colocation c-set inf: (OVPN1 OVPN2 ...) myGroup - Can you recommend a documentation about howto specify a colocation? What is the function of the ( for example. Stefan ___ 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] howto group resources without having an order
Dear Developers Users, i have 4 resources: p_eth0 p_conntrackd p_openvpn1 p_openvpn2 Right now, I use group and colocation to let p_eth0 and p_conntrackd start in the right order (first eth0, then conntrackd). I want now to also include p_openvpn1 + 2 but not having them in any order. Means - running on the same cluster node but independent from each other. I want to be able to not depend on openvpn1 to start openvpn2 (that's the default behavior iirc without groups/orders). Any help is greatly appreciated. Best regards Stefan ___ 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] Could not initialize corosync configuration API error 2
Dear Developers/Users, we're using Pacemaker 1.1.7 and Corosync Cluster Engine 1.4.2 with Debian 6 and a recent vanilla Kernel (3.10). On quite a lot of our clusters we can not check the ring status anymore: corosync-cfgtool -s returns: Could not initialize corosync configuration API error 2 A reboot is fixing the problem. Even though the status is not returned, i see traffic on the ring interfaces and the cluster is operational. We're using rrp_mode: active with 2 ring interfaces with multicast. Is this a known problem? Does a workaround exist to not force us to reboot the machines regularly ? Any help is greatly appreciated. Regards Stefan Bauer ___ 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] order required if group is present?
Hi List, i have 5 resources configured (p_bond1, p_conntrackd, p_vlan118,p_vlan119, p_openvpn) additionally I have put all of them in a group with: group cluster1 p_bond1,p_vlan118,p_vlan119,p_openvpn,p_conntrackd By this, crm is starting the resources in the order, the group is defined (p_bond1,p_vlan118 and so on...) Is this an expected behavior? If so, it's providing the function `order` was made for? Thanks in advance Stefan ___ 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] order required if group is present?
Hi together, thank you very much for pointing that out. stefan -Ursprüngliche Nachricht- Von: Andrew Beekhof [mailto:and...@beekhof.net] Gesendet: Freitag, 26. Juli 2013 01:24 An: The Pacemaker cluster resource manager Betreff: Re: [Pacemaker] order required if group is present? On 26/07/2013, at 12:59 AM, Andreas Mock andreas.m...@web.de wrote: Hi Stefan, a) yes, the ordered behaviour is intentional. b) In former version you could change this behaviour with an attribute. But this attribute is depreciated in newer versions of pacemaker. c) The solution for parallel starting resources are resource sets. d) groups are essentially a shortcut for a colocation and ordering constraints. ___ 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] commandline option to load cib-file like crm(live)configure: load /tmp/cib
Dear Users, we have prepared a tiny cib-file and want to load it into the cluster on the commandline. It works fine if executed in the crm tool with crm(live)configure: load /tmp/cib How can this be done on the commandline? Keep in mind, that our cib-file is not xml but the crm subshell can handle it anyway. Here is a stanza from /tmp/cib: primitive p_eth0 ocf:heartbeat:IPaddr2 \ params ip=1.2.3.4 cidr_netmask=24 nic=eth0 \ and so on Thank you in advance! Stefan ___ 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] commandline option to load cib-file like crm(live)configure: load /tmp/cib
I was to stupid to read the manpage. Its done like: crm configure load replace /tmp/cib sorry for the trouble! Stefan Von: Bauer, Stefan (IZLBW Extern) [mailto:stefan.ba...@iz.bwl.de] Gesendet: Montag, 10. Juni 2013 13:57 An: pacemaker@oss.clusterlabs.org Betreff: [Pacemaker] commandline option to load cib-file like crm(live)configure: load /tmp/cib Dear Users, we have prepared a tiny cib-file and want to load it into the cluster on the commandline. It works fine if executed in the crm tool with crm(live)configure: load /tmp/cib How can this be done on the commandline? Keep in mind, that our cib-file is not xml but the crm subshell can handle it anyway. Here is a stanza from /tmp/cib: primitive p_eth0 ocf:heartbeat:IPaddr2 \ params ip=1.2.3.4 cidr_netmask=24 nic=eth0 \ and so on Thank you in advance! Stefan ___ 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
