Diagnostics Log Assist: No connectivity to the Cloud Proxy

Products

• VCF Operations

Issue/Introduction

When selecting more than one ESX host object for Log Assist, customers report the error message “No connectivity to the Cloud Proxy” during the validation process. 

log-assist/log/spring.log on the Cloud Proxy will have the following message around the time of the failed validation. 

[main] com.vmware.vcops.logassist.Main          : Started Main in N seconds

Environment

VCF Operations 9.0.x

Cause

In general the issue is caused because of a GET esxcfg-info request performed during validation. The larger the returned info is, the more memory will be needed. Selecting multiple hosts will multiply that memory.

Resolution

This issue is resolved in VCF Operations 9.1.

To workaround this issue you will need to increase the memory configuration of the Log Assist Application. 

To increase the memory of the Log Assist Application:

1. SSH to the cloud proxy VM
2. Execute:

vi /storage/db/vmware-vrops-cprc/configuration/cprc.containers.env.configuration

add:

export JVM_OPTS="-Xmx800m -Xms800m"

Save the file.

3. Reboot the VM.
4. Test if the issue persists.

 

If the issue persists then you can increase the memory of the Log Assist Container and the Log Assist Application even further. 

To increase the memory of the Log Assist Container:

Open /usr/lib/vmware-vcopssuite/utilities/conf/vcopsmemconf.xml and find the <service> block for log-assist.

You need to increase both the minMemoryAllocationMb (to force it to give you the memory) and the maxMemoryAllocationMb (so the system doesn't block it).

Change the block to look like this:

<service>

<name>log-assist</name>

<!-- 1. Force the system to give it at least 2048 MB -->

<minMemoryAllocationMb>2048</minMemoryAllocationMb>

<!-- 2. Raise the maximums so they don't block the 2048 MB minimum -->

<maxMemoryAllocationMb size="xsmall">2048</maxMemoryAllocationMb>

<maxMemoryAllocationMb size="small">2048</maxMemoryAllocationMb>

<maxMemoryAllocationMb size="medium">2048</maxMemoryAllocationMb>

<maxMemoryAllocationMb size="large">2048</maxMemoryAllocationMb>

<initAllocationPercent>10</initAllocationPercent>

<pointsMemoryAllocation>15</pointsMemoryAllocation>

<cpuAllocationPercent>40</cpuAllocationPercent>

<role>remoteCollector</role>

</service> 

 

This will increase the container memory to 2gb. Then increase the Java application limit to 70-80% of the container limit.

(editing the /storage/db/vmware-vrops-cprc/configuration/cprc.containers.env.configuration file)