[Linux-HA] unsubscribe

Grabowski, Jürgen Grabowski at kdo.de
Tue May 15 07:11:19 MDT 2007 

unsubscribe 


Mit freundlichen Grüßen
Zweckverband Kommunale Datenverarbeitung Oldenburg (KDO)
Der Verbandsgeschäftsführer



i. A. Jürgen Grabowski
Systemtechniker UNIX
Elsässer Straße 66
26121 Oldenburg
Telefon  0441 9714-238
Telefax  0441 9714-17238
E-Mail   grabowski at kdo.de
Internet http://www.kdo.de 

 



Der Inhalt dieser E-Mail ist vertraulich und ausschließlich für den im Adressfeld bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser E-Mail unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen und diese Mail sowie alle Kopien davon zu vernichten.

 
 
 

-----Ursprüngliche Nachricht-----
Von: linux-ha-bounces at lists.linux-ha.org [mailto:linux-ha-bounces at lists.linux-ha.org] Im Auftrag von linux-ha-request at lists.linux-ha.org
Gesendet: Dienstag, 15. Mai 2007 15:07
An: linux-ha at lists.linux-ha.org
Betreff: Linux-HA Digest, Vol 42, Issue 54

Send Linux-HA mailing list submissions to
	linux-ha at lists.linux-ha.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.linux-ha.org/mailman/listinfo/linux-ha
or, via email, send a message with subject or body 'help' to
	linux-ha-request at lists.linux-ha.org

You can reach the person managing the list at
	linux-ha-owner at lists.linux-ha.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-HA digest..."


Today's Topics:

   1. Re: Remove node from cluster (Max Hofer)
   2. Bonding for High Availability (Jan Kalcic)
   3. Re: Bonding for High Availability (Diego Julian Remolina)
   4. Re: Re: Fwd: Linux-HA Bug report (Dan Gahlinger)
   5. Re: NewToHA2    (Eric Marcus)
   6. What heartbeat version to install now ? (Benjamin Watine)
   7. RE: MySQL Master Master (Benjamin Lawetz)


----------------------------------------------------------------------

Message: 1
Date: Tue, 15 May 2007 12:40:48 +0200
From: Max Hofer <max.hofer at apus.co.at>
Subject: Re: [Linux-HA] Remove node from cluster
To: linux-ha at lists.linux-ha.org
Message-ID: <200705151240.48955.max.hofer at apus.co.at>
Content-Type: text/plain;  charset="ansi_x3.4-1968"

Mariusz, could you please integrate this info in the Wiki?

