Avamar: VM-proxyregistrering slutter å svare
Summary: VM-proxyregistrering slutter å svare
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
Oppgradert Avamar-server til v7.3
Etter at Avamar-serveren ble oppgradert til Avamar v7.3, sluttet registreringen av proxy-serveren å fungere. Når du prøver å registrere deg på nytt, slutter den å svare på "UN-Registering with the MCS"
Fra proxy-siden, når du prøver å kjøre initproxyappliance.sh for å registrere proxy til MCS. Følgende avagent.log viser følgende informasjon. Den gikk i hengetilstand.
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)
Fra Avamar-serversiden viser MCS-loggen følgende feil:
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
Med versjon 7.3.0.226 er klient-servergodkjenning aktivert som standard.
Her er de to kjente årsakene til dette problemet:
- Feil sertifikat på klienten eller på Data Domain-systemet
- Tiden på Data Domain-systemet er ikke synkronisert med tiden på Avamar Server (ca. >2 min)
Resolution
Se kb 484773 for løsning (det kreves en Dell Support-konto for å se denne artikkelen)
Affected Products
AvamarProducts
AvamarArticle Properties
Article Number: 000063156
Article Type: Solution
Last Modified: 04 Mar 2026
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.