Hello Everyone, Is it possible to have someone install the mentioned from source:
PCMK 1.1.6-2d8fad5 CMAN 3.1.7 Corosync 1.4.2 OpenAIS Latest version And see if they are able to get dlm_controld (working), and o2cb (broken due to ocfs2_controld.pcmk) going on their machine? I also wanted to ask for a heads up in regards to interoperability of future releases for the two stacks, when Cluster3 gets split into (dlm, gfs2-utils, fence, fence-agents etc...), as of which pcmk stacks would be more interested in the first two sub projects. I figure that's what is being currently worked on.... Thanks in Advance, Nick. On Mon, Nov 7, 2011 at 9:58 PM, Nick Khamis <[email protected]> wrote: > Hello Tim, > > Thank you so much for your response. it would make sense that when cman starts > corosync, all the openais related stuff were also included. I really > wish I had more > time to dig into the code. Tomorrow morning I may do just that. > Maybe re-installing everything from scratch on a clean VM. It could be > the "make uninstall" > is not wiping out everything from the previous installations, and thus > effecting the expected results. > Another thing I thought about was checking out the head of the rest of > the pcmk stack (corosync, openais). But before I went into any of that > tangent, I thought I > would post to the list. > >>> but it could be the case that you are the first person in the world to try >>> to combine these versions of these specific components in exactly the >>> way you are doing so. > > Googling those errors would definitely suggest that. And when the cman > cluster gets split > into the different modules, a new set of errors will get introduced, > and cometh are > Lehman's laws. There is nothing new here, however; if it's indeed a > bug then it would only > be a matter of time. > > In respect to the versions of everything being compiled, I am not > doing anything that should > be out of the ordinary. Just simply building the latest stable > versions of the two stacks? Where > the past incompatible versions of whatever are known... > > As always thank you for your time. > > Regards, > > Nick. > > > On Mon, Nov 7, 2011 at 9:08 PM, Tim Serong <[email protected]> wrote: >> On 11/07/2011 11:34 PM, Nick Khamis wrote: >>> Hello Everyone, >>> >>> After being unsuccessful trying to get cman+pacemaker working, >>> I decided to try the latest committed version of pacemaker "git clone >>> https://github.com/ClusterLabs/pacemaker.git";. And recieving >>> the following error from ocfs2_controld.pcmk: >>> >>> >>> ocfs2_controld.pcmk -D >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional service options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'corosync_quorum' for option: name >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional service options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'corosync_cman' for option: name >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional service options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'openais_clm' for option: name >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional service options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'openais_evt' for option: name >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional service options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'openais_ckpt' for option: name >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional service options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'openais_msg' for option: name >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional service options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'openais_lck' for option: name >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional service options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'openais_tmr' for option: name >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: No >>> additional configuration supplied for: service >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: config_find_next: >>> Processing additional quorum options... >>> ocfs2_controld[6883]: 2011/11/03_16:34:19 info: get_config_opt: Found >>> 'quorum_cman' for option: provider >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 info: get_cluster_type: >>> Detected an active 'cman' cluster >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 info: get_local_node_name: >>> Using CMAN node name: astdrbd1 >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 info: >>> init_ais_connection_once: Connection to 'cman': established >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 info: crm_new_peer: Node >>> astdrbd1 now has id: 1 >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 info: crm_new_peer: Node 1 >>> is now known as astdrbd1 >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 ERROR: crm_abort: >>> send_ais_text: Triggered assert at corosync.c:352 : dest != >>> crm_msg_ais >>> Sending message 0 via cpg: FAILED (rc=22): Message error: Success (0) >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 ERROR: send_ais_text: >>> Sending message 0 via cpg: FAILED (rc=22): Message error: Success (0) >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 ERROR: crm_abort: >>> send_ais_text: Triggered assert at corosync.c:352 : dest != >>> crm_msg_ais >>> Sending message 1 via cpg: FAILED (rc=22): Message error: Success (0) >>> ocfs2_controld[6883]: 2011/11/03_16:34:20 ERROR: send_ais_text: >>> Sending message 1 via cpg: FAILED (rc=22): Message error: Success (0) >>> 1320352460 setup_stack@170: Cluster connection established. Local node id: >>> 1 >>> 1320352460 setup_stack@174: Added Pacemaker as client 1 with fd -1 >>> >> >> I still believe these errors are the result of pacemaker (apparently) >> not knowing/thinking it's running on/with openais (for some reason). See: >> >> http://oss.clusterlabs.org/pipermail/pacemaker/2011-November/011978.html >> >> I also don't see how the patch Andrew mentioned at >> http://oss.clusterlabs.org/pipermail/pacemaker/2011-November/011992.html >> could fix this (but would be delighted to be proved wrong). >> >>> Setup: >>> >>> PCMK 1.1.6-2d8fad5 >>> CMAN 3.1.7 >>> Corosync 1.4.2 >>> OpenAIS Latest version >>> >>> I just want to mention that I never start OpenAIS just corosync. Is >>> this ok for dlm, >>> and configfs? Or should I be using openais? >> >> ocfs2_controld with Pacemaker needs openais, but openais isn't something >> you "start" separately, it's a bunch of plugins that corosync is meant >> to load. What this means in a CMAN environment, I do not know. >> >> IMO (and as Florian alluded to in another message), you'd probably save >> yourself a lot of trouble taking prebuilt packages from a distro where >> the pieces you need are known to work together. >> >> Not to say I think what you're doing won't ultimately be worthwhile, but >> it could be the case that you are the first person in the world to try >> to combine these versions of these specific components in exactly the >> way you are doing so. >> >> Regards, >> >> Tim >> -- >> Tim Serong >> Senior Clustering Engineer >> SUSE >> [email protected] >> _______________________________________________ >> Linux-HA mailing list >> [email protected] >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems >> > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
