[Pacemaker] [Linux-HA] pcmk + corosync + cman for dlm support?

[Nick Khamis]

Vladislav,

Thank you so much for your response. Just to make sure, all I need is to:
* Apply the three patches to cman. Found here
"http://www.gossamer-threads.com/lists/linuxha/pacemaker/75164?do=post_view_threaded".
* Recompile CMAN
* Do I have to recompile PCMK again?

I also want to mention that fencing is not important right now, and I
would like to disable fencing JUST for the prototype,
and untill things are going. I am almost there (cman-pcmk+ocfs2) with
the exception of O2CB which is throwing the following error:

Nov 01 20:15:26 astdrbd1 crmd: [1494]: info: send_direct_ack: ACK'ing
resource op astDRBD:1_notify_0 from
76:1:0:4a9306d4-a099-4b6f-ba84-404c302f45a8: lrm_invoke-lrmd-1320192926-6
Nov 01 20:15:26 astdrbd1 crmd: [1494]: info: process_lrm_event: LRM
operation astDRBD:1_notify_0 (call=10, rc=0, cib-update=0,
confirmed=true) ok
Nov 01 20:15:27 astdrbd1 crmd: [1494]: info: do_lrm_rsc_op: Performing
key=7:2:0:4a9306d4-a099-4b6f-ba84-404c302f45a8 op=astIP_monitor_60000)
Nov 01 20:15:27 astdrbd1 lrmd: [1491]: info: rsc:astIP:11: monitor
Nov 01 20:15:27 astdrbd1 crmd: [1494]: info: do_lrm_rsc_op: Performing
key=90:2:0:4a9306d4-a099-4b6f-ba84-404c302f45a8 op=astDRBD:1_notify_0)
Nov 01 20:15:27 astdrbd1 lrmd: [1491]: info: rsc:astDRBD:1:12: notify
Nov 01 20:15:27 astdrbd1 crmd: [1494]: info: do_lrm_rsc_op: Performing
key=58:2:0:4a9306d4-a099-4b6f-ba84-404c302f45a8 op=astO2CB:1_start_0 )
Nov 01 20:15:27 astdrbd1 lrmd: [1491]: info: rsc:astO2CB:1:13: start
Nov 01 20:15:27 astdrbd1 crmd: [1494]: info: process_lrm_event: LRM
operation astIP_monitor_60000 (call=11, rc=0,
cib-update=17,confirmed=false) ok
Nov 01 20:15:28 astdrbd1 crmd: [1494]: info: send_direct_ack: ACK'ing
resource op astDRBD:1_notify_0 from
90:2:0:4a9306d4-a099-4b6f-ba84-404c302f45a8:
lrm_invoke-lrmd-1320192928-7
Nov 01 20:15:28 astdrbd1 crmd: [1494]: info: process_lrm_event: LRM
operation astDRBD:1_notify_0 (call=12, rc=0, cib-update=0,
confirmed=true) ok
Nov 01 20:15:28 astdrbd1 crmd: [1494]: info: do_lrm_rsc_op: Performing
key=15:2:0:4a9306d4-a099-4b6f-ba84-404c302f45a8
op=astDRBD:1_promote_0)
Nov 01 20:15:28 astdrbd1 lrmd: [1491]: info: rsc:astDRBD:1:14: promote
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: info:
get_cluster_type: Cluster type is: 'cman'
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: info:
get_local_node_name: Using CMAN node name: astdrbd1
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: info:
init_ais_connection_once: Connection to 'cman': established
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: info: crm_new_peer:
Node astdrbd1 now has id: 1
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: info: crm_new_peer:
Node 1 is now known as astdrbd1
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: ERROR: crm_abort:
send_ais_text: Triggered assert at ais.c:346 : dest != crm_msg_ais
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: ERROR: send_ais_text:
Sending message 0 via cpg: FAILED (rc=22): Message error: Success (0)
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: ERROR: crm_abort:
send_ais_text: Triggered assert at ais.c:346 : dest != crm_msg_ais
Nov 01 20:15:28 astdrbd1 ocfs2_controld: [1883]: ERROR: send_ais_text:
Sending message 1 via cpg: FAILED (rc=22): Message error: Success (0)
Nov 01 20:15:29 astdrbd1 pacemakerd: [1485]: WARN: send_ipc_message:
IPC Channel to 1883 is not connected
Nov 01 20:15:29 astdrbd1 lrmd: [1491]: info: RA output:
(astIP:start:stderr) ARPING 192.168.2.6 from 192.168.2.6 eth2
Sent 5 probes (5 broadcast(s))
Received 0 response(s)

Thanks in Advance,

Nick.

On Fri, Oct 28, 2011 at 3:34 AM, Vladislav Bogdanov
<bubble at hoster-ok.com> wrote:
> 28.10.2011 04:04, Nick Khamis wrote:
>> Hello Everyone,
>>
>> I just want to make sure this is still the case before I go through
>> with it. I am trying to setup an
>> active/active using:
>>
>> Corosync 1.4.2
>> Pacemaker 1.1.6
>> Cluster3
>> DRBD 8.3.7
>> OCFS2
>>
>> The only reason I installed Cluster3 was for dlm support. Fencing
>> would be handled by stonithd.
>> Is there any reason I need to fully install and configure two cluster
>> managers. Defining nodes in
>> both cman and corosync/openais?
>
> You may look at
> http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg09959.html
>
> That message contains Andrew's dlm_controld patch for shortening fencing
> path - it now talks directly to stonith subsystem, rebased for 3.0.17,
> and some fixes to make it all compile. Some work should probably be done
> to make it apply/compile on latest cluster3.
>
> That way I eliminate cman from stack (except some dlm-related libs) and
> run cluster with stable fencing on top of corosync/openais.
>
> Best,
> Vladislav
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>