Avamar: root-to-root replication reports "Cannot connect to Avamar dispatcher" due to mismatched passwords between source and target

Summary: How to address an Avamar root-to-root (R2$) replication that reports "Exit code 15: Cannot connect to Avamar dispatcher" due to mismatched passwords.

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.

Symptoms

During a root-to-root replication, the following error is observed:

0  ERROR!  Exit code 15: Cannot connect to Avamar dispatcher
 

Performing login tests from both the Source to the Target Avamar, and Target to Source Avamar fail:

Source Avamar to target Avamar:

avmgr logn --avamaronly --server=Target_Avamar_FQDN --id=root --ap=password --encrypt=tls --encrypt-strength=high
0  ERROR!  Exit code 69: Authentication failure  (Invalid password?  User disabled?)
2024/08/11-23:25:05.71559 [avmgr]  ERROR: <0001> uplinkcallbase::send   Could not send message to dispatcher
 

Target Avamar to Source Avamar:

avmgr logn --avamaronly --server=Source__Avamar_FQDN --id=root --ap=password --encrypt=tls --encrypt-strength=high 
0  ERROR!  Exit code 69: Authentication failure  (Invalid password?  User disabled?)
2024/08/11-23:30:05.81652 [avmgr]  ERROR: <0001> uplinkcallbase::send   Could not send message to dispatcher

Cause

The passwords for MCUser, root, and admin are mismatched between the Source and target.

Resolution

1. Verify that there are no connection timeouts.

2. Configure the same password on the Source and target Avamar Grid for root, admin, and MCUser using the change-passwords utility.

3. Stop the Avamar firewall service on all nodes on both the source and target grids:

Single node (as root): 

service avfirewall stop
 

Multinode grid (as root with root keys loaded):

mapall --noerror --all+ --user=root service avfirewall stop

For instructions on loading keys see Avamar: How to Log in to an Avamar Server and Load Various Keys.

4. Repeat login tests from the source and target grid.

Wanted results:

Source grid:

avmgr logn --avamaronly --server=Target_Avamar_Grid --id=root --ap=password --encrypt=tls --encrypt-strength=high
1  Request succeeded
-1  privilege level  (enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2)
2  block type  (directory)
 
avmgr logn --avamaronly --server=Target_Avamar_Grid --id=root --ap=password--encrypt=proprietary
1  Request succeeded
-1  privilege level  (enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2)
2  block type  (directory)
 
avmgr logn --avamaronly --server=Target_Avamar_Grid --id=root --ap=password--encrypt=tls --encrypt=ssl --encrypt-strength=high
1  Request succeeded
-1  privilege level  (enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2)
2  block type  (directory)
 

Target grid:

avmgr logn --avamaronly --server=Source_Avamar_Grid --id=root --ap=password --encrypt=tls --encrypt-strength=high
1  Request succeeded
-1  privilege level  (enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2)
2  block type  (directory)
 
avmgr logn --avamaronly --server=Source_Avamar_Grid --id=root --ap=password--encrypt=proprietary
1  Request succeeded
-1  privilege level  (enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2)
2  block type  (directory)
 
avmgr logn --avamaronly --server=Source_Avamar_Grid --id=root --ap=password--encrypt=tls --encrypt=ssl --encrypt-strength=high
1  Request succeeded
-1  privilege level  (enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2)
2  block type  (directory)

Affected Products

Avamar, Avamar Server
Article Properties
Article Number: 000037515
Article Type: Solution
Last Modified: 12 Aug 2025
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.