qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey_Zhemzhit...@troika.ru
Subject Building qpid 0.8 with clustering on RHEL 6
Date Tue, 22 Feb 2011 13:02:16 GMT
Hi there,

I'm trying to build qpid 0.8 with support of clustering on the RedHat 
Enterprise Linux 6.
For the clustering support to be available it is necessary corosync 
headers and object files to be available, but in there are only 
corosync_1.2.3-21.el6.x86_64.rpm, corosynclib_1.2.3-21.el6.x86_64.rpm, 
corosync_1.2.3-21.el6.i686.rpm.
I have tried to build corosync-1.2.3, and use its headers and object files 
to build qpid and I was able to do it, but now I have another problem. 
When I'm trying to restart corosync and qpid on reboot,  process of 
corosync dies as well as process of the qpid. 
The last error message in the log of the corosync (from the RHEL 
distribution) is 

Feb 22 15:58:30 corosync [CPG   ] lib_init_fn: conn=0x201dc90, 
cpd=0x201c370

Here is log of the qpid

2011-02-22 15:58:30 notice Journal "TplStore": Created
2011-02-22 15:58:30 notice Store module initialized; 
store-dir=/opt/qpid-0.8/data/cluster-node1
2011-02-22 15:58:30 notice Initializing CPG
2011-02-22 15:58:36 error Error during CPG shutdown: Cannot finalize CPG 
group : library (2)
2011-02-22 15:58:36 critical Unexpected error: Cannot get local CPG 
identity: library (2)
2011-02-22 15:58:36 critical Unexpected error: Daemon startup failed: 
Cannot get local CPG identity: library (2)

When corosync and qpid are started as services manually there are no any 
problems.

Could you please suggest how to troubleshoot this problem? It seems that 
such a problem occurs only on system reboot.


Best Regards,
Sergey Zhemzhitsky
_______________________________________________________

The information contained in this message may be privileged and conf idential and protected
from disclosure. If you are not the original intended recipient, you are hereby notified that
any review, retransmission, dissemination, or other use of, or taking of any action in reliance
upon, this information is prohibited. If you have received this communication in error, please
notify the sender immediately by replying to this message and delete it from your computer.
Thank you for your cooperation. Troika Dialog, Russia. 
If you need assistance please contact our Contact Center  (+7495) 258 0500 or go to www.troika.ru/eng/Contacts/system.wbp
 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message