Hi Jan, Thanks for this support. What you want to say with “RHEL 6 is last version where OpenAIS services are supported”, which application openais or corosync?
I ask due to Red Hat says, RHEL6 supports corosync instead of openais. We tested our client application with r30(released in 2004), because r30 source is distributed in the source code of client application. There is a communication problem between client and openais server. Unix listening socket is created and client sends data from this socket, but ais server does not return for progress. Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:107 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:122 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:124 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:130 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:133 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:139 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:142 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:148 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:151 Nov 13 13:31:32 MRUPle4Server libais[16002]: clm.c:saClmInitialize:154 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saServiceConnectTwo:152 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saServiceConnectTwo:157 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saServiceConnectTwo:159 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saServiceConnectTwo:165 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saServiceConnectTwo:171 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saServiceConnectTwo:181 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saServiceConnectTwo:185 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saRecvRetry:286 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saRecvRetry:298 Nov 13 13:31:32 MRUPle4Server libais[16002]: util.c:saRecvRetry:303 | sockfd:14, flags:16640 We did not find RCA for that with more debugging. Secondly, we tested openais functionality with openais-0.80.6-37.el5.x86_64.rpm that is provided by Red Hat. No changes anything. We though, openais is not suitable on RHEL6 so, we decided to continue with corosync. -----Original Message----- From: Jan Friesse [mailto:[email protected]] Sent: Friday, November 13, 2015 11:15 AM To: Anil KARADAG; [email protected] Subject: Re: [corosync] Code migration from openais r30 to corosync Hi, anil karadag napsal(a): > Hi, > > I have a application, which provides clustering with openais. After > RHEL upgrade from 5 to 6, openais cannot be run properly. And Red Hat > supports Actually, RHEL 6 is last version where OpenAIS services are supported, so there shouldn't be any required changes or they should be minimal. What exactly doesn't work for you? RHEL 7 (corosync 2.x) is different story. > corosync with cman in RHEL6. So we are analyzing. Can you provide docs > to understand and verify what same/different between them. > > For example corosync: method_yy() is equivalent to openais: method_xx(). No such document really exists, simply because Corosync API (what existed and was heavily used also in RHEL 5) is completely different. Take a look specifically to cpg_overview, quorum_overview and cmap_overview (RHEL 7)/confdb_overview (RHEL 6). Regards, Honza > > _______________________________________________ > discuss mailing list > [email protected]<mailto:[email protected]> > http://lists.corosync.org/mailman/listinfo/discuss > Bu e-posta mesajı ve ekleri gönderildiği kişi ya da kuruma özeldir ve gizlidir. Ayrıca hukuken de gizli olabilir. Hiçbir şekilde üçüncü kişilere açıklanamaz ve yayınlanamaz. Eğer mesajın gönderildiği alıcı değilseniz bu elektronik postanın içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız kesinlikle yasaktır ve bu elektronik postayı ve eklerini derhal silmeniz gerekmektedir. NETAŞ TELEKOMÜNİKASYON A.Ş. bu mesajın içerdiği bilgilerin doğruluğu veya eksiksiz olduğu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne şekilde olursa olsun içeriğinden, iletilmesinden, alınmasından, saklanmasından ve kullanılmasından sorumlu değildir. Bu mesajdaki görüşler gönderen kişiye ait olup, NETAŞ TELEKOMÜNİKASYON A.Ş.’nin görüşlerini yansıtmayabilir. ------------------------------------------------------- This e-mail and its attachments are private and confidential and intended for the exclusive use of the individual or entity to whom it is addressed. It may also be legally confidential. Any disclosure, distribution or other dissemination of this message to any third party is strictly prohibited. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted. NETAŞ TELEKOMÜNİKASYON A.Ş. makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the transmission, reception, storage or use of such information in any way whatsoever. The opinions expressed in this message are those of the sender and may not necessarily reflect the opinions of NETAŞ TELEKOMÜNİKASYON A.Ş.
_______________________________________________ discuss mailing list [email protected] http://lists.corosync.org/mailman/listinfo/discuss
