Today I received an error in my vCenter Server:
“Could not connect to one or more vCenter Server systems“
This surprised me, because this environment is a quiet one without any kind of special configuration.
In this article I want to share what happened and how I resolved the issue.
Could not connect to one or more vCenter Server systems
My first thought was to reboot the system as it was running for quite some time, but this wasn’t helpfull.
Next step was to check the Appliance Management interface on port 5480.
Here I found the cause of my problem:
The nice thing is that the health status already provides the solution for my issue: Increase the size of disk /storage/seat or decrease the data retention.
When you navigate to Monitor > Disks you can find the proof that the disk is actually full:
I don’t want to give in on data retention, so I will expand the disk.
There’s good VMware KB article to guide us through expanding the disk here: VMware KB 2145603
Log on to the ESXi host the VCSA is running on.
Expand the disk as shown below:
Connect to the VCSA appliance via SSH with your root credentials and run the following commands:
shell.set --enabled true
shell
# Shows current status of the disks
df -h
# Expand the disk
/usr/lib/applmgmt/support/scripts/autogrow.sh
# Check if the disk has expanded
df -h
Reboot your VCSA and find it working again! 🙂
PS. Check our vCloud Director related articles here.
13,690 total views, 1 views today
Did you leave out a step requiring the user to expand the disk through vcenter before running autogrow.sh?
Problem is…. this is just a work around. Why would a VCSA run out of space on that partition? I ask because I have the same problem and it was a default install and hardly any usage. I’ve done the install twice now and both have ended up in the exact same situation after only two (2) months of idling.