On Wed, 8 Dec 2010, sunitha kumar wrote:
> Hi,
> I am using:
>
> heartbeat-3.0.0-33.2
> pacemaker-mgmt-client-1.99.2-6.1
> pacemaker-libs-1.0.5-4.1
> pacemaker-1.0.5-4.1
> pacemaker-mgmt-1.99.2-6.1
>
> /etc/init.d/heartbeat stop hangs in /usr/lib/heartbeat/heartbeat -k
> strace output on this show
Hi,
I am using:
heartbeat-3.0.0-33.2
pacemaker-mgmt-client-1.99.2-6.1
pacemaker-libs-1.0.5-4.1
pacemaker-1.0.5-4.1
pacemaker-mgmt-1.99.2-6.1
/etc/init.d/heartbeat stop hangs in /usr/lib/heartbeat/heartbeat -k
strace output on this shows it is waiting on its child to exit.., which are
inturn waiti
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Reichert
I have found that for a heartbeat v1 one-system node, you cannot have
auto_failback set to off (or on); heartbeat never really completely
starts.
I leave auto_failback out of the ha.cf file co
On 2008-09-15T16:03:47, Brian Reichert <[EMAIL PROTECTED]> wrote:
> I have found that for a heartbeat v1 one-system node, you cannot
> have auto_failback set to off (or on); heartbeat never really
> completely starts.
Not to mention that v1 with just one node doesn't make any sense.
v1 only prot
On Mon, Sep 15, 2008 at 10:57:40AM -0700, Lamarre, Michael wrote:
> Hello, I am a very new user of Linux-HA, as you will quickly realize as
> you read this. :) We are putting together a system that is not HA in the
> clustered sense, but does require good availability. We want the system
> to be a
Hello, I am a very new user of Linux-HA, as you will quickly realize as
you read this. :) We are putting together a system that is not HA in the
clustered sense, but does require good availability. We want the system
to be able to reboot if it somehow gets extremely hosed/bogged
down/whatever, and
kisalay wrote:
> Hi,
>
> I have a 2 node 2.0.8 Linux HA setup.
> I have observed that when stop is issued on my setup, as soon as the start
> returns, the stop hangs indefinitely, and the only way to stop heartbeat is
> to do killall.
>
> I dug a little deeper into the problem.
>
> First, the pr
On 4/9/07, Kevin Jamieson <[EMAIL PROTECTED]> wrote:
kisalay wrote:
> I have a 2 node 2.0.8 Linux HA setup.
> I have observed that when stop is issued on my setup, as soon as the start
> returns, the stop hangs indefinitely, and the only way to stop heartbeat is
> to do killall.
or wait for th
kisalay wrote:
I have a 2 node 2.0.8 Linux HA setup.
I have observed that when stop is issued on my setup, as soon as the start
returns, the stop hangs indefinitely, and the only way to stop heartbeat is
to do killall.
I've noticed similar behaviour on heartbeat 2.0.7, though haven't gotten
a
Hi,
I have a 2 node 2.0.8 Linux HA setup.
I have observed that when stop is issued on my setup, as soon as the start
returns, the stop hangs indefinitely, and the only way to stop heartbeat is
to do killall.
I dug a little deeper into the problem.
First, the problem is sporadic. I wrote the fol
10 matches
Mail list logo
