I got the following health status when logging in to vCenter Server Appliance console the other day. Not quite sure how to proceed to fix this. Using the Google machine, there are several scenarios where you could clear out the files or expand the drive size.
Fix Threads:
VCSA 5.5: vCenter 5.5 appliance space issue /storage/core out of space
Different folder: The / filesystem is low on disk space or inodes VCSA
Increasing Drive Size VCSA 6.0: Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.0 (2126276) | VMware ...
Deleting Files VCSA 6.0U1: How to Fix /storage/core filesystem Out of Disk Space Error on VCSA 6.0U1
This is what I'm seeing in my /storage/core folder:
I'm not sure if it's safe to clear out the folder, or to expand the drive. I'm afraid there's another issue that is causing the folder to fill up, so either of these "fixes" may just be a bandaid to the underlying issue.
Hello,
I was able to find a couple of thread below which may match the log details on your system
https://communities.vmware.com/thread/491749
https://communities.vmware.com/thread/549087
https://communities.vmware.com/thread/547262
Is it possible those are email dumps because snmp alert emails aren't getting sent out due to the bug with the smtp script? We ran in to something similar when we discovered our email alerts werent sending and had over 50k queued emails.
[EDIT]
Check out this kb. It said 6.5, but we saw the issue with 65u1 too. -- Email alerts for alarms are not delivered on vCenter Server Appliance 6.5 (2148396) | VMware KB
Also- FWIW, check out /var/spool/mqueue/ on your vcsa(s)... ours had over 50k messages waiting to be sent.
[/EDIT]
I had two of these in my original post. They discuss removing *.tgz files, but these seem to be related to snmp traps.
My /var/spool/mqueue folder is empty, so I don't think it backed up email message queues.
I have this issue with VCSA 6.5.0.21000 in a new project, only 1 VM, VCSA.
This problem appears after patch VCSA.
Photon problem?
I remove files core* in /storage/core folder and the system is healthly again.
That seems mostly a bug. Reach out to VMware support . They might provide an updated rpm for snmpd to fix the issue.
Problem solved after I got new version of vmware-snmp-1.1.9.rpm from support