Hi Andrew,
Thank you for comments.
> diff --git a/lib/services/services_linux.c b/lib/services/services_linux.c
> index 961ff18..2279e4e 100644
> --- a/lib/services/services_linux.c
> +++ b/lib/services/services_linux.c
> @@ -227,6 +227,7 @@ recurring_action_timer(gpointer data)
> op->stdout_
/me slaps forhead
this one should work
diff --git a/lib/services/services.c b/lib/services/services.c
index 8590b56..753e257 100644
--- a/lib/services/services.c
+++ b/lib/services/services.c
@@ -313,6 +313,7 @@ services_action_free(svc_action_t * op)
if (op->opaque->repeat_timer) {
Hi Andrew,
I applied three corrections that you made and checked movement.
I picked all "abort" processing with g_source_remove() of services.c just to
make sure.
* I set following "abort" in four places that carried out g_source_remove
>>> if (g_source_remove(op->opaque->repeat_timer)
On 9 Oct 2014, at 5:06 pm, Alexandre wrote:
> I have seen this behavior on several virtualsed environments. when vm backup
> starts, the VM actually freezes for a (short?) Period of time.I guess it then
> no more responding to the other cluster nodes thus triggering unexpected fail
> over and
Hi Andrew,
Okay!
I test your patch.
And I inform you of a result.
Many thanks!
Hideo Yamauchi.
- Original Message -
> From: Andrew Beekhof
> To: renayama19661...@ybb.ne.jp; The Pacemaker cluster resource manager
>
> Cc:
> Date: 2014/10/10, Fri 10:47
> Subject: Re: [Pacemaker] [Pro
Perfect!
Can you try this:
diff --git a/lib/services/services.c b/lib/services/services.c
index 8590b56..cb0f0ae 100644
--- a/lib/services/services.c
+++ b/lib/services/services.c
@@ -417,6 +417,7 @@ services_action_kick(const char *name, const char *action,
int interval /* ms */
free(id);
On 10 Oct 2014, at 12:12 pm, Lax wrote:
> Hi All,
>
> I ran into a time out issue while failing over from master to the peer
> server and I have a 2 node setup with 2 resources. Though it was working all
> along, this was the first time this issue is seen for me.
>
> It fail with following err
Hi All,
I ran into a time out issue while failing over from master to the peer
server and I have a 2 node setup with 2 resources. Though it was working all
along, this was the first time this issue is seen for me.
It fail with following error 'error: process_lrm_event: LRM operation
resourceB_sto
Hi Andrew,
Setting of gdb of the Ubuntu environment does not yet go well and I touch lrmd
and cannot acquire trace.
Please wait for this a little more.
But.. I let lrmd terminate abnormally when g_source_remove() of
cancel_recurring_action() returned FALSE.
-
gboolean
cancel_recurring_acti
Hi all. I was hoping to get some help with my configuration. I'm kinda
stuck at the moment.
I've made some changes to the Raid1 RA to implement a ms style
configuration (you can see a diff here http://pastebin.com/Q2nbF6Rg
against the RA in the github repo)
I've modeled my ms implementation h
10 matches
Mail list logo
