So today I wanted to resolve the fact my VCSA would say low memory on the VAMI health page.
I was about to attempt the fix provided by the contributor, since the answer by the employee just lead me down the rabbit hole of what the vsphere-pod service was.
I was on 7.0.2 of vCenter, and noticed there was a recent update to 7.0.3 I proceeded to update. After it was done everything seemed to be working fine and I was curious if it resolved the low memory health warning in VAMI. To my dismay, when I navigated to the VAMI port URL, I was greeted with nothing more then a spinning “Loading” circle.
When I opened an incognito window, and attempted to log in I was greeted with “unable to login” . Googling lead me to the linked reference, which after reading I noticed it talking about the service “applmgmt”.
I decided to give restarting the service a shot.
service-control –stop applemgmt
then start it back up
service-control –start applemgmt
Lucky for me it worked, and I was able to login (at least via a incognito window). The issue with my main browser seemed to be cache, so I pressed F12, opened the dev tools, then right clicked the refresh icon and clicked “Empty Cache and Hard refresh” which resolved my issue.
When I got into VAMI the health was all green which resolved me low memory issue as well. 🙂
This is a quick post on the latest security release notification from VMware.
If for whatever reason an update is not possible you can follow these workarounds.
While you can use VUM to distribute updates and patches to ESXi hosts.
You’ll have to use VAMI for updating vCenter.
You can download the latest patches here (vmware account required).
I did this on my lab vCenter, took a lil while but not bad.
- Made a backup of the VCSA using Veeam
- Shutdown Veeam or any other backup solution that might use vCenter
- Notified anyone that might use vCenter that it would be inaccessible during update
- Attached ISO to VCSA VM (You can do as 4sysops did and upload to a datastore, or you can simply open the VCSA console via VMRC, and attach the ISO from your Downloads folder)
- Log into VAMI (https://vcsa:5480)
- Click Update on left nav, then Update -> Check CD-ROM
- The update should be available as the option, then click Stage and Install
- Accept the EULA, use/don’t use CEIP, Check I have a backup, Click Install.
It could take an hour or so, then everything is back to running state, here’s the summary page after completion:
You can read the alternative methods such as using CLI, or how to handle a vCenter HA cluster upgrade using the link above to 4sysops guide on upgrading vCenter.
Sorry this post is not as extensive as usual, just a heads up about the latest VMware patches. Stay Safe out there.