The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
ESXi host is unable to generate support logs because local storage is full (1007329)
- When attempting to collect ESXi host logs, you see an error that states that the network copy failed for a specific file.
- A support file is created, but its size is zero bytes.
- You see this message:
Could not copy /var/log to tar area. Have you run out of disk space?
To prevent this issue from occurring again, consider:
- Why were the logs taking up so much space? Logspew of this kind may be an indicator of a problem, and therefore must not be ignored unless you know the cause.
- Use remote logging
To redirect system log files to a remote host:
Note: This article assumes that you have a syslog server configured. For an example of how to setup a syslogd server, see the Red Hat article How do I direct logs from all the systems in my network to one centralized server in Red Hat Enterprise Linux? (this requires a Red Hat login). If you do not have a Red Hat login, see the content and user forums on syslog.org for instructions and support on configuring syslog.
- From vSphere Infrastructure Client, select the host in the inventory.
- Click the Configuration tab.
- In the Software section, click Advanced Settings.
- Click Syslog.
- For Syslog.Remote.Hostname, enter a host name to which syslog data can be forwarded.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.