From: Robert Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Possible problem with cman init script in CVS HEAD (fence related)
Date: Mon, 27 Nov 2006 10:22:25 -0600 [thread overview]
Message-ID: <456B10C1.8090604@redhat.com> (raw)
In-Reply-To: <4566D102.3060707@ubuntu.com>
Fabio Massimo Di Nitto wrote:
> Hi guys,
>
> I found a corner case where calling fence_tools -w leave will/might hang.
> in my setup where i have 2 nodes cluster:
>
> - both nodes are up
> - poweroff the first one -> OK
> - reboot the second one -> OK
> - the second node comes up again:
>
> cman_tools services will show:
> fence 0 default 00040001 JOIN_START_WAIT
>
> since the first node is "dead" there is never a complete switch to state = none.
>
> if you call fence_tools -w leave it will hang there forever.
>
> in my init scripts I just changed the fence_stop() to use the usual wait 10
> seconds or die kind of loop:
>
> fence_tool -w leave &
> for sec in $(seq 1 10); do
> if pidof fence_tool &> /dev/null; then
> if [ "$sec" = 10 ]; then
> kill $(pidof fence_tool) > /dev/null 2>&1
> else
> sleep 1
> fi
> fi
> done
>
> Regards
> Fabio
>
> PS I spotted this problem when updating the Ubuntu init scripts, but the code
> used in upstream init script seems to suffer the exact same problem. You also
> want to note that i am not checking for fenced to exit, but for the tools to return.
>
>
Hi Fabio,
You should be able to do the same thing by specifying -t 10 for a
ten-second timeout
on fence_tool. For example:
fence_tool -t 10 -w leave
The default timeout value is five minutes, which means the hang
shouldn't last
forever at any rate.
Regards,
Bob Peterson
Red Hat Cluster Suite
next prev parent reply other threads:[~2006-11-27 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 11:01 [Cluster-devel] Possible problem with cman init script in CVS HEAD (fence related) Fabio Massimo Di Nitto
2006-11-27 16:22 ` Robert Peterson [this message]
2006-11-27 16:33 ` Fabio Massimo Di Nitto
2006-11-27 23:38 ` Robert Peterson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=456B10C1.8090604@redhat.com \
--to=rpeterso@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.