[Pacemaker] hbagent of pacemaker-mgmt
Yan Gao
ygao at novell.com
Wed Jul 15 08:56:41 UTC 2009
Hi,
>>>On 7/15/2009 at 3:18 PM, "Junko IKEDA" <ikedaj at intellilink.co.jp>
wrote:
> Hi,
>
> hbagent detects whether or not the event occurred on that node if it
works
> with Heartbeat.
Indeed
> Can I get the "myuuid" of openais?
Theoretically, we could get openais nodeid. I'll revise hbagent later.
>
>
> snmp_subagent/hbagentv2.c
>
> 280 static void
> 281 hbagentv2_update_diff(const char *event, crm_data_t *msg)
> 282 {
>
> 357 #if SUPPORT_HEARTBEAT
> 358 if (is_heartbeat_cluster()) {
> 359 if (STRNCMP_CONST(node_id, myuuid) != 0) {
> 360 /* This change is not at my node */
> 361 free_xml(diff);
> 362 return;
> 363 }
> 364 }
> 365 #endif
>
> Thanks,
> Junko
>
> On Tue, 14 Jul 2009 16:18:03 +0900, Junko IKEDA
<ikedaj at intellilink.co.jp>
> wrote:
>
> > Sorry for missing attatchments.
> >
> > Thanks,
> > Junko
> >
> > On Tue, 14 Jul 2009 16:11:20 +0900, Junko IKEDA
<ikedaj at intellilink.co.jp>
> wrote:
> >
> >> Hi,
> >>
> >> I am trying to run hbagent with openais in the following way,
> >>
> >> # export HA_cluster_type="openais"
> >> # service openais start
> >> # /usr/lib64/heartbeat/hbagent -d
> >>
> >> hbagent could start successfully,
> >> but there is something wrong with it.
> >>
> >> When I run hbagent included in Heartbeat 2.1.4,
> >> trap events came from the node which the event occurred on.
> >> But with openais, all node throw the trap even if that event
didn't occur
> on it.
> >>
> >> For example,
> >> primitive resource "dummy1" and "dummy2" started on "dom1".
> >> In this case, only "dom1" was supposed to trap that these two
resources
> started on it,
> >> but "dom2" (stand-by node) also notice it.
> >> It looks like a duplicate.
> >> Please see the attached logs.
> >>
> >> Should I need any additional setups?
> >>
> >> * version
> >> openais-0.80
> >> pacemaker-1.0.4
> >> pacemaker-mgmt-1.99
> >>
> >> Thanks,
> >> Junko
> >
Regards,
Yan Gao
China R&D Software Engineer
ygao at novell.com
Novell, Inc.
Making IT Work As One™
More information about the Pacemaker
mailing list