Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"Generic error during the SSL Handshake" error when configuring replications between VDCs in the same vCloud Director instance in vCloud Availability (75005)

Last Updated: 10/16/2019Categories: TroubleshootingTotal Views: 6198Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Configuring a replication from one Virtual Data Center (VDC) to another in the same vCloud Director instance fails with the error:

Generic error during the SSL Handshake

In /opt/vmware/h4/cloud/log/cloud.log on the vApp Replication Manager, you see similar messages to:

2019-09-30 11:31:20.146 DEBUG - [36e06245-3a50-48ae-af9c-7c8349a6159b] [c4-scheduler-1] c.v.h.c.service.ManagerHealthChecker     : Connected to manager 00000000-0000-0000-0000-000000000000 (https://localhost:8044)
2019-09-30 11:47:35.325 ERROR - [UI__88909003-fe13-4afd-b7c3-223b01372878_Cj] [job-2] com.vmware.h4.jobengine.JobExecution     : Task 6e0bc563-19e0-47c7-8d9e-e3d94b24d226 (WorkflowInfo{type='start', resourceType='vmReplication', resourceId='C4-4356235-d2e3-4764-4230-d0b1eaa554c9', isPrivate=false, resourceName='null'}) has failed
com.vmware.exception.GenericSSLException: Remote host closed connection during handshake
at com.vmware.exception.converter.ClientExceptionConverter.convertException(ClientExceptionConverter.java:52)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
at com.vmware.rest.client.AbstractRestClient.genericExchange(AbstractRestClient.java:134)
... 28 common frames omitted
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at sun.security.ssl.InputRecord.read(InputRecord.java:505)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975)
... 44 common frames omitted

In /opt/vmware/h4/replicator/log/replicator.log on the Replicator, you see a similar message:

2019-09-30 11:30:48.275  WARN - [e97f6685-d1d4-40d1-8016-ed3f195227e3] [health-check-2] c.v.r.health.HealthCheckingFactory       : Resource is broken: RestSettings{baseURI=https://192.168.1.52:8044, timeout=10000, maxConn=2, sniHostname='null', hostnameVerifier=com.vmware.rest.client.security.NoopHostnameVerifier@1f, clientCertificate=ClientCertificate{keystorePath='./config/keystore.p12', keystoreAlias='replicator'}, trustManager=com.vmware.rest.client.security.ShaTrustManager@b0e1ac98, authenticator=null}
com.vmware.exception.ConnectionRefusedException: Connect to 192.168.1.52:8044 [/192.168.1.52] failed: Connection refused (Connection refused)
at com.vmware.exception.converter.ClientExceptionConverter.convertException(ClientExceptionConverter.java:42)
at com.vmware.rest.client.AbstractRestClient.genericExchange(AbstractRestClient.java:146)
at com.vmware.rest.client.json.RestClient.exchange(RestClient.java:96)
...
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to 192.168.1.52:8044 [/192.168.1.52] failed: Connection refused (Connection refused)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:156)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
...
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
...

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue can occur when the vCloud Availability Tunnel and Replicator appliances are unable to connect to the vCloud Availability Replication Manager over port 8044 which is required for vCloud Availability service management traffic.

Resolution

To resolve this issue, ensure that the vCloud Availability Replication Manager is accessible over port 8044 from the vCloud Availability Tunnel and Replicator appliances on your network.

If this issue persists after validating your network settings, contact VMware Support and note this Article ID (75005) in the problem description. For more information, see How to Submit a Support Request.

Related Information

For more information on port requirements, see the VMware vCloud Availability Network Ports Configuration section of the vCloud Availability documentation.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
[VMC on AWS] VMware HCX の導入後にパブリック IP アドレスが自動的に割り当てられる (75035)

KB
•
利用持有者令牌 - 检索用户信息：包含用户数据的已解码 base64 持有者令牌中存在不一致问题 (75137)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware vCloud Availability 3.0.x

Take Our Survey

Support Assistant