On Tue, May 26, 2009 at 3:22 PM, Eliot Gable wrote:
> I am using 1.0.3, but the failure-timeout thing does not seem to work for
> pingd.
>
You'll have to show us the rest of your configuration
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
h
...@beekhof.net]
Sent: Monday, May 25, 2009 11:49 AM
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] PingD Failure-Timeout
On Thu, May 21, 2009 at 10:20 PM, Eliot Gable wrote:
> Is there a way to time-out the failure of PingD?
Yes, but you need version >= 1.0.0
I assume you're not runn
On Thu, May 21, 2009 at 10:20 PM, Eliot Gable wrote:
> Is there a way to time-out the failure of PingD?
Yes, but you need version >= 1.0.0
I assume you're not running it as a clone right?
>
>
>
> In my configuration, I cannot run PingD all the time on every node. Only one
> node (the master) has
tended recipient, please call me
immediately. BROADVOX is a registered trademark of Broadvox, LLC.
From: Eliot Gable [mailto:ega...@broadvox.net]
Sent: Thursday, May 21, 2009 4:20 PM
To: pacemaker@oss.clusterlabs.org
Subject: [Pacemaker] PingD Failure-Timeout
Is there a way to time-out the fail
Is there a way to time-out the failure of PingD?
In my configuration, I cannot run PingD all the time on every node. Only one
node (the master) has public Internet access. I use PingD to cause the master
to fail-over to one of the slaves. When a slave becomes master, it then gains
public Intern
