VMware Cloud Community
hezronm
Contributor
Contributor
Jump to solution

invocation failed with "java.net.SocketTimeoutException: Read timed out" Read timed out

I am trying to configure SRM8.2 for windows and windows based vcenter but I am getting an error."nvocation failed with "java.net.SocketTimeoutException: Read timed out" Read timed out" Not sure what I am doing wrong, The SRM server and vcenter have dns configured with fqdn and checks out correctly. No ports are blocked by the firewall. The error is followed by what I can call a soft crash of SRM because I loose the connection the srm server. "SRM Server at srmvm04cert.xxxxx is unreachable

Failed to connect to Site Recovery Manager Server at https://srmvm04cert.xxxx:9086/vcdr/vmomi/sdk. Reason: https://srmvm04cert.xxxx:9086/vcdr/vmomi/sdk invocation failed with "java.net.SocketTimeoutException: Read timed out" Read timed out

Operation ID: 769b7972-3f9f-4411-8986-750387d176b0

Any help will be appreaciated.

I am using SRM 8.2 (VMware-srm-8.2.0-13480383) and vcenter is 67u2b

Reply
0 Kudos
1 Solution

Accepted Solutions
hezronm
Contributor
Contributor
Jump to solution

VMware has a fix in the works on next release 8.2.0.2

View solution in original post

Reply
0 Kudos
3 Replies
hezronm
Contributor
Contributor
Jump to solution

On looking through the vmware-dr log I found out the following...

2019-08-19T20:33:39.013-06:00 info vmware-dr[01840] [SRM@6876 sub=Recovery opID=cf99c4c3-aa86-4aa7-8cf7-1244efe5c84b-retrievePropertiesEx:d166] [526a1] GetTask called for plan: dr.recovery.RecoveryPlan:5d2d3ae2-3146-4bb8-8ab5-58e4810ce9cd:61d38f29-6091-4c9e-ad77-bfa3093becf7

2019-08-19T20:33:39.013-06:00 panic vmware-dr[01388] [SRM@6876 sub=Default opID=7172b8ab-ce51-43cc-b037-e0c72b18bc9b-reprotect:4ba7:53fe:1ed7]

-->

--> Panic: Assert Failed: !deviceGroupIdMap.empty() || !deviceIdMap.empty() (Dr::Storage::Operations::ReplicationManager::ReverseReplication: Both deviceGroupMap and deviceIdMap can be empty) @ ..\..\src\storage\operations\replicationManager.cpp:433

--> Backtrace:

--> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 8.2.0, build: build-13480383, tag: vmware-dr, cpu: x86_64, os: windows, buildType: release

--> backtrace[00] vmacore.dll[0x00252430]

--> backtrace[01] vmacore.dll[0x0006CEE0]

--> backtrace[02] vmacore.dll[0x00063F70]

--> backtrace[03] vmacore.dll[0x0006614E]

--> backtrace[04] vmacore.dll[0x00226CE1]

--> backtrace[05] vmacore.dll[0x00226E51]

--> backtrace[06] dr-storage.dll[0x003C7E12]

Reply
0 Kudos
hezronm
Contributor
Contributor
Jump to solution

VMware has a fix in the works on next release 8.2.0.2

Reply
0 Kudos
AmitDhankad
Contributor
Contributor
Jump to solution

Hi, please check ping from VRM to Vcenter and vice versa, also make both VRM and Vcenter entry in /etc/hosts file.

Reply
0 Kudos