You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "An Yang (JIRA)" <ji...@apache.org> on 2014/07/15 12:22:04 UTC
[jira] [Commented] (QPID-3483) Unable to run qpid in a cluster
under cman
[ https://issues.apache.org/jira/browse/QPID-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061917#comment-14061917 ]
An Yang commented on QPID-3483:
-------------------------------
Hi Alan,
I met the same problem, and got "You are not authorized to access bug #733221.", could you give me any advices?
Thanks.
> 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 was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org