---
title: "Log Exhaustion on vCenter"
canonical: "https://www.virtcloudrocks.com/space/VSPHTECH01/852200/Log%20Exhaustion%20on%20vCenter"
format: markdown
---
## Problem

Today a critical issue appeared on one of our vCenter servers - below it can be seen the details

`vSphere UI Health Alarm", "Log disk exhaustion on vcenter name"`

Performing some research I reached a relevant VMware KB → 

> Macro (auibutton)

## Solution

To resolve the issue we followed below steps,

> Macro (ui-steps)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)

### /storage/log partition full due to Large Java dump files created under /storage/log/vmware/perfcharts in vCenter Server Appliance

> Macro (ui-steps)
> 
> > Macro (legacy-content)

### /storage/log becomes 100% full when exporting the vCenter Appliance log bundles

> Macro (ui-steps)
> 
> > Macro (legacy-content)

### vCenter Appliance /storage/log partition full due to excessive pod-startup.log file

Not applicable in our case

### VCSA /storage/log/ partition runs out of space due to java hprof dumps created by VMware Analytics service

Check below symptoms,

- /storage/log/vmware/analytics/ folder has a number of java hprof files
- The  analytics-runtime.log-0.stdout file shows an "OutOfMemoryError"

![image](media://792d1c0d-21ee-443a-8895-4da79d664fb8)

In our case that wasn't the issue.

### vCenter Server Appliance 7.0.x /storage/log partition runs out of space due to VMware Analytics service log file (analytics-runtime.log.stderr) (85468)

> Macro (ui-steps)
> 
> Check below symptoms
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)

### Further Troubleshooting

> Macro (ui-steps)
> 
> Check for and remove excessive PostgreSQL service health alarm log files  
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)

### Additional checks

Additionally checks for logs that creating capacity issues can be done by running below commands,

```shell
# cd /storage/log/
# du -a |sort -n -r |head -n 20
```

This will give you details of subfolders which have high capacity → you can check individual subdirectories and remove not needed files.