Avamar: DPC unable to connect to Avamar after upgrade

Summary: After a DPC upgrade, the DPC server cannot connect to the Avamar Server. The connection check hangs during the Certificate Validation phase. The issue occurs due to a Message Broker and RabbitMQ configuration problem between DPC and Avama ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

  • DPC fails to connect to the Avamar Server after a successful upgrade.
  • The connection validation process does not complete.
  • Running the following command hangs during the Certificate Validation phase: 
    goav rabbitmq check-dpc-connection
  • The Avamar logs report Message Broker and RabbitMQ related failures similar to the following: 
    java.lang.Exception: Failed to config message broker -- Failed to delcear queues and shovels.
        at com.emc.clp.plugin.avamar.task.AvamarRemoteTaskManager.getStatusUpdate(AvamarRemoteTaskManager.java:96)
        at com.emc.clp.task.TaskServiceImpl.lambda$auditTask$10(TaskServiceImpl.java:539)
        at java.base/java.util.Optional.ifPresent(Optional.java:183)
        at com.emc.clp.task.TaskServiceImpl.auditTask(TaskServiceImpl.java:535)
        at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
        at com.emc.clp.task.TaskServiceImpl.auditTasks(TaskServiceImpl.java:522)
        at jdk.internal.reflect.GeneratedMethodAccessor270.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84)
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
2026-01-16 11:26:18,181 WARN scheduling-24 c.e.c.t.TaskServiceImpl Task failed: com.emc.clp.plugin.avamar.activation.QuickSetupRemoteTask@5703e069
java.util.concurrent.CompletionException: java.lang.Exception: Failed to config message broker -- Failed to delcear queues and shovels.
        at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:331)



Cause

The root cause remains unknown. The issue appears when existing Message Broker configuration, queues, shovels, or certificates remain inconsistent after a DPC upgrade.

Resolution

Steps to follow

Follow Step A to reset the Message Broker and RabbitMQ configuration. If the issue continues, follow Step B.

Step A: Reset Message Broker And RabbitMQ Configuration

  1. Log in to the Avamar Server as the root user.
  2. Stop the RabbitMQ service:  
    service rabbitmq-server stop
  3. Stop the Message  
    Broker:msgbrokerctl.pl --stop
  4. Remove the Message Broker shovel configuration:  
    msgbrokerctl.pl --remove
  5. Verify certificate removal under the following directory:  
    /etc/rabbitmq/
     The directory previously contained:  
    root_ec_cert.pem
client_ec_pri_key.pem
client_ec_csr.csr
client_ec_cert.pem
keystore.p12
    After running the remove command, the system automatically deletes these files. Manual deletion is not required.
  6. Start the Message  
    Broker: msgbrokerctl.pl --start
  7. Start the RabbitMQ service:  
    service rabbitmq-server start
  8. Verify the RabbitMQ and shovel status:  
    service rabbitmq-server status
rabbitmqctl eval 'rabbit_shovel_status:status().'
  9. Remove the Avamar Server from DPC.
  10. Add the Avamar Server back to DPC.
  11. Verify that the following certificates regenerate under /etc/rabbitmq/ after registration: 
    root_ec_cert.pem
client_ec_pri_key.pem
client_ec_csr.csr
client_ec_cert.pem
keystore.p12

Step B: Register Avamar Using Message Broker Quick Setup

If Step A does not resolve the issue, register the Avamar Server manually using the following command: 

mccli msgbroker quicksetup --host=<dpc_hostname> --user=<dpc-userName> -pass=<dpc_password>

After registration, verify that DPC connects successfully to the Avamar Server and that certificate validation completes.

 

Additional Information

Additional Information / Notes

  • The msgbrokerctl.pl --remove command automatically removes RabbitMQ certificates.
  • Manual certificate deletion does not provide additional benefit.
  • Re-adding the Avamar Server to DPC after completing Step A resolves the issue in most cases.
  • The procedure applies only to supported Avamar and DPC versions.

Affected Products

Avamar Server, Avamar Virtual Edition
Article Properties
Article Number: 000426699
Article Type: Solution
Last Modified: 07 Apr 2026
Version:  1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.