On Tuesday 15 May 2007, Mariusz Mart wrote:
> Work fine:)
> Thanks
> 
> >>> "Andrew Beekhof" <beekhof at gmail.com> 07-05-15 10:05 >>>
> On 5/12/07, Mariusz Mart <mamart at novell.pl> wrote:
> > Hi!
> >
> > I have 3 node cluster and I would like to remove one node from CRM database. Is there a simple solution for that?
> > I can just stop it and not use, but it will be better if there is no 
> > extra node in hb_gui;)
> 
> you need to stop the node
> then you need to run hb_delnode (i'm not sure of the options) then you 
> need to delete the node from the CIB using
>    cibadmin -D -o nodes -X '<node uname="yournodename"/>'
> and
>    cibadmin -D -o status -X '<node_status uname="yournodename"/>'


------------------------------

Message: 2
Date: Tue, 15 May 2007 11:50:42 +0200
From: Jan Kalcic <jandot at googlemail.com>
Subject: [Linux-HA] Bonding for High Availability
To: General Linux-HA mailing list <linux-ha at lists.linux-ha.org>
Message-ID: <46498272.8000003 at googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi People,

I got my cluster running with heartbeat2 but using haresources file. The resources I've created are IPAddr, drbd and apache but doesn't matter.
What I need is double the network interface eth0 on each machine, create a bond interface on this and then create virtual IPAddr on the the bond interface. Is this possibile?
What I'm looking for is create a High Availability environment in a multiple switch topology network.

Regards,
Jan


------------------------------

Message: 3
Date: Tue, 15 May 2007 07:13:50 -0400
From: Diego Julian Remolina <diego.remolina at ibb.gatech.edu>
Subject: Re: [Linux-HA] Bonding for High Availability
To: General Linux-HA mailing list <linux-ha at lists.linux-ha.org>
Message-ID: <464995EE.5020000 at ibb.gatech.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi Jan,

It is very possible. I do this on a machine running RHEL4. I actually go a step further and do tagged VLANs (802.1q) on top of the bonded interface, so my configuration is like this:

[root at sauron network-scripts]# cat ifcfg-eth0 DEVICE=eth0 ONBOOT=yes BOOTPROTO=none MASTER=bond0 SLAVE=yes USERCTL=no

[root at sauron network-scripts]# cat ifcfg-eth1
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
USERCTL=no

[root at sauron network-scripts]# cat ifcfg-eth2
DEVICE=eth2
ONBOOT=yes
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
USERCTL=no

[root at sauron network-scripts]# cat ifcfg-bond0 DEVICE=bond0 ONBOOT=yes BOOTPROTO=none USERCTL=no

[root at sauron network-scripts]# cat ifcfg-bond0.431
DEVICE=bond0.431
BOOTPROTO=static
ONBOOT=yes
IPADDR=X.Y.131.21
NETMASK=255.255.255.0
TYPE=Ethernet
VLAN=yes

[root at sauron network-scripts]# cat ifcfg-bond0.432
DEVICE=bond0.432
BOOTPROTO=static
ONBOOT=yes
IPADDR=X.Y.132.21
NETMASK=255.255.255.0
TYPE=Ethernet
VLAN=yes

[root at sauron network-scripts]# cat ifcfg-bond0.433
DEVICE=bond0.433
BOOTPROTO=static
ONBOOT=no
IPADDR=X.Y.133.21
NETMASK=255.255.255.0
TYPE=Ethernet
VLAN=yes

For the haresources or cib.xml file you must use the IPaddr2 script for the virtual IPs as shown here (It is of importance to define the different VLANs on top of the bonded interface in my case):

[root at sauron network-scripts]# cat /etc/ha.d/haresources node1_fqdn IPaddr2::X.Y.131.20/24/bond0.431:0  IPaddr2::X.Y.132.20/24/bond0.432:0
IPaddr2::X.Y.133.20/24/bond0.433:0 drbddisk::export Filesystem::/dev/drbd0::/export::ext3::rw,usrquota,grpquota,acl,user_xattr saslauthd cyrus-imapd clamd mimedefang sendmail node2_fqdn IPaddr2::X.Y.131.19/24/bond0.431:0 IPaddr2::X.Y.132.19/24/bond0.432:1
IPaddr2::X.Y.145.133/24/bond0.433:2 drbddisk::web Filesystem::/dev/drbd1::/web::ext3::rw,usrquota,grpquota,acl,user_xattr mysqld httpd

If you have only bonding and use one virtual IP, then the IPaddr script should be enough, since you will only end up having bond0 and bond0:0 as your virtual interface. The need of the IPaddr2 script arises when you need to determine the name of the virtual interfaces so that heartbeat stops and starts the correct virtual IPs correctly.

You must also check your kernel and the bonding modes available for your network cards. Some bonding modes require special switch configurations. Some modes give you better throughput and other modes are oriented towards availability. Check the readme files for the bonding module in your kernel documentation.

HTH,

Diego


Jan Kalcic wrote:
> Hi People,
> 
> I got my cluster running with heartbeat2 but using haresources file. 
> The resources I've created are IPAddr, drbd and apache but doesn't matter.
> What I need is double the network interface eth0 on each machine, 
> create a bond interface on this and then create virtual IPAddr on the 
> the bond interface. Is this possibile?
> What I'm looking for is create a High Availability environment in a 
> multiple switch topology network.
> 
> Regards,
> Jan
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems



------------------------------

Message: 4
Date: Tue, 15 May 2007 08:16:30 -0400
From: "Dan Gahlinger" <dgahling at gmail.com>
Subject: Re: [Linux-HA] Re: Fwd: Linux-HA Bug report
To: "General Linux-HA mailing list" <linux-ha at lists.linux-ha.org>
Message-ID:
	<439b44d10705150516y5a03a418r369a2ff792929f5c at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

how about just 2.0.8.5 ?

Although I suppose it's possible this 2.0.9 that you built will "become" the "real" 2.0.9 at some point?

Dan.

On 5/15/07, Lars Marowsky-Bree <lmb at suse.de> wrote:
>
> On 2007-05-15T10:47:43, Andrew Beekhof <beekhof at gmail.com> wrote:
>
> > In fairness to SUSE, it was solely my doing while I learnt how to 
> > use the openSUSE build service.  The version there isnt an official 
> > SUSE release either.
> >
> > To be honest I didnt know what to call it... 2.0.8 seemed wrong 
> > (since there was an extra 4-5 months development in there) but there 
> > is no real 2.0.9 either... oh well.
>
> Well, the version in mercurial does identify itself as 2.0.9 when build.
> Maybe, to reflect the intermediate state, 2.0.8.999 would have been 
> better.
>
>
> Sincerely,
>     Lars
>
> --
> Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX 
> Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is 
> the name everyone gives to their mistakes." -- Oscar Wilde
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>


------------------------------

Message: 5
Date: Tue, 15 May 2007 08:25:52 -0400
From: "Eric Marcus" <Eric.Marcus at kentcounty.org>
Subject: [Linux-HA] Re: NewToHA2   
To: <linux-ha at lists.linux-ha.org>
Message-ID: <46496EFC.43E6.007B.0 at kentcounty.org>
Content-Type: text/plain; charset=US-ASCII

Hello!   Yes, it was the firewall.  Apparently my IPChains config didn't stick and the FW is off now.    I thought I updated the list but I don't know if I am replying correctly.   Am I supposed to put the Subject in like I am doing on this one and clean up the body a bit like this?     I am plugging along slowly with HA 2.  Its fun working with new stuff and luckily I am being paid to do this!  Now I am having some EVMS issue that is posted in the list.  I also have a call with Novell too.  A two pronged attack to that issue on my part I suppose.  
Thanks for the reply.  

   3. Re: NewToHA2 (Andrew Beekhof)


Message: 3
Date: Tue, 15 May 2007 11:44:20 +0200
From: "Andrew Beekhof" <beekhof at gmail.com>
Subject: Re: [Linux- HA] NewToHA2
To: "General Linux- HA mailing list" <linux- ha at lists.linux- ha.org>
Message- ID:
	<26ef5e70705150244s7a835f0v561287daee3a9d56 at mail.gmail.com>
Content- Type: text/plain; charset=ISO- 8859- 1; format=flowed

its almost always a firewall.

try stopping the firewall completely and see if the problem persists.

On 5/8/07, Eric Marcus <Eric.Marcus at kentcounty.org> wrote:
>
> Hello, I am new to HA2 and am having some configuration issues.   I installed HA2  (2.0.8- 1) on two Suse 10 (SLES10) machines using Alan's Education Project Screencast (http://www.linux- ha.org/Education/Newbie/InstallHeartbeatScreencast)
>
> I think I have a node configuration issue even though it is in ha.cf.   I am very familiar with Novell Cluster Services.   The problem I outline below makes me think that both of the nodes are trying to be the "Master" but I don't how to fix this.  I've spent a week on this and am feeling very stupid!   Here goes.....
>
> My ha.cf file for the 2 servers shows
>
> use_logd yes
> bcast eth1
> node it- mgatedom it- mgatedomc
> crm on
>
>
> The logd.cf shows
>
> logfacility     daemon
>
>
> The authkeys show
>
> auth 1
> 1 sha1 cluster1
>
>
> Now, when I start it up on IT- MGATEDOM,  it shows "done"
>
> crm_mon shows only 1 node configured and after a couple minutes the "Current DC: NONE" becomes "Current DC: it- mgatedom" with 0 resources configured.  It still shows 1 node, not 2.
>
> Then I go to IT- MGATEDOMC to start it up......   It says "done" and when I do a tail /var/log/message I see this
>
>
>
> it- mgatedomc:~ # /etc/init.d/heartbeat start Starting High- 
> Availability services:
>                                                                      
> done
>
> it- mgatedomc:~ # tail /var/log/messages May  8 12:06:16 it- mgatedomc 
> heartbeat: [4514]: info: G_main_add_TriggerHandler:  Added signal 
> manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: 
> G_main_add_TriggerHandler:  Added signal manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Removing /var/run/heartbea t/rsctmp failed, recreating.
> May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP 
> Broadcast heartb eat started on port 694 (694) interface eth1 May  8 
> 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP Broadcast 
> heartb eat closed on port 694 interface eth1 -  Status: 1 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: G_main_add_SignalHandler: Added signal handler for signal 17 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Local status now set to: ' up'
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedom:eth1 up.
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Status update 
> for node it-  mgatedom: status active May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedomc:eth1 up.
> it- mgatedomc:~ # tail /var/log/messages May  8 12:06:16 it- mgatedomc 
> heartbeat: [4514]: info: G_main_add_TriggerHandler:  Added signal 
> manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: 
> G_main_add_TriggerHandler:  Added signal manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Removing /var/run/heartbea t/rsctmp failed, recreating.
> May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP 
> Broadcast heartb eat started on port 694 (694) interface eth1 May  8 
> 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP Broadcast 
> heartb eat closed on port 694 interface eth1 -  Status: 1 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: G_main_add_SignalHandler: Added signal handler for signal 17 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Local status now set to: ' up'
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedom:eth1 up.
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Status update 
> for node it-  mgatedom: status active May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedomc:eth1 up.
> it- mgatedomc:~ # tail /var/log/messages May  8 12:06:16 it- mgatedomc 
> heartbeat: [4514]: info: G_main_add_TriggerHandler:  Added signal 
> manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: 
> G_main_add_TriggerHandler:  Added signal manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Removing /var/run/heartbea t/rsctmp failed, recreating.
> May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP 
> Broadcast heartb eat started on port 694 (694) interface eth1 May  8 
> 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP Broadcast 
> heartb eat closed on port 694 interface eth1 -  Status: 1 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: G_main_add_SignalHandler: Added signal handler for signal 17 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Local status now set to: ' up'
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedom:eth1 up.
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Status update 
> for node it-  mgatedom: status active May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedomc:eth1 up.
> it- mgatedomc:~ # tail /var/log/messages May  8 12:06:16 it- mgatedomc 
> heartbeat: [4514]: info: G_main_add_TriggerHandler:  Added signal 
> manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: 
> G_main_add_TriggerHandler:  Added signal manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Removing /var/run/heartbea t/rsctmp failed, recreating.
> May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP 
> Broadcast heartb eat started on port 694 (694) interface eth1 May  8 
> 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP Broadcast 
> heartb eat closed on port 694 interface eth1 -  Status: 1 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: G_main_add_SignalHandler: Added signal handler for signal 17 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Local status now set to: ' up'
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedom:eth1 up.
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Status update 
> for node it-  mgatedom: status active May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedomc:eth1 up.
> it- mgatedomc:~ # tail /var/log/messages May  8 12:06:16 it- mgatedomc 
> heartbeat: [4514]: info: G_main_add_TriggerHandler:  Added signal 
> manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: 
> G_main_add_TriggerHandler:  Added signal manual handler May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Removing /var/run/heartbea t/rsctmp failed, recreating.
> May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP 
> Broadcast heartb eat started on port 694 (694) interface eth1 May  8 
> 12:06:16 it- mgatedomc heartbeat: [4514]: info: glib: UDP Broadcast 
> heartb eat closed on port 694 interface eth1 -  Status: 1 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: G_main_add_SignalHandler: Added signal handler for signal 17 May  8 12:06:16 it- mgatedomc heartbeat: [4514]: info: Local status now set to: ' up'
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedom:eth1 up.
> May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Status update 
> for node it-  mgatedom: status active May  8 12:06:17 it- mgatedomc heartbeat: [4514]: info: Link it- mgatedomc:eth1 up.
> it- mgatedomc:~ # tail /var/log/messages May  8 12:07:06 it- mgatedomc 
> heartbeat: [4514]: debug: hist- >ackseq =0 May  8 12:07:06 it- 
> mgatedomc heartbeat: [4514]: debug: hist- >lowseq =0, hist- >hi 
> seq=103 May  8 12:07:06 it- mgatedomc heartbeat: [4514]: debug: 
> expecting from it- mgatedo m May  8 12:07:06 it- mgatedomc heartbeat: 
> [4514]: debug: it's ackseq=0 May  8 12:07:06 it- mgatedomc heartbeat: [4514]: debug:
> May  8 12:07:06 it- mgatedomc heartbeat: [4514]: debug: hist- >ackseq 
> =0 May  8 12:07:06 it- mgatedomc heartbeat: [4514]: debug: hist- 
> >lowseq =0, hist- >hi seq=104 May  8 12:07:06 it- mgatedomc heartbeat: 
> [4514]: debug: expecting from it- mgatedo m May  8 12:07:06 it- 
> mgatedomc heartbeat: [4514]: debug: it's ackseq=0 May  8 12:07:06 it- mgatedomc heartbeat: [4514]: debug:
>
>
>
> The line that says "expecting from it- mgatedom" confuses me.
>
> crm_mon shows "Not Connected".
>
> netstat - n - l | grep 694 shows that udp 694 is there.
>
> The strange thing is if I stop both of them and start it on IT- MGATEDOMC first, then it will come up just fine and then when I start it on IT- MGATEDOM, it has the above issue.
>
> Any ideas?
>
> Thank you,
> Eric...
>
> _______________________________________________
> Linux- HA mailing list
> Linux- HA at lists.linux- ha.org
> http://lists.linux- ha.org/mailman/listinfo/linux- ha See also: 
> http://linux- ha.org/ReportingProblems
>



------------------------------

Message: 6
Date: Tue, 15 May 2007 14:55:29 +0200
From: Benjamin Watine <watine at cines.fr>
Subject: [Linux-HA] What heartbeat version to install now ?
To: General Linux-HA mailing list <linux-ha at lists.linux-ha.org>
Message-ID: <4649ADC1.5080809 at cines.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi

I'm about to install Heartbeat on a fresh Debian 4 system, and I was wondering wich version of heartbeat I should install ?
Some bugs have been corrected since v2.0.8, and I would like to install these corrections too. So should I install v2.0.8 and apply the patches that I want, or install the latest development version ?

If you think there's no major problem installing latest snapshot, where can I find it ? here ? : http://hg.linux-ha.org/dev/archive/tip.tar.bz2
Any other version to suggest ?

Thanks in advance.

Benjamin


------------------------------

Message: 7
Date: Tue, 15 May 2007 09:06:53 -0400
From: "Benjamin Lawetz" <blawetz at teliphone.ca>
Subject: RE: [Linux-HA] MySQL Master Master
To: "'General Linux-HA mailing list'" <linux-ha at lists.linux-ha.org>
Message-ID: <011501c796f1$e89c2360$dededede at benthos>
Content-Type: text/plain;	charset="US-ASCII"

Hi Markus,

	If I recall you need to reset the failed resource after you manually clean it up. Your monitor failed, couldn't restart it, heartbeat determines there is a problem with this resource on this node that it cannot do anything to fix. You have to manually fix it and then reset the failed resource.

>From the http://www.linux-ha.org/v2/AdminTools/crm_resource page

12. Resetting a failed resource after having been manually cleaned up
	crm_resource -C -H c001n02 -r my_frist_ip


> -----Original Message-----
> From: linux-ha-bounces at lists.linux-ha.org
> [mailto:linux-ha-bounces at lists.linux-ha.org] On Behalf Of Markus W.
> Sent: May 15, 2007 6:39 AM
> To: General Linux-HA mailing list
> Subject: Re: [Linux-HA] MySQL Master Master
> 
> Starting from scratch:
> 
> OS: Linux, RHEL 4, Kernel 2.6.9-55.EL
> HA: RPM Installation from
> http://dev.centos.org/centos/4/testing/i386/RPMS/heartbeat-2.0
> .8-2.el4.centos
> 
> Configuration, Log, Cibadmin Files: see Attachements
>  - xx.xx.xx.xx: Ping IP
>  - yy.yy.yy.yy: Cluster IP
>  - zz.zz.zz.zz: Cluster Broadcast
> 
> Problem:
> Edit /etc/init.d/httpd on node 1 to return 1 on startup (simulate 
> error) Stop httpd on node1 => heartbeat try to restart httpd on node 1 
> (fail)  => httpd or the group Web failover to node2 Reset 
> /etc/init.d/httpd on node 1 to normal behaviour Start httpd on node1 
> Set node2 in standby mode => heartbeat wont failback to node1
> 
> Best regards,
> 
> Markus
> 
> Dejan Muhamedagic schrieb:
> > On Mon, May 14, 2007 at 11:01:16AM +0200, Markus W. wrote:
> >   
> >> Ok, I understand nothing. I have the same problem with apache like 
> >> mysql. If apache run on the first node and something goes wrong on 
> >> that node apache would switch to the second node - great.
> Apache wont
> >> failback to the first node if I repair the first node and
> switch the
> >> second node into standby mode - bad.
> >>     
> >
> > With default settings, resources should move back to their
> preferred
> > node, once that one is live again. You'd probably want to post the 
> > logs and the configuration. See
> http://linux-ha.org/ReportingProblems
> >
> >   
> >> Anywhere on the ha "universe" page there was an
> information about this. 
> >> But I don't understand why heartbeat dont try the first node just 
> >> once again. If the first node is ok why heartbeat shouln'd
> move the
> >> resource back to the first node? Ok, if the first node
> isn't ok again
> >> I would understand heartbeat is given up to run the
> resource anywhere.
> >>
> >> Thanks
> >>
> >> Benjamin Lawetz schrieb:
> >>     
> >>> I have a vague impression that you might run into
> problems with the
> >>> dummy mysql script. From memory (and one of the gurus here will 
> >>> correct me if I'm
> >>> wrong) heartbeat can call "status" on startup or certain
> occasions.
> >>>
> >>> So having status return an "All OK" when the ressource
> agent should
> >>> not be running might cause unexpected behaviour. You
> might need to
> >>> implement a dummy start and stop and status of just touching or 
> >>> deleting a fake pid file and returning the status
> according to this. 
> >>> You could then implement your function in the monitor part of the 
> >>> script.
> >>>
> >>> But I may be wrong.
> >>>
> >>>  
> >>>       
> >>>> -----Original Message-----
> >>>> From: linux-ha-bounces at lists.linux-ha.org
> >>>> [mailto:linux-ha-bounces at lists.linux-ha.org] On Behalf
> Of Markus W.
> >>>> Sent: May 11, 2007 7:17 AM
> >>>> To: General Linux-HA mailing list
> >>>> Subject: Re: [Linux-HA] MySQL Master Master
> >>>>
> >>>> Hi Benjamin,
> >>>>
> >>>> Wow! It rocks!! Thanks!!!
> >>>>
> >>>> As information the lsb dummy mysql ha script:
> >>>>
> >>>> case "$1" in
> >>>>  start)
> >>>>    exit 0
> >>>>    ;;
> >>>>  stop)
> >>>>    exit 0
> >>>>    ;;
> >>>>  status)
> >>>>    status mysqld
> >>>>    if [ $? -eq "0" ]; then
> >>>>        /usr/sbin/attrd_updater -n mysql_running -d 3s -v 1
> >>>>        exit 0
> >>>>    else
> >>>>        /usr/sbin/attrd_updater -n mysql_running -d 3s -v 0
> >>>>        exit 3
> >>>>    fi
> >>>>    ;;
> >>>>  *)
> >>>>    echo $"Usage: $0 {start|stop|status} (start|stop faked)"
> >>>>    exit 1
> >>>> esac
> >>>>
> >>>> --
> >>>> Markus
> >>>>
> >>>>
> >>>> Benjamin Lawetz schrieb:
> >>>>    
> >>>>         
> >>>>> Hi Markus,
> >>>>>
> >>>>> 	I ran into the same problem. Didn't find any
> better way than to
> >>>>> modify the monitoring script of mysql and add in the case
> >>>>>      
> >>>>>           
> >>>> of a failure:
> >>>>    
> >>>>         
> >>>>> /usr/sbin/attrd_updater -n mysql_running -d 5s -v 0
> >>>>>
> >>>>> And in the case of a success:
> >>>>>
> >>>>> /usr/sbin/attrd_updater -n mysql-mod_running -d 5s -v 1
> >>>>>
> >>>>> The running the monitor script as a clone:
> >>>>>
> >>>>>       <clone id="mysql">
> >>>>>         <instance_attributes id="mysql">
> >>>>>           <attributes>
> >>>>>             <nvpair id="mysql-clone_node_max" 
> name="clone_node_max"
> >>>>> value="1"/>
> >>>>>           </attributes>
> >>>>>         </instance_attributes>
> >>>>>         <primitive id="mysql-child" provider="heartbeat" 
> >>>>>      
> >>>>>           
> >>>> class="ocf"
> >>>>    
> >>>>         
> >>>>> type="mysql">
> >>>>>           <operations>
> >>>>>             <op id="mysql-child-monitor" name="monitor" 
> >>>>>      
> >>>>>           
> >>>> interval="20s"
> >>>>    
> >>>>         
> >>>>> timeout="40s" prereq="nothing">
> >>>>>               <instance_attributes
> id="mysql-child-monitor-attr">
> >>>>>               </instance_attributes>
> >>>>>             </op>
> >>>>>             <op id="mysql-child-start" name="start" 
> >>>>>      
> >>>>>           
> >>>> prereq="nothing"/>
> >>>>    
> >>>>         
> >>>>>           </operations>
> >>>>>         </primitive>
> >>>>>       </clone>
> >>>>>
> >>>>> And then had a constraint:
> >>>>>
> >>>>>       <rsc_location rsc="group_1" id="cli-stop2-group_1">
> >>>>>         <rule score="-INFINITY" id="cli-stop2-rule-group_1">
> >>>>>           <expression operation="lte" value="0" 
> >>>>>      
> >>>>>           
> >>>> id="cli-stop2-expr-group_1"
> >>>>    
> >>>>         
> >>>>> attribute="mysql_running"/>
> >>>>>         </rule>
> >>>>>       </rsc_location>
> >>>>>
> >>>>> This will run the monitor on every node and set the score
> >>>>>      
> >>>>>           
> >>>> to -INFINITY
> >>>>    
> >>>>         
> >>>>> for the node where mysql fails.
> >>>>>
> >>>>> If mysql comes back online though, the "mysql_running" will
> >>>>>      
> >>>>>           
> >>>> be set to "1"
> >>>>    
> >>>>         
> >>>>> but I don't think it will trigger a recalculation of
> the scores. 
> >>>>> Haven't figured out yet how to cause this.
> >>>>>
> >>>>>
> >>>>> Hope this helps
> >>>>>  
> >>>>>      
> >>>>>           
> >>>> _______________________________________________
> >>>> Linux-HA mailing list
> >>>> Linux-HA at 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 at 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 at 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 at lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

End of Linux-HA Digest, Vol 42, Issue 54
****************************************

More information about the Linux-HA mailing list