Just an update to this - there seems to be a bug in the cman / corosync. When they are run together, the corosync doesn't seem to read the uidgid.d settings. Therefore if you want to use cman and corosync, you have to run the broker as root. That is not something we wanted.
So we decided to go without cman until this issue is fixed. Running it just with corosync seems to work fine for us. Regards Jakub On Wed, Aug 17, 2011 at 17:38, Jakub Scholz <[email protected]> wrote: > Well, we were trying to go according to the guide, including the > troubleshooting chacklist. But the list seems to describe only how to > get the cluster running using corosync only. We wanted to include cman > in the setup - so that we have the quorum, fencing and so on. So our > corosync is being run by the cman. And as a result, it seems that we > can get the cluster running only under root user and not under the > qpidd user. That's why I assume that the configuration of the > addresses, firewalls etc. are correct. It almost seems to me like the > corosync ignores the uidgid configuration when run by cman. > > A colleague of mine is now changing the setup to exclude cman - we > will see whether that helps or not. > > Regards > Jakub > > On Wed, Aug 17, 2011 at 14:59, Alan Conway <[email protected]> wrote: >> On 08/16/2011 02:02 PM, Jakub Scholz wrote: >>> >>> Hi Andy, >>> >>> Yes, I'm trying to run it qpidd user: >>> >>> $ id >>> uid=498(qpidd) gid=498(qpidd) groups=498(qpidd) >>> >> >> 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]
