Re: [Linux-HA] How do I remove a -INFINITY score?

2008-07-24 Thread Raghuram Bondalapati
Nick, when i had a similar issue before, Andrew siggested using crm_resource -D. Can you try that and see if that resets the -INFINITY score. --Raghu On 7/24/08, Nick <[EMAIL PROTECTED]> wrote: > > I have a cluster in master/slave setup running on CentOS 5.1 > (heartbeat-2.1.3-3.el5) with apache

Re: [Linux-HA] fail-count-resource not getting incremented

2008-07-10 Thread Raghuram Bondalapati
I tried that, but it did not work. --Raghu On 7/9/08, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > > On Wed, Jul 9, 2008 at 19:47, Raghuram Bondalapati > <[EMAIL PROTECTED]> wrote: > > Andrew, the Score for Node vcs9472 for Resource resource_ip1 is always > set >

Re: [Linux-HA] resource monitoring and restarting

2008-07-09 Thread Raghuram Bondalapati
I think if you set Resource Failure Stickiness to -INFINITY on mysql service it should failover. In general if you set Default Resource Failure Stickiness to -INFINITY, it will failover any failed service to the other node instead of trying to restart. --Raghu On 7/9/08, Steve Wray <[EMAIL PROT

Re: [Linux-HA] fail-count-resource not getting incremented

2008-07-09 Thread Raghuram Bondalapati
<[EMAIL PROTECTED]> wrote: > > Known bug in 2.1.3 > > Please grab the latest Pacemaker release (0.6.5) for you distro from > http://download.opensuse.org/repositories/server:/ha-clustering/ > > On Tue, Jul 8, 2008 at 22:51, Raghuram Bondalapati > <[EMAIL

Re: [Linux-HA] Help with xinetd service failover

2008-07-09 Thread Raghuram Bondalapati
Understood. Thanks for clarifying and the link to docs Andrew. On 7/9/08, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > > On Tue, Jul 8, 2008 at 20:25, Raghuram Bondalapati > <[EMAIL PROTECTED]> wrote: > > Hi Andrew, the failover of xinetd works fine when i replace xine

Re: [Linux-HA] Problem apprehending heartbeat 2.1.3

2008-07-09 Thread Raghuram Bondalapati
Hi, I found the below site from Novell pretty usefull in getting me started after generating a basic cib.xml. Please check it out. http://www.novell.com/documentation/beta/sles10/heartbeat/index.html?page=/documentation/beta/sles10/heartbeat/data/heartbeat.html --Raghu On 7/9/08, Thibaut Perri

[Linux-HA] fail-count-resource not getting incremented

2008-07-08 Thread Raghuram Bondalapati
Hello list, I have a two node cluster configured with a resource named "resource_ip1". It's of type "IPaddr" and of class "ocf". When the node1 hosting "resource_ip1" is rebooted it failsover to node2. However the fail-count-resource for "resource_ip1" on node1 does not get incremented and still

Re: [Linux-HA] Help with xinetd service failover

2008-07-08 Thread Raghuram Bondalapati
. Why is fencing resource needed in this case and not for the above scenario. Can you please also point me to some documentation on setting up fencing resources. Regards --Raghu On 7/8/08, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > > On Thu, Jul 3, 2008 at 22:29, Raghuram Bondalapa

Re: [Linux-HA] Question on mnitored resource migration

2008-07-08 Thread Raghuram Bondalapati
n: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Auftrag von Raghuram > Bondalapati > Gesendet: Montag, 7. Juli 2008 18:30 > An: linux-ha@lists.linux-ha.org > Betreff: [Linux-HA] Question on mnitored resource migration > > > Hi, > > I am having trouble failing over a

[Linux-HA] Question on mnitored resource migration

2008-07-07 Thread Raghuram Bondalapati
Hi, I am having trouble failing over a monitored resource on to a node which was earlier marked by HA as being not fit to run that resource. However the node that has been earlier marked by HA as not fit to run that resource has been repaired and can now run that resource. How can i get HA to mar

[Linux-HA] Help with xinetd service failover

2008-07-03 Thread Raghuram Bondalapati
Hi folks, I have setup a two node HA cluster with IPaddr as OCF resource and xinetd as LSB resource with a colocation constraint on INFINITY. The failover of services to second node works fine when the first node running the listed services goes down or is rebooted. If the xinted process is killed