Message broker connection failed to all the configured hosts - Sipelia™ 2.10

Sipelia User Guide 2.10
Applies to
Sipelia™ 2.10
Last updated
2020-03-11
Content type
Guides
Guides > User guides
Language
English
Product
Sipelia™ Communications Management
Version
2.10

The Sipelia™ plugin role displays the error message Message broker connection failed to all the configured hosts: and the connection to Sipelia™ Server is not possible from Security Desk.

Before you begin

  • Ensure that the RabbitMQ username and password are correct.
  • Ensure that the Message broker server parameters are correct.
    • The server address must be reachable from the machine where Sipelia Server and Sipelia Client are installed.
    • The correct ports must be selected. By default, Sipelia™ uses the SSL connection to RabbitMQ which works on the RabbitMQ SSL port. If this connection is disabled in Sipelia™, the Message broker server port must be changed to use the RabbitMQ non-SSL port. If required, you can also change the ports used by RabbitMQ.

What you should know

  • This error typically occurs when your Sipelia™ Message broker configuration is incorrect. Your Message broker server is not reachable from the machine hosting the Sipelia™ system, or the RabbitMQ server is offline or is not working.
  • You can increase the reliability of your system by deploying and configuring multiple RabbitMQ servers. If one of the servers fails, Sipelia™ automatically connects to the next server. This ensures that Sipelia™ is always operational.
    IMPORTANT: It is strongly recommended that you use the RabbitMQ version that is included with the Sipelia™ installation package. Differences between RabbitMQ releases might prevent the use of older versions. Sipelia™ Server installation always installs or upgrades to the correct RabbitMQ version.

Procedure

  1. Restart the Sipelia™ plugin role. If the problem is still present, continue with the next step.
  2. Ensure that your Message broker configuration is correct. Verify the username, password, address, and port. If the problem is still present, continue with the next step.
  3. Ensure that there are no network issues that prevent the Sipelia™ plugin or Sipelia™ Security Desk from reaching the RabbitMQ server that is installed with the Sipelia™ plugin. Depending on your network architecture, you might need to update your networking system to allow the required traffic to pass. RabbitMQ uses the AMPQ (TCP) protocol, the default SSL port is 5671, and the default port for non-SSL communication is 5672. If the problem is still present, continue with the next step.
  4. On the machine where RabbitMQ server is installed, verify that the RabbitMQ service is running, then restart the RabbitMQ service.
    NOTE: To access the RabbitMQ service, open the Windows Services panel (services.msc) and look for RabbitMQ.
  5. If the RabbitMQ service fails to start, check the RabbitMQ service logs (file path: %APPDATA%\RabbitMQ\log) for an explanation of the failure.