Loading...
Loading...
This issue can occur if the Cloud Disaster Recovery Agent (CDRA) runs out of memory and swap space, causing the CDRA VM to become unresponsive. A reboot can be performed to clear the memory. To confirm the issue, check the monitor_cdra.log for memory usage prior to reboot. From monitor_cdra.log : prcVrtMem prcResMem prcNumThreads prcTime sysSwapSize sysSwapUsed MemTotal MemFree 7174865 3354992 168 Mon Feb 11 06:15:39 2019 630780 630780 3881036 86412 7174865 3355092 168 Mon Feb 11 06:15:39 2019 630780 630780 3881036 107308 NA NA NA NA 630780 0 3881028 3537172 6940033 1650848 81 Thu Apr 25 19:35:55 2019 630780 0 3881028 1499704 6994245 1673680 94 Thu Apr 25 19:35:56 2019 630780 0 3881028 1399284 In the above example, (prior to the CDRA reboot) the Java process utilized 3.3 GB, swap was full, and the number of threads was 168. This confirms the out-of-memory issue causing the CDRA GUI to become unresponsive.
High Java utilization is causing the CDRA to become unresponsive and disconnect from CDRS. Cloud DR version 18.3.0.1 has a known memory leak issue which is addressed in Cloud DR release 18.3.0.4.
Perform the following steps to address this issue: Login to the vCenter running the on premise CDRA VM. Reboot the CDRA VM and start a ping test to confirm its availability after reboot. Login to the CDRA GUI, and go to log collection section to confirm the out-of-memory issue has been resolved. Upgrade Cloud Disaster Recovery to version 18.3.0.4 or later to fix the memory leak issue and avoid this issue from recurring.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.