/var/lib/heartbeat/hb_generation
On 11-07-29 04:18 PM, Hai Tao wrote: > where is the hb_generation file ? > > > Thanks. > > Hai Tao > > > >> Date: Fri, 29 Jul 2011 12:11:43 -0700 >> From: david.l...@digitalinsight.com >> To: linux-ha@lists.linux-ha.org >> Subject: Re: [Linux-HA] replace a dead node >> >> the one other thing you may have to do is to change the hb_generation file on >> the new box. sometimes I have needed to do this, other times I have not. >> check >> the log file on both systems when you bring the new box up, if either of them >> complain about the generation number of the other box, shutdown heartbeat on >> the >> new box and copy the file over (or update the value in the file) on the new >> box. >> >> David Lang >> >> >> On Fri, 29 Jul 2011, mike wrote: >> >>> Date: Fri, 29 Jul 2011 16:06:25 -0300 >>> From: mike<mgbut...@nbnet.nb.ca> >>> Reply-To: General Linux-HA mailing list<linux-ha@lists.linux-ha.org> >>> To: General Linux-HA mailing list<linux-ha@lists.linux-ha.org> >>> Subject: Re: [Linux-HA] replace a dead node >>> >>> My first thought (kinda off the cuff really) is this: >>> Create the new server with the same name as the old master >>> Install the HA binaries >>> Copy the ha.cf file from the backup node to the new node >>> Copy the/etc/ha.d/authkeys file form the backup server to the new >>> server. >>> Copy the crm configuration files over, i.e. >>> /var/lib/heartbeat/crm/cib.xml and /var/lib/heartbeat/crm/cib.xml.sig >>> Copy any application related config files over, i.e. apache.conf, >>> /etc/init.d/mysql and so on. >>> Start heartbeat on the new node and it should join in with the cluster >>> unless I missed something. >>> >>> Good luck. Let me know how it goes. I'd be interested in knowing if I >>> missed something. >>> >>> -mgb >>> >>> On 11-07-29 02:47 PM, Hai Tao wrote: >>>> I have a two nodes cluster. The master is dead, and the application has >>>> failed over to the slave now. I need to replace the master with a new >>>> server. The question is, how can I make the current node accept the new >>>> node as its peer, and make a new cluster? >>>> >>>> >>>> Thanks. >>>> >>>> >>>> >>>>> From: taoh...@hotmail.com >>>>> To: linux-ha@lists.linux-ha.org >>>>> Date: Fri, 22 Jul 2011 13:58:55 -0700 >>>>> Subject: Re: [Linux-HA] Does HA monitor its resources? >>>>> >>>>> >>>>> How can I disable HA without stopping the resources then? >>>>> >>>>> I like to disable HA by stopping the heartbeat, but once I do that a >>>>> failover will happen, but I do not want that. >>>>> >>>>> Thanks. >>>>> >>>>> Hai Tao >>>>> >>>>> >>>>> >>>>>> Date: Fri, 22 Jul 2011 17:23:58 -0300 >>>>>> From: mgbut...@nbnet.nb.ca >>>>>> To: linux-ha@lists.linux-ha.org >>>>>> Subject: Re: [Linux-HA] Does HA monitor its resources? >>>>>> >>>>>> It should re-enable it yes. Incidentally, you can set the number of >>>>>> times it will do this in your cib.xml file in /var/lib/heartbeat/crm. >>>>>> >>>>>> For instance, on one of my clusters I only want the resource re-started >>>>>> 3 times. On a fourth failure I want it to do a failover. I set it with >>>>>> this entry in the cib.xml: >>>>>> >>>>>> <nvpair id="nvpair.id17897906" >>>>>> name="default-resource-failure-stickiness" value="500000"/> >>>>>> >>>>>> Hope this helps. >>>>>> >>>>>> -mike >>>>>> >>>>>> >>>>>> On 11-07-22 02:55 PM, Hai Tao wrote: >>>>>>> Does HA monitor its resources? If I manually disable the floating IP, >>>>>>> (for example, ifdown eth0:0), will HA be able to detect that and >>>>>>> re-enable the IP? >>>>>>> >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> Hai Tao >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> _______________________________________________ >>>>> 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 >>>> >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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
