Avamar: PDM schlägt mit Fehler beim Bereitstellen des Proxys fehl

Summary: Avamar: Das Bereitstellen von Proxys mit dem Proxy Deployment Manager (PDM) schlägt fehl: "Fehler bei der Bereitstellung des Proxys".

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

Bereitstellen von Proxys mithilfe von Proxy Deployment Manager schlägt mit Fehler bei Bereitstellen des Proxy fehl.

Zum Beispiel:

Fehler Proxy Deployment Manager

Cause

Der Avamar-Utility-Node kann während der Proxybereitstellung nicht mit dem ESX-Host auf Port 443 kommunizieren.

Wählen Sie im deploymanager.log (in /data01/avamar/var/log/vcs/ /tmp/proxydeploy/vcs/_

2016-05-15T21:57:10.329-0700 TRACE [cTaskExecutor-4][ impl.ConnectionManagerService# closeTicket]: Closing connection manager ticket: ...6c4657958ef8
2016-05-15T21:57:12.503-0700 TRACE [Thread-22 ][ util.VcConnection# keepAlive]: Keep-aliving VC session
2016-05-15T21:57:12.504-0700 TRACE [Thread-22 ][ impl.ConnectionManagerService# sendKeepAlive]: Keep-alive connection manager session: ...0de2820e9fc9
2016-05-15T21:57:12.611-0700 DEBUG [Thread-23 ][ worker.TaskWorker# updateProgress]: Updating task progress: 0
2016-05-15T21:57:12.616-0700 DEBUG [Thread-23 ][ events.VCSEvent# send]: Sending event: template: org.springframework.amqp.rabbit.core.RabbitTemplate@59074829 com.emc.avamar.vmware.vcs.deploymanager.deploy.status_event: com.emc.avamar.vmware.events.VCSEvent@2bf66009
2016-05-15T21:57:13.559-0700 ERROR [pool-8-thread-2][ worker.DeployWorker# run]: Error deploying proxy
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
at sun.security.ssl.BaseSSLSocketImpl.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
at com.emc.avamar.vmware.deploymanager.worker.DeployWorker.uploadVmdkFile(DeployWorker.java:917)
at com.emc.avamar.vmware.deploymanager.worker.DeployWorker.run(DeployWorker.java:340)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Resolution

Lassen Sie die Kommunikation zwischen dem Avamar-Raster und den ESXi-Hosts auf Port 443 zu, wie im Avamar for VMware-Benutzerhandbuch beschrieben:

Tabelle der erforderlichen Datenports

Affected Products

Avamar, Avamar Server

Products

Avamar
Article Properties
Article Number: 000170718
Article Type: Solution
Last Modified: 14 Jul 2026
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.