Sending data to vCloud Usage Insight fails due to a connection timeout

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

When you click on SEND UPDATE TO VUI, under Settings, Send Update to Usage Insight in Usage Meter web application, the connection to vCloud Usage Insight fails with a timeout error.

The following error appears in uploader_main.log.
 

[2021-03-9 21:47:31]  | ERROR |       Notification-3 |    com.vmware.um.rawstorage.DataUploader | Uploader-<UUID_1> | Failed to upload Notification sequence number, '2157' and part number, '1' due to timeout com.vmware.um.restclient.TimeoutException: timeout
	at com.vmware.um.restclient.impl.OkHttpRequest.syncRequest(OkHttpRequest.java:57)
	at com.vmware.um.restclient.impl.OkHttpPost.send(OkHttpPost.java:103)
	at com.vmware.um.rawstorage.XferBase.sendData(XferBase.java:277)
	at com.vmware.um.rawstorage.DataUploader.retryableUpload(DataUploader.java:467)
	at com.vmware.um.rawstorage.DataUploader.start(DataUploader.java:248)
	at com.vmware.um.rawstorage.DataUploaderExecutor.lambda$run$0(DataUploaderExecutor.java:61)
	at java.util.HashMap.forEach(HashMap.java:1289)
	at com.vmware.um.rawstorage.DataUploaderExecutor.run(DataUploaderExecutor.java:61)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Testing connectivity with the following curl command shows that the connection from vCloud Usage Meter to vCloud Usage Insight is fine.      

curl -kv https://ums.cloud.vmware.com/um/api/v1/ping

Environment

VMware vCloud Usage Meter 4.x

Cause

This is an issue with vCloud Usage Meter 4.1.

Resolution

Upgrade to vCloud Usage Meter 4.3 to fix the issue.