This week i upgraded an usagemeter from 22.214.171.124 to 126.96.36.199 with the inplace upgrade method.
Usage Meter 188.8.131.52 patch release rolled out on May 23rd. This release addresses a major issue found in Usage Meter 4.5. For more information i refer to the following blog:
The release notes can be found at:
We followed the upgrade guide provided by VMware:
After the reboot and check if the upgrade was successful we tried to send a test update to the Usage Insight. The test send of data failed with thw following error:
In the notifications we can find the following messages:
After a search through the VMware Knowlegde Base I came across this article:
To test connectivity to vCloud Usage Insight by using the curl command:
curl -kv https://ums.cloud.vmware.com/um/api/v1/ping --proxy 192.168.1.50:8080
The response came back with HTTP status code 200, so that was OK.
Now we check the vCloud Usage Meter registration status in vCloud Usage Insight by using the curl command:
curl -kv https://ums.cloud.vmware.com/um/api/v1/upload/registration?um=<UM UUID> --proxy 192.168.1.50:8080
This response also came back with HTTP status code 200, so AOK, so far for the checks…
Let’s get in touch with GSS
As this was the advice all along in the first error message ….
The GSS engineer stated that there was an issue with the nginx jvm settings when using a proxy.
We had to add a line to the nginx.conf in the following directory, but before we change anything lets make a snapshot of the system in case we ruin everything.
Remark: Please contact GSS if you want support editing files, and always make a backup or in this case a snapshot before changing settings
Edit the nginx.conf and add the follwing line somewhere around line 58,
This line set a dummy file for proxy configuration., we are setting a dummy proxy configuration as we are hitting a known issue and this will be fixed in a future release.
Go down one dir to
Stop NGINX service with the follwing command:
Now start the service again:
Start NGINX service
Now get the status of all services:
You see a lot of errors, these can be ignored.
Now go to the VAMI UI and reset the proxy again:
Now go to the Settings Page in the Usage Meter UI and Send an update to Usage Insight.
It works! You can also check the usagemeter in Insight: Go to https://ums.cloud.vmware.com/ui/
The last update should be after the issue was fixed!
Remark: Please contact GSS if you want support editing files, and always make a backup or in this acse a snapshot before changing settings