Jason Leydon
asked on
VMware Log Insight upgrade failing due to insufficient disk space
Unfortunately with Log Insight being a rather restrictive vApp with minimal technical documentation - I find it is difficult to troubleshoot certain issues. When the VM is created for Log Insight (3.3 in my case) it creates a 12.5gb which I believe is where the system itself lies and where subsequent upgrades would take place. There is plenty of storage for logs itself so I have narrowed down where my specific issue is to the disk with the OS and it cannot be expanded due to the nature of how the VM is designed.
After multiple restarts/shutdowns and trying multiple versions of the update (tried 3.6 and 4.0 upgrades) - I continue to receive an error that there is not enough space. I went through knowledge base articles and forum posts but could not find any related issues.
Anyone know how to even begin to troubleshoot this? I am wondering if there is a way to clear out cache files (perhaps previous upgrades that reside on the disk I need to expand.
After multiple restarts/shutdowns and trying multiple versions of the update (tried 3.6 and 4.0 upgrades) - I continue to receive an error that there is not enough space. I went through knowledge base articles and forum posts but could not find any related issues.
Anyone know how to even begin to troubleshoot this? I am wondering if there is a way to clear out cache files (perhaps previous upgrades that reside on the disk I need to expand.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Closing with this solution. Although it did not resolve my exact problem this does link to a KB that reflects where you can review the storage space available on this partition.
ASKER
They advised me to rebuild LogInsight instead with a clean copy of 4.0 and recreate my rules. This was not ideal but unfortunately I could not see a way around it. One thing to note is the fact that my 3.3 to 3.6 upgrade worked fine - which I then upgraded to 4.0. However, going from 3.0 to 3.3 to 3.6 is what failed.