Avamar: RabbitMQ Resolution Guide

• RabbitMQ is a message Broker agent which accepts and forwards messages.
• It is used in Avamar to accomplish message transfer with Data Protection Central (DPC) and some VMware related actions.
• When DPC is used to monitor Avamar, Avamar uses dynamic shovels and queues to push messages to DPC. Avamar also receives messages from DPC when using RabbitMQ RPC.
• Most of the time when an Avamar error occurs it is related to this connection between Avamar and DPC,
• There may also be an issue with the local RabbitMQ Broker agent running on Avamar (when DPC is not in use).

• How to check the DPC Service status:

/usr/local/dpc/bin/dpc status

• How to restart the service:

msgbrokerctl.pl --stop

msgbrokerctl.pl --start

• How to reactivate Avamar with DPC:

mccli msgbroker quicksetup --host=<dpc_hostname> --user=administrator@dpc.local --pass=<dpc_password>

• How to check the Avamar BRM settings in mcserver.xml

egrep "brmHostname|enableBrmService" /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml

• How to retrieve the DPC root ca from Avamar:

curl -ks --tlsv1.2 -u <dpcUser>:<dpcPassword> https://<dpcHostname>/brm/app/cert/getRootCA

• How to check for overflowing RabbitMQ queues:

rabbitmqctl list_queues

• How to check for purge a RabbitMQ queue:

rabbitmqctl purge_queue 

The default RabbitMQ configuration file (/etc/rabbitmq/rabbitmq.conf):

listeners.ssl.1 = 127.0.0.1:5671
listeners.ssl.2 = ::1:5671
listeners.tcp = none

ssl_options.versions.1 = tlsv1.2
ssl_options.cacertfile           = /etc/rabbitmq/rabbitmq_server_ssl.crt
ssl_options.certfile             = /etc/rabbitmq/rabbitmq_server_ssl.crt
ssl_options.keyfile              = /etc/rabbitmq/rabbitmq_server_ssl.key

ssl_options.verify               = verify_peer
ssl_options.fail_if_no_peer_cert = false
ssl_options.honor_cipher_order = true
ssl_options.honor_ecc_order    = true

ssl_options.ciphers.1 = TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
ssl_options.ciphers.2 = TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
ssl_options.ciphers.3 = TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
ssl_options.ciphers.4 = TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
ssl_options.ciphers.5 = TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
ssl_options.ciphers.6 = TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384


management.ssl.port       = 15671
management.ssl.ip       = 127.0.0.1
management.ssl.cacertfile = /etc/rabbitmq/rabbitmq_server_ssl.crt
management.ssl.certfile   = /etc/rabbitmq/rabbitmq_server_ssl.crt
management.ssl.keyfile    = /etc/rabbitmq/rabbitmq_server_ssl.key

management.ssl.honor_cipher_order   = true
management.ssl.honor_ecc_order      = true
management.ssl.client_renegotiation = false
management.ssl.secure_renegotiate   = true
management.ssl.versions.1 = tlsv1.2
management.ssl.ciphers.1 = TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
management.ssl.ciphers.2 = TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
management.ssl.ciphers.3 = TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
management.ssl.ciphers.4 = TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
management.ssl.ciphers.5 = TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
management.ssl.ciphers.6 = TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

If there are ongoing issues after reviewing the information and articles above, create a Service Request to get assistance from the Dell Technologies Avamar Support team.

Log files:

• /usr/local/avamar/var/rabbitmq/log/rabbit@localhost.log
• /var/log/rabbitmq
• /usr/local/avamar/var/mc/server_log/mcserver.log.0

• /var/log/messages
• /var/log/dpc/elg/ 
• /var/log/dpc/monitor
• /var/log/dpc/msm-ui-main

• Article Avamar: How to use the Goav RabbitMQ feature set