Avamar: Update Data Domain Fails with SSH Client is Not Authenticated Error
Summary: This article explains an issue where editing the Data Domain on an Avamar server results in 'Update Data Domain failed' error because 'SSH client not authenticated.' When adding a new Data Domain to an Avamar, the failure message is: "Unable to add SNMP Community string to Data Domain system." ...
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
When editing the Data Domain using Avamar User Interface (AUI), it fails with the error
Update DataDomain failed.

/usr/local/avamar/var/mc/server_log/mc-rest-api.log shows:
2024-12-18 15:01:54.077 WARN 8841 --- [AsyncTask-1] com.avamar.mc.api.task.AsyncTask: Unexpected error occurred in async task
com.avamar.mc.api.core.exception.RestClientException: Update DataDomain failed.
at com.avamar.mc.api.datadomain.service.DataDomainServiceImpl.updateDataDomain(DataDomainServiceImpl.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at org.springframework.aop.interceptor.AsyncExecutionInterceptor.lambda$invoke$0(AsyncExecutionInterceptor.java:115)
at org.springframework.aop.interceptor.AsyncExecutionAspectSupport.lambda$doSubmit$3(AsyncExecutionAspectSupport.java:276)
at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
2024-12-18 15:01:54.079 WARN 8841 --- [AsyncTask-1] com.avamar.mc.api.task.AsyncTask : Task.Error(code=31300, exception=com.avamar.mc.api.core.exception.RestClientException: Update DataDomain failed., details=null, event=Event(id=3984576, time=1734555714069, code=31300, category=APPLICATION, type=WARNING, severity=PROCESS, summary=Ssh client is not authenticated, domain=/, hasData=No, swSource=MCS:VM, source=EventSource(nodeId=av-server, programName=com.avamar.mc.datadomain.DataDomainService, sourceHardwareId=CKM01234567890_100-580-846-00-FFF, hardwareId=CKM01234567890_100-580-846-00-FFF, ddrName=dd-srv.lab.com, ddrId=8E72DC56A503F3865A0A418BFEF9414E3A4D7981, gsanVersion=19.10.0-135), data=EventData(attributes={dd=dd-srv.lab.com, ipv6Hostname=, user=ddboost, requestor={product=INTERNAL, role=Administrator, domain=/, host=192.168.1.110, user=MCUser}, ipv4Hostname=dd-srv.lab.com}), dataList=null, principal=UserPrincipal(id=69d23d7e-567e-4f98-ae2e-17367ec68f80, name=MCUser, domain=/, host=/192.168.1.110, product=INTERNAL, productVersion=null, role=ROOT), detail=null))
The /usr/local/avamar/var/mc/server_log/mcserver.log.0 shows the following exception:
Unsupported type: OPENSSH PRIVATE KEY 10/24-13:53:03.00526 [RMI TCP Connection(2239)-192.168.1.110#50125] com.avamar.mc.datadomain.DataDomainService._updateDdr FINE: Validate key based ssh connection when updating ddr 10/24-13:53:03.00526 [RMI TCP Connection(2239)-192.168.1.110#50125] com.avamar.asn.service.ServiceContainerImpl.getService FINE: Service get initiated to service: com.avamar.mc.prefs.MCSPreferencesService 10/24-13:53:03.00526 [RMI TCP Connection(2239)-192.168.1.110#50125] com.avamar.asn.service.ServiceContainerImpl.getService FINE: Service get completed for service: com.avamar.mc.prefs.MCSPreferencesService 10/24-13:53:03.00526 [RMI TCP Connection(2239)-192.168.1.110#50125] com.avamar.mc.datadomain.DdrSshUtils.loadJ2sshLicense INFO: Successfully load j2ssh license 10/24-13:53:03.00601 [RMI TCP Connection(2239)-192.168.1.110#50125] com.avamar.mc.util.MCException.logException WARNING: com.sshtools.publickey.InvalidPassphraseException: Unsupported type: OPENSSH PRIVATE KEY at com.sshtools.publickey.OpenSSHPrivateKeyFile.toKeyPair(OpenSSHPrivateKeyFile.java:79) at com.avamar.mc.datadomain.DdrSsh.createSshClient(DdrSsh.java:140) at com.avamar.mc.datadomain.DdrSsh.createSshClient(DdrSsh.java:189) at com.avamar.mc.datadomain.DdrSsh.validateCredentials(DdrSsh.java:283) at com.avamar.mc.datadomain.DataDomainService.validateKeyBasedSshConnection(DataDomainService.java:3563) at com.avamar.mc.datadomain.DataDomainService._updateDdr(DataDomainService.java:1179) at com.avamar.mc.datadomain.DataDomainService.updateDdr(DataDomainService.java:1036) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498)
Cause
The latest OS Security Rollup contains a new version of OpenSSH.
The previous OS Security Rollup version shows
The previous OS Security Rollup version shows
OpenSSH_7.2p2:
admin@av-serveradmin@av-server:~/>: awk -F'"' '/<package-survey/ {print $2}' /usr/local/avamar/var/package-survey-*post_errata* |sort|tail -1
2023-R3-v4
admin@av-server:~/>: ssh -V
OpenSSH_7.2p2, OpenSSL 1.0.2p-fips 14 Aug 2018 (OwB:1.5.9.0, BSAFE Micro Edition Suite:5.0.1.0)
admin@av-server:~/>: A recent OS Security Rollup version shows OpenSSH_8.4p1:
admin@av-server:~/>: awk -F'"' '/<package-survey/ {print $2}' /usr/local/avamar/var/package-survey-*post_errata* |sort|tail -1
2024-R3-v4
admin@av-server:~/>:
admin@av-server:~/>: ssh -V
OpenSSH_8.4p1, OpenSSL 1.1.1d 10 Sep 2019
admin@av-server:~/>:
The Management Console Server (MCS) does not support a private key with OPENSSH as the header, only RSA.
Resolution
This issue requires editing the
Contact Dell Support and reference this article ID. Dell Support must perform the edits.
mcddrcreate_sshkey file and regenerating the ddr_key.
Contact Dell Support and reference this article ID. Dell Support must perform the edits.
Affected Products
Avamar, Avamar ServerArticle Properties
Article Number: 000265265
Article Type: Solution
Last Modified: 02 Dec 2025
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.