Why is my Kace VM disk filling up?
First, in subscriptions in the patch management settings in Kace; I configured the subscription for only the Adobe publisher, chose all classifications, and all severities. I then went into the Patch and Feature Update Download Setting, toggled all subscribed files under patching, and finally toggled File Download after signature download. I had this set to run at 3AM.
I was then moving onto the schedules section of patch management, but I noticed I was not able to hit my Kace webUI, after a few minutes it was still not responding so I looked at the ESXI box that is hosting the Kace VM. The ESXI box showed that the 100GB disk was now 100% full (it was only about 20% full before), and in the event log for the Kace VM I see nothing but an error saying "There is no more space for virtual disk 'k1000.vmdk'. You might be able to continue this session by freeing disk space on the relevant volume, and clicking Retry. Click Cancel to terminate this session."
Ok, its obvious that something with the Adobe patch has caused my drive to fill. The problem is I can't search within the k1000.vmdk file to see what exactly is filling the drive, or see what I can delete. Right now, the Kace VM will function normally for about three minutes if I restart the Kace VM on the ESXI box, but after about three minutes a window will pop up on the ESXI box saying the same 'There is no more space for virtual disk 'k1000.vmdk...' error, when this error window pops up it will automatically shutdown the Kace VM. I will restart the Kace VM in the ESXI box, and during the three minute window I have rolled back all changes I have made, I deleted all patch files and feature update files in the Patch and Feature Update Download Settings, and I even did a backup and restore from the last backup before I made any changes. None of these steps have resulted in the disk space going back to it's usual 20% filled capacity. I will say however that when looking at the patch management page it does say 'Starting package file download' under the catalog header, not sure why this is as nothing is configured to be downloaded. Also, looking in the patch catalog, if I change the view to Downloaded, the catalog is empty, so I don't believe I have any patches downloaded.
You're probably wondering why we just don't expand the disk size of the VM, well the ESXI box is only hosted on a 256gb SSD, with other apps running on it, so there isn't really much disk space to expand.
Anyways, I'm just wondering if there is anything I can delete to free up space, or if there is a way to navigate the k1000.vmdk to see what might be using the space. Perhaps there is something I need to check to confirm nothing is attempted at getting downloaded? The fact that the VM will run for three minutes before giving me that 'there is no more space' error makes me think it is still trying to download something, even though I have canceled and terminated all downloading processes.
Anyways, ANY suggestion would be highly appreciated. Thank you.
The SMA appliance is available in 1TB or 3TB virtual disk size. The ESX datastore should be provisioned for the appropriate size.
See documentation for product requirements.
Although you may have thin-provisioned the VM, the virtual disk can reach the maximum disk size.
This is a VMware ESX message. "There is no more space for virtual disk 'k1000.vmdk"
The deletion of patches..etc will have no affect. The ESX datastore is too small.
Delete your backups, delete all patches in your database and turn off downloads, that may give you just enough space to recover, but you will need to increase the disk .
we had a cloud based system, with next to nothing running and it was always running out of space. You will need at least that 1tb if you want to use your SMA for anything useful