Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

9.3. Cluster Troubleshooting

9.3.1. Troubleshooting Cluster configuration
复制链接

When you initially start a HA cluster, all brokers are in joining mode. The brokers do not automatically select a primary, they rely on the cluster manager rgmanager to do so. If rgmanager is not running or is not configured correctly, brokers will remain in the joining state. Refer to Section 9.1.9, “Cluster Resource Manager (rgmanager)” for more information.
If a broker is unable to establish a connection to another broker in the cluster, the log will contain SASL errors similar to the following: 
info SASL: Authentication failed: SASL(-13): user not found: Password verification failed

warning Client closed connection with 320: User anonymous@QPID federation connection denied. Systems with authentication enabled must specify ACL create link rules.

warning Client closed connection with 320: ACL denied anonymous@QPID creating a federation link.

Procedure 9.3. Troubleshooting Cluster SASL Configuration

  1. Set the HA security configuration and ACL file as described in Section 9.1.19, “Security”
  2. Once the cluster is running and the primary is promoted , run: 
    qpid-ha status --all
    to ensure that the brokers are running as one cluster.
  3. Once the cluster is running, run qpid-ha to make sure that the brokers are running as one cluster.
Report a bug
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2026 Red Hat返回顶部