[Linux-HA] Heartbeat IPv6addr OCF
I'm trying to add an IPv6 address to a load balancer cluster. I set up the primitives like so: primitive ip3 ocf:heartbeat:IPv6addr \ params ipv6addr=2600:3c00::0034:c007 nic=eth0:3 \ op monitor interval=5s \ meta target-role=Started primitive ip3arp ocf:heartbeat:SendArp \ params ip=2600:3c00::0034:c007 nic=eth0:3 The resource ip3 will not start, however. It gives me back ip3_start_0 (node=tek-lin-lb1, call=19, rc=6, status=complete): not configured. How can I add an IPv6 primitive? -- View this message in context: http://old.nabble.com/Heartbeat-IPv6addr-OCF-tp35211501p35211501.html Sent from the Linux-HA mailing list archive at Nabble.com. ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
Hello, ipv6addr=2600:3c00::0034:c007 from the manpage of ocf_heartbeat_IPv6addr it looks like that you have to specify the netmask so try: ipv6addr=2600:3c00::0034:c007/64 assuiming that you're in a /64. Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
Thanks for the tip, however, it did not work. That's actually a /116. So I put in 2600:3c00::0034:c007/116 and am getting the same error. I requested that it restart the resource as well, just to make sure it wasn't the previous error. Nick On Sun, Mar 24, 2013 at 3:55 AM, Thomas Glanzmann tho...@glanzmann.dewrote: Hello, ipv6addr=2600:3c00::0034:c007 from the manpage of ocf_heartbeat_IPv6addr it looks like that you have to specify the netmask so try: ipv6addr=2600:3c00::0034:c007/64 assuiming that you're in a /64. Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
Hello Nick Try to use nic=eth0 instead of nic=eth0:3 thanks 2013/3/24 Nick Walke tubaguy50...@gmail.com Thanks for the tip, however, it did not work. That's actually a /116. So I put in 2600:3c00::0034:c007/116 and am getting the same error. I requested that it restart the resource as well, just to make sure it wasn't the previous error. Nick On Sun, Mar 24, 2013 at 3:55 AM, Thomas Glanzmann tho...@glanzmann.de wrote: Hello, ipv6addr=2600:3c00::0034:c007 from the manpage of ocf_heartbeat_IPv6addr it looks like that you have to specify the netmask so try: ipv6addr=2600:3c00::0034:c007/64 assuiming that you're in a /64. Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems -- esta es mi vida e me la vivo hasta que dios quiera ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
Hello Nick, Thanks for the tip, however, it did not work. That's actually a /116. So I put in 2600:3c00::0034:c007/116 and am getting the same error. I requested that it restart the resource as well, just to make sure it wasn't the previous error. now, I had to try it: node $id=9d9b62d2-405d-459a-a724-cb2643d7d9a1 node-62 primitive ipv6test ocf:heartbeat:IPv6addr \ params ipv6addr=2a01:4f8:bb:400::2/64 \ op monitor interval=15 timeout=15 \ meta target-role=Started property $id=cib-bootstrap-options \ dc-version=1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff \ cluster-infrastructure=Heartbeat \ stonith-enabled=false And it works: (node-62) [~] ifconfig eth0 Link encap:Ethernet HWaddr 00:25:90:97:db:b0 inet addr:10.100.4.62 Bcast:10.100.255.255 Mask:255.255.0.0 inet6 addr: 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 Scope:Global inet6 addr: fe80::225:90ff:fe97:dbb0/64 Scope:Link inet6 addr: 2a01:4f8:bb:400::2/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40345 errors:0 dropped:0 overruns:0 frame:0 TX packets:10270 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:52540127 (50.1 MiB) TX bytes:1127817 (1.0 MiB) Memory:fb58-fb60 (infra) [~] traceroute 2a01:4f8:bb:400::2 traceroute to 2a01:4f8:bb:400::2 (2a01:4f8:bb:400::2), 30 hops max, 80 byte packets 1 merlin.glanzmann.de (2a01:4f8:bb:4ff::1) 1.413 ms 1.550 ms 1.791 ms 2 2a01:4f8:bb:400::2 (2a01:4f8:bb:400::2) 0.204 ms 0.202 ms 0.270 ms Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
[Linux-HA] Many Resources Dependent on One Resource Group
I've asked this question on the list before and never received a good answer, so here goes again. I've also read the Pacemaker documentation, but I just cannot seem to get this. I have a drbd resource, p_drbd0. I have a resource group, g_clust01, which consists of a filesystem (p_fs_clust01) and a cluster IP (p_vip, clust01). g_clust01 is dependent on p_drbd0. It can only run where p_drbd0 runs. I want to create 30 separate MySQL resources (p_mysql01 through p_mysql30). All of the mysql resources should be dependent on group g_clust01. They cannot run anywhere that g_clust01 is not running. But the mysql instances should not be dependent on each other. If a node is placed in standby, here's what should happen. 1. All of the mysql instances should be stopped in parallel. 2. resource group g_clust01 should be stopped. 3. drbd resource p_drbd0 should failover to the standby node. 4. resource group g_clust01 should start on the standby node. 5. All of the mysql instances should be started in parallel on the standby. NOTE: We already have all of the above working except the mysql instances. Currently we have the mysql instances as part of group g_clust01, but that causes them to start and stop sequentally. It also makes it so that if you stop a single mysql resource, all of the ones after it are also stopped, which is undesirable. We want to be able to stop and start mysql instances individually, but we want them all dependent on the underlying cluster IP, filesystem, and drbd. Can someone please point me in the right direction? -- Eric Robinson Disclaimer - March 24, 2013 This email and any files transmitted with it are confidential and intended solely for 'General Linux-HA mailing list'. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Many Resources Dependent on One Resource Group
In the simplest terms, we currently have resources: A = drbd B = filesystem C = cluster IP D thru J = mysql instances. Resource group G1 consists of resources B through J, in that order, and is dependent on resource A. This fails over fine, but it has the serious disadvantage that if you stop or remove a mysql resource in the middle of the list, all of the ones after it stop too. For example, if you stop G, then H thru J stop as well. We want to change it so that the resource group G1 consists only of resources B C. All of the mysql instances (D thru J) are individually dependent on group G1, but not dependent on each other. That way you can stop or remove a mysql resource without affecting the others. I saw this scenario described in the Pacemaker docs, but I cannot find an example of the syntax. -- Eric Robinson Disclaimer - March 24, 2013 This email and any files transmitted with it are confidential and intended solely for 'General Linux-HA mailing list'. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
On Sun, 2013-03-24 at 01:36 -0700, tubaguy50035 wrote: params ipv6addr=2600:3c00::0034:c007 nic=eth0:3 \ Are you sure that's a valid IPV6 address? I get headaches every time I look at these, but it seems a valid address is 8 groups, and you've got 5 there. Maybe you mean 2600:3c00::0034:c007? --Greg ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
I don't know what I'm doing wrong then. I copied exactly what you put in and now I'm getting these errors: ipv6test_start_0 (node=tek-lin-lb1, call=25, rc=1, status=complete): unknown error ipv6test_start_0 (node=tek-lin-lb2, call=20, rc=1, status=complete): unknown error Looking in my syslog I see: Mar 24 14:37:13 tek-lin-lb2 IPv6addr: [8038]: ERROR: no valid mecahnisms Mar 24 14:37:13 tek-lin-lb2 lrmd: [3005]: info: operation start[18] on ipv6test for client 3008: pid 8038 exited with return code 1 Mar 24 14:37:13 tek-lin-lb2 crmd: [3008]: info: process_lrm_event: LRM operation ipv6test_start_0 (call=18, rc=1, cib-update=65, confirmed=true) unknown error Anything I need to do to allow IPv6... or something? Nick On Sun, Mar 24, 2013 at 4:29 AM, Thomas Glanzmann tho...@glanzmann.dewrote: Hello Nick, Thanks for the tip, however, it did not work. That's actually a /116. So I put in 2600:3c00::0034:c007/116 and am getting the same error. I requested that it restart the resource as well, just to make sure it wasn't the previous error. now, I had to try it: node $id=9d9b62d2-405d-459a-a724-cb2643d7d9a1 node-62 primitive ipv6test ocf:heartbeat:IPv6addr \ params ipv6addr=2a01:4f8:bb:400::2/64 \ op monitor interval=15 timeout=15 \ meta target-role=Started property $id=cib-bootstrap-options \ dc-version=1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff \ cluster-infrastructure=Heartbeat \ stonith-enabled=false And it works: (node-62) [~] ifconfig eth0 Link encap:Ethernet HWaddr 00:25:90:97:db:b0 inet addr:10.100.4.62 Bcast:10.100.255.255 Mask:255.255.0.0 inet6 addr: 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 Scope:Global inet6 addr: fe80::225:90ff:fe97:dbb0/64 Scope:Link inet6 addr: 2a01:4f8:bb:400::2/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40345 errors:0 dropped:0 overruns:0 frame:0 TX packets:10270 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:52540127 (50.1 MiB) TX bytes:1127817 (1.0 MiB) Memory:fb58-fb60 (infra) [~] traceroute 2a01:4f8:bb:400::2 traceroute to 2a01:4f8:bb:400::2 (2a01:4f8:bb:400::2), 30 hops max, 80 byte packets 1 merlin.glanzmann.de (2a01:4f8:bb:4ff::1) 1.413 ms 1.550 ms 1.791 ms 2 2a01:4f8:bb:400::2 (2a01:4f8:bb:400::2) 0.204 ms 0.202 ms 0.270 ms Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
Hello Nick, Anything I need to do to allow IPv6... or something? I agree with Greg here. Have you tried setting the address manually? ip -6 addr add ip/cidr dev eth0 ip -6 addr show dev eth0 ip -6 addr del ip/cidr dev eth0 ip -6 addr show dev eth0 (node-62) [~] ip -6 addr add 2a01:4f8:bb:400::3/64 dev eth0 (node-62) [~] ip -6 addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2a01:4f8:bb:400::3/64 scope global valid_lft forever preferred_lft forever inet6 2a01:4f8:bb:400::2/64 scope global valid_lft forever preferred_lft forever inet6 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 scope global dynamic valid_lft 2591998sec preferred_lft 604798sec inet6 fe80::225:90ff:fe97:dbb0/64 scope link valid_lft forever preferred_lft forever (node-62) [~] ip -6 addr del 2a01:4f8:bb:400::3/64 dev eth0 (node-62) [~] ip -6 addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2a01:4f8:bb:400::2/64 scope global valid_lft forever preferred_lft forever inet6 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 scope global dynamic valid_lft 2591990sec preferred_lft 604790sec inet6 fe80::225:90ff:fe97:dbb0/64 scope link valid_lft forever preferred_lft forever Do you see a link local address on your eth0? A link local address is one that starts with fe80:: otherwise try loading the ipv6 module: modprobe ipv6 # Don't know if that is the right module name, all my # kernels have ipv6 build in (Debian wheezy / squeeze / backports) Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
From the first node: nick@tek-lin-lb1:~$ sudo ip -6 addr add 2600:3c00::34:c007/116 dev eth0 nick@tek-lin-lb1:~$ sudo ip -6 addr show dev eth0 3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2600:3c00::34:c007/116 scope global valid_lft forever preferred_lft forever inet6 2600:3c00::f03c:91ff:fe70:7541/64 scope global dynamic valid_lft 43200sec preferred_lft 43200sec inet6 2600:3c00::34:c003/64 scope global valid_lft forever preferred_lft forever inet6 fe80::f03c:91ff:fe70:7541/64 scope link valid_lft forever preferred_lft forever nick@tek-lin-lb1:~$ sudo ip -6 addr del 2600:3c00::34:c007/116 dev eth0 nick@tek-lin-lb1:~$ sudo ip -6 addr show dev eth0 3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2600:3c00::f03c:91ff:fe70:7541/64 scope global dynamic valid_lft 43200sec preferred_lft 43200sec inet6 2600:3c00::34:c003/64 scope global valid_lft forever preferred_lft forever inet6 fe80::f03c:91ff:fe70:7541/64 scope link valid_lft forever preferred_lft forever From the second node: nick@tek-lin-lb2:~$ sudo ip -6 addr add 2600:3c00::34:c007/116 dev eth0 nick@tek-lin-lb2:~$ sudo ip -6 addr show dev eth0 3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2600:3c00::34:c007/116 scope global valid_lft forever preferred_lft forever inet6 2600:3c00::f03c:91ff:fe70:f0a4/64 scope global dynamic valid_lft 43190sec preferred_lft 43190sec inet6 2600:3c00::34:c005/64 scope global valid_lft forever preferred_lft forever inet6 fe80::f03c:91ff:fe70:f0a4/64 scope link valid_lft forever preferred_lft forever nick@tek-lin-lb2:~$ sudo ip -6 addr del 2600:3c00::34:c007/116 dev eth0 nick@tek-lin-lb2:~$ sudo ip -6 addr show dev eth0 3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2600:3c00::f03c:91ff:fe70:f0a4/64 scope global dynamic valid_lft 43197sec preferred_lft 43197sec inet6 2600:3c00::34:c005/64 scope global valid_lft forever preferred_lft forever inet6 fe80::f03c:91ff:fe70:f0a4/64 scope link valid_lft forever preferred_lft forever I shouldn't be able to do that if the IPv6 module wasn't loaded, correct? So it seems like it is. Nick On Sun, Mar 24, 2013 at 3:16 PM, Thomas Glanzmann tho...@glanzmann.dewrote: Hello Nick, Anything I need to do to allow IPv6... or something? I agree with Greg here. Have you tried setting the address manually? ip -6 addr add ip/cidr dev eth0 ip -6 addr show dev eth0 ip -6 addr del ip/cidr dev eth0 ip -6 addr show dev eth0 (node-62) [~] ip -6 addr add 2a01:4f8:bb:400::3/64 dev eth0 (node-62) [~] ip -6 addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2a01:4f8:bb:400::3/64 scope global valid_lft forever preferred_lft forever inet6 2a01:4f8:bb:400::2/64 scope global valid_lft forever preferred_lft forever inet6 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 scope global dynamic valid_lft 2591998sec preferred_lft 604798sec inet6 fe80::225:90ff:fe97:dbb0/64 scope link valid_lft forever preferred_lft forever (node-62) [~] ip -6 addr del 2a01:4f8:bb:400::3/64 dev eth0 (node-62) [~] ip -6 addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2a01:4f8:bb:400::2/64 scope global valid_lft forever preferred_lft forever inet6 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 scope global dynamic valid_lft 2591990sec preferred_lft 604790sec inet6 fe80::225:90ff:fe97:dbb0/64 scope link valid_lft forever preferred_lft forever Do you see a link local address on your eth0? A link local address is one that starts with fe80:: otherwise try loading the ipv6 module: modprobe ipv6 # Don't know if that is the right module name, all my # kernels have ipv6 build in (Debian wheezy / squeeze / backports) Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Many Resources Dependent on One Resource Group
On 3/24/13 12:58 PM, Robinson, Eric wrote: In the simplest terms, we currently have resources: A = drbd B = filesystem C = cluster IP D thru J = mysql instances. Resource group G1 consists of resources B through J, in that order, and is dependent on resource A. This fails over fine, but it has the serious disadvantage that if you stop or remove a mysql resource in the middle of the list, all of the ones after it stop too. For example, if you stop G, then H thru J stop as well. We want to change it so that the resource group G1 consists only of resources B C. All of the mysql instances (D thru J) are individually dependent on group G1, but not dependent on each other. That way you can stop or remove a mysql resource without affecting the others. I saw this scenario described in the Pacemaker docs, but I cannot find an example of the syntax. Try adding this to the group: meta ordered=false Or you could take the MySQL instances out of the group and make them each individually dependent on drbd/filesystem with a collocation/order ruleset. Also, you might want to use lrmadmin to set 'max_children' to something more than 4, otherwise it'll only startup 4 MySQL instances at once. Obviously dependent upon how much horsepower you have, but we set it to 32 or 64 (although most of our resources are just IPaddr). ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
Hello Nick, I shouldn't be able to do that if the IPv6 module wasn't loaded, correct? that is correct. I tried modifying my netmask to copy yours. And I get the same error, you do: ipv6test_start_0 (node=node-62, call=6, rc=1, status=complete): unknown error So probably a bug in the resource agent. Manually adding and removing works: (node-62) [~] ip -6 addr add 2a01:4f8:bb:400::2/116 dev eth0 (node-62) [~] ip -6 addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2a01:4f8:bb:400::2/116 scope global valid_lft forever preferred_lft forever inet6 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 scope global dynamic valid_lft 2591887sec preferred_lft 604687sec inet6 fe80::225:90ff:fe97:dbb0/64 scope link valid_lft forever preferred_lft forever (node-62) [~] ip -6 addr del 2a01:4f8:bb:400::2/116 dev eth0 Nick, you can do the following things to resolve this: - Hunt down the bug and fix it or let someone else do it for you - Use another netmask, if possible (fighting the symptoms instead of resolving the root cause) - Write your own resource agent (fighting the symptoms instead of resolving the root cause) Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Heartbeat IPv6addr OCF
This the correct place to report bugs? https://github.com/ClusterLabs/resource-agents Nick On Sun, Mar 24, 2013 at 10:45 PM, Thomas Glanzmann tho...@glanzmann.dewrote: Hello Nick, I shouldn't be able to do that if the IPv6 module wasn't loaded, correct? that is correct. I tried modifying my netmask to copy yours. And I get the same error, you do: ipv6test_start_0 (node=node-62, call=6, rc=1, status=complete): unknown error So probably a bug in the resource agent. Manually adding and removing works: (node-62) [~] ip -6 addr add 2a01:4f8:bb:400::2/116 dev eth0 (node-62) [~] ip -6 addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2a01:4f8:bb:400::2/116 scope global valid_lft forever preferred_lft forever inet6 2a01:4f8:bb:400:225:90ff:fe97:dbb0/64 scope global dynamic valid_lft 2591887sec preferred_lft 604687sec inet6 fe80::225:90ff:fe97:dbb0/64 scope link valid_lft forever preferred_lft forever (node-62) [~] ip -6 addr del 2a01:4f8:bb:400::2/116 dev eth0 Nick, you can do the following things to resolve this: - Hunt down the bug and fix it or let someone else do it for you - Use another netmask, if possible (fighting the symptoms instead of resolving the root cause) - Write your own resource agent (fighting the symptoms instead of resolving the root cause) Cheers, Thomas ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Many Resources Dependent on One Resource Group
meta ordered=false Wouldn't it that make it se we could not be sure that the filesystem and cluster IP start before the MySQL instances? Or you could take the MySQL instances out of the group and make them each individually dependent on drbd/filesystem with a collocation/order ruleset. That would work, but what is the actual syntax? -- Eric Robinson Disclaimer - March 24, 2013 This email and any files transmitted with it are confidential and intended solely for 'David Coulson','General Linux-HA mailing list'. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
