Red Hat Bugzilla – Bug 515513
Make cluster update work out of the box without special authentication options
Last modified: 2015-11-15 20:11:37 EST
Description of problem: E.g. when starting qpidd as service, don't want to get authentication errors when second node is started up.
Fixed in r885870, set default --cluster-mechanism to ANONYMOUS. Cluster updates now works without any authentication options.
The cluster update is successfully solved by adding cluster-mechanism=ANONYMOUS to qpidd.conf. The auth. exceptions can be seen when above option is removed and default user is removed (qpid). The above option was added to RHEL4/5 qpidd.conf. The issue has been inhibited/fixed, tested on RHEL 5.5 i386 / x86_64 on packages: python-qmf-0.7.946106-13.el5 python-qpid-0.7.946106-14.el5 qmf-*0.7.946106-17.el5 qpid-cpp-*-0.7.946106-17.el5 qpid-dotnet-0.4.738274-2.el5 qpid-java-*-0.7.946106-10.el5 qpid-tools-0.7.946106-11.el5 ruby-qmf-0.7.946106-17.el5 ruby-qpid-0.7.946106-2.el5 -> VERIFIED
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: With this update, the qpidd service can be run without additional authentication options.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0773.html