qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (QPID-3483) Unable to run qpid in a cluster under cman
Date Fri, 15 Feb 2013 14:57:13 GMT

     [ https://issues.apache.org/jira/browse/QPID-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alan Conway closed QPID-3483.
-----------------------------

    Resolution: Won't Fix

See https://bugzilla.redhat.com/show_bug.cgi?id=733221 for more details.
                
> Unable to run qpid in a cluster under cman
> ------------------------------------------
>
>                 Key: QPID-3483
>                 URL: https://issues.apache.org/jira/browse/QPID-3483
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Clustering
>    Affects Versions: 0.13
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>
> Description of problem:
> Section 7.1 of user guide "Starting a Broker in a Cluster" describes a way how
> to start qpidd in a cluster under cman. That does not work on RHEL 6.x where
> corosync requires /etc/corosync/uidgid.d to authenticate non-root access to
> corosync. But when corosync runs under cman, cman overrides configuration
> parser of corosync by its own parser, taking into account only
> /etc/cluster/cluster.conf configuration. That file has no option to setup
> uidgid at all.
> At the end, as qpidd runs under qpidd user, there is no way to run qpidd in a
> RHEL6.x cluster under cman.
> Version-Release number of selected component (if applicable):
> MRG 2.0 & RHEL 6.x
> How reproducible:
> 100%
> Steps to Reproduce (apply the below to at least 3 nodes in a cluster):
> 1. Edit /etc/corosync/uidgid.d/qpidd per manuals
> 2. Setup /etc/cluster/cluster.conf to have some working cman configuration
> (e.g. use file from https://access.redhat.com/kb/docs/DOC-58232)
> 3. /etc/qpidd.conf has:
> cluster-mechanism=PLAIN
> cluster-username=guest
> cluster-password=guest
> cluster-name=TEST
> cluster-cman=yes
> 4. service cman start
> 5. service qpidd start
> Actual results:
> qpidd will fail with:
> Starting Qpid AMQP daemon: Daemon startup failed: Failed to initialize CPG.:
> security (100)
> Expected results:
> qpidd will start properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message