Hi Chris,
I'm afraid of using corosynclib-devel-1.2.0 for building qpid that will be
used with corosynclib-1.2.3, because of possible incompatibility, so I
prefer to build corosync-1.2.3 additionally.
Finally I have managed to find that selinux was the problem although
corosync was from the distribution of rhel6 and both corosync and qpid
were started as services.
type=AVC msg=audit(1298373582.553:25): avc: denied { read write } for
pid=1423 comm="corosync" name="control_buffer-SWjjsT" dev=tmpfs ino=14240
scontext=system_u:system_r:corosync_t:s0 tcontext=s
ystem_u:object_r:initrc_state_t:s0 tclass=file
type=SYSCALL msg=audit(1298373582.553:25): arch=c000003e syscall=2
success=no exit=-13 a0=244bdf0 a1=2 a2=180 a3=7fffabfc87d0 items=0 ppid=1
pid=1423 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=
0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="corosync"
exe="/usr/sbin/corosync" subj=system_u:system_r:corosync_t:s0 key=(null)
type=AVC msg=audit(1298373582.554:26): avc: denied { unlink } for
pid=1423 comm="corosync" name="control_buffer-SWjjsT" dev=tmpfs ino=14240
scontext=system_u:system_r:corosync_t:s0 tcontext=syste
m_u:object_r:initrc_state_t:s0 tclass=file
type=SYSCALL msg=audit(1298373582.554:26): arch=c000003e syscall=87
success=no exit=-13 a0=244bdf0 a1=2 a2=d a3=7fffabfc87d0 items=0 ppid=1
pid=1423 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0
egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="corosync"
exe="/usr/sbin/corosync" subj=system_u:system_r:corosync_t:s0 key=(null)
type=AVC msg=audit(1298373582.554:27): avc: denied { read write } for
pid=1423 comm="corosync" name="request_buffer-kBnPC0" dev=tmpfs ino=14241
scontext=system_u:system_r:corosync_t:s0 tcontext=s
ystem_u:object_r:initrc_state_t:s0 tclass=file
type=SYSCALL msg=audit(1298373582.554:27): arch=c000003e syscall=2
success=no exit=-13 a0=244cdf0 a1=2 a2=180 a3=7fffabfc87d0 items=0 ppid=1
pid=1423 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=
0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="corosync"
exe="/usr/sbin/corosync" subj=system_u:system_r:corosync_t:s0 key=(null)
type=AVC msg=audit(1298373582.554:28): avc: denied { unlink } for
pid=1423 comm="corosync" name="request_buffer-kBnPC0" dev=tmpfs ino=14241
scontext=system_u:system_r:corosync_t:s0 tcontext=syste
m_u:object_r:initrc_state_t:s0 tclass=file
type=SYSCALL msg=audit(1298373582.554:28): arch=c000003e syscall=87
success=no exit=-13 a0=244cdf0 a1=2 a2=d a3=7fffabfc87d0 items=0 ppid=1
pid=1423 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0
egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="corosync"
exe="/usr/sbin/corosync" subj=system_u:system_r:corosync_t:s0 key=(null)
type=AVC msg=audit(1298373582.554:29): avc: denied { read write } for
pid=1423 comm="corosync" name="response_buffer-Ln4qN7" dev=tmpfs ino=14242
scontext=system_u:system_r:corosync_t:s0 tcontext=
system_u:object_r:initrc_state_t:s0 tclass=file
type=SYSCALL msg=audit(1298373582.554:29): arch=c000003e syscall=2
success=no exit=-13 a0=244ddf0 a1=2 a2=180 a3=7fffabfc87d0 items=0 ppid=1
pid=1423 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=
0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="corosync"
exe="/usr/sbin/corosync" subj=system_u:system_r:corosync_t:s0 key=(null)
type=AVC msg=audit(1298373582.554:30): avc: denied { unlink } for
pid=1423 comm="corosync" name="response_buffer-Ln4qN7" dev=tmpfs ino=14242
scontext=system_u:system_r:corosync_t:s0 tcontext=syst
em_u:object_r:initrc_state_t:s0 tclass=file
type=SYSCALL msg=audit(1298373582.554:30): arch=c000003e syscall=87
success=no exit=-13 a0=244ddf0 a1=2 a2=d a3=7fffabfc87d0 items=0 ppid=1
pid=1423 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0
egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="corosync"
exe="/usr/sbin/corosync" subj=system_u:system_r:corosync_t:s0 key=(null)
type=AVC msg=audit(1298373582.554:31): avc: denied { read write } for
pid=1423 comm="corosync" name="dispatch_buffer-6Qd8Xe" dev=tmpfs ino=14243
scontext=system_u:system_r:corosync_t:s0 tcontext=
system_u:object_r:initrc_state_t:s0 tclass=file
type=SYSCALL msg=audit(1298373582.554:31): arch=c000003e syscall=2
success=no exit=-13 a0=244edf0 a1=2 a2=180 a3=7fffabfc87d0 items=0 ppid=1
pid=1423 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=
0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="corosync"
exe="/usr/sbin/corosync" subj=system_u:system_r:corosync_t:s0 key=(null)
type=AVC msg=audit(1298373582.554:32): avc: denied { unlink } for
pid=1423 comm="corosync" name="dispatch_buffer-6Qd8Xe" dev=tmpfs ino=14243
scontext=system_u:system_r:corosync_t:s0 tcontext=syst
em_u:object_r:initrc_state_t:s0 tclass=file
Best Regards,
Sergey Zhemzhitsky
Chris Sears <[email protected]>
22.02.2011 19:57
Please respond to
[email protected]
To
[email protected]
cc
[email protected]
Subject
Re: Building qpid 0.8 with clustering on RHEL 6
Sergey,
It looks like corosynclib-devel is included in the optional RHEL 6 repo.
Perhaps you have that repo disabled?
http://pkgs.org/centos-6-rhel-6/centos-rhel-optional-i386/corosynclib-devel-1.2.0-2.el6.i686.rpm.html
<
http://pkgs.org/centos-6-rhel-6/centos-rhel-optional-i386/corosynclib-devel-1.2.0-2.el6.i686.rpm.html
>
-
Chris
On Tue, Feb 22, 2011 at 11:37 AM, <[email protected]> wrote:
> Hi Alan,
>
> Thanks for response.
>
> There is no corosynclib-devel in the RHEL 6 distribution.
> Both qpid and corosync are started as services, so SELinux must not
bring
> any problems.
> And firewall allows all traffic.
>
> As I have mentioned the problem occurs only after reboot, and services
are
> started manually everything works fine.
>
> Best Regards,
> Sergey Zhemzhitsky
>
>
>
>
> Alan Conway <[email protected]>
> 22.02.2011 17:31
> Please respond to
> [email protected]
>
>
> To
> [email protected]
> cc
>
> Subject
> Re: Building qpid 0.8 with clustering on RHEL 6
>
>
>
>
>
>
> On 02/22/2011 08:02 AM, [email protected] wrote:
> > 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.
>
> You need to install corosynclib-devel for the header files.
>
> > 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.
>
> Try the checklist at
https://cwiki.apache.org/qpid/starting-a-cluster.html
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
>
>
_______________________________________________________
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
