Avamar:虚拟机代理注册停止响应
Summary: 虚拟机代理注册停止响应
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
将 Avamar Server 升级到了 v7.3
Avamar Server 升级到 Avamar v7.3 后,代理服务器注册停止工作。尝试重新注册时,系统停止响应并显示“UN-Registering with the MCS”
从代理端,尝试运行 initproxyappliance.sh 以将代理注册到 MCS 时。avagent.log显示以下信息。它进入挂起状态。
2016/11/02-22:59:23.70883 [avagent] Debug output redirected 2016-11-02 22:59:23 avagent Info <5008>: Logging to /usr/local/avamarclient/var/avagent.log 2016/11/02-22:59:23.70892 [avagent] Config: VARDIR=/usr/local/avamarclient/var, HOMEDIR=/root 2016/11/02-22:59:23.70893 [avagent] Looking for flag file "/usr/local/avamarclient/var/avamar.cmd" 2016/11/02-22:59:23.70895 [avagent] Looking for flag file "/usr/local/avamarclient/var/avagent.cmd" 2016-11-02 22:59:23 avagent Info <5702>: Command Line: /usr/local/avamarclient/bin/avagent.bin --quiet --init --daemon=false --listenport=28009 --bindir="/usr/local/avamarclient/bin" --vardir="/usr/local/avamarclient/var" --sysdir="/usr/local/avamarclient/etc" --logfile="/usr/local/avamarclient/var/avagent.log" --logtimeformat=default --logtimezone=default --mcsaddr="AvamarHostName" --listenport=28009 --dpndomain="/Avamar_Proxies" 2016-11-02 22:59:23 avagent Info <5703>: Parsed Flags: /usr/local/avamarclient/bin/avagent.bin --quiet --initialize --service=false --acport=28009 --bindir=/usr/local/avamarclient/bin --vardir=/usr/local/avamarclient/var --sysdir=/usr/local/avamarclient/etc --logfile=/usr/local/avamarclient/var/avagent.log --logtimeformat=default --logtimezone=default --mcsaddr=AvamarHostName --acport=xxxx --dpndomain=/Avamar_Proxies 2016-11-02 22:59:23 avagent Info <6601>: Hostnamelist: 127.x.x.x,avamarproxy2.domainname,avamarproxy2,10.xxx.xx.67 2016-11-02 22:59:23 avagent Info <6609>: UN-Registering with the MCS (10.xxx.xx.63)
在 Avamar Server 端,MCS 日志显示以下错误:
root@avamar1:/usr/local/avamar/var/mc/server_log/#: grep '10.xxx.xx.67' mcserver.log.0 WARNING: Cl->MC 10.xxx.xx.67:47147: Can not process client request. Peer not authenticated FINE: MC->Cl 10.xxx.xx.67:47147 <message errno="100002" errdesc="SSL-related operations failed: Peer not authenticated" ack="no" type="response" sync="fg" /> WARNING: thread :pool-7-thread-20 connection to 10.xxx.xx.67:47147 took 24140 mseconds WARNING: Cl->MC 10.xxx.xx.67:47151: Can not process client request. Peer not authenticated FINE: MC->Cl 10.xxx.xx.67:47151 <message errno="100002" errdesc="SSL-related operations failed: Peer not authenticated" ack="no" type="response" sync="fg" /> WARNING: Cl->MC 10.xxx.xx.67:47152: Can not process client request. Peer not authenticated FINE: MC->Cl 10.xxx.xx.67:47152 <message errno="100002" errdesc="SSL-related operations failed: Peer not authenticated" ack="no" type="response" sync="fg" /> WARNING: thread :pool-7-thread-9 connection to 10.xxx.xx.67:47152 took 30029 mseconds WARNING: Cl->MC 10.xxx.xx.67:47153: Can not process client request. Peer not authenticated FINE: MC->Cl 10.xxx.xx.67:47153 <message errno="100002" errdesc="SSL-related operations failed: Peer not authenticated" ack="no" type="response" sync="fg" /> WARNING: Cl->MC 10.xxx.xx.67:47155: Can not process client request. Peer not authenticated FINE: MC->Cl 10.xxx.xx.67:47155 <message errno="100002" errdesc="SSL-related operations failed: Peer not authenticated" ack="no" type="response" sync="fg" /> WARNING: thread :pool-7-thread-12 connection to 10.xxx.xx.67:47155 took 8766 mseconds
Cause
对于版本 7.3.0.226,默认情况下启用客户端-服务器身份验证。
以下是此问题的两个已知原因:
- 客户端或 Data Domain 系统上的证书不正确
- Data Domain 系统上的时间与 Avamar Server 上的时间不同步(约 >2 分钟)
Resolution
有关解决方法,请参阅知识库 文章484773 (需要戴尔支持帐户才能查看本文)
Affected Products
AvamarProducts
AvamarArticle Properties
Article Number: 000063156
Article Type: Solution
Last Modified: 23 Jun 2026
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.