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