Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

The /var/log partition of the ESX host runs out of space due to vmkiscsid.log growth (1027622)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 11693Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When running VMware ESX 4.x with a software iSCSI initiator, you see these symptoms:

Running the df command in the host terminal shows that the partition /var/log is 100% full. For more information, see Investigating disk space on an ESX or ESXi host (1003564).

The log file /var/log/vmkernel does not update.

The log file /var/log/vmkiscsid.log or /var/log/vmkiscsid.log is very large.

Cause

On VMware ESX 4.x, the software iSCSI daemon log file at /var/log/vmkiscsid.log is not rotated or cleared, unlike other syslog-generated log files. Therefore, the vmkiscsid.log file grows to a very large size if the host has experienced, or is experiencing, ongoing communication issues with the iSCSI storage.

Resolution

Solution

This issue is resolved by ESX 4.0 Update 3, released 2011-05-05. After installing this update, 600KB of vmkiscsid logs are retained, across 6 files. For more information, see the release notes at https://www.vmware.com/support/vsphere4/doc/vsp_esx40_u3_rel_notes.html.

Workaround for ESX 4.0

If you need the software iSCSI client logs for troubleshooting purposes, archive them prior to reboot. See the Additional Information section.

Reboot the ESX 4.0 host.

The file /var/log/vmkiscsid.log is erased during startup and the space used by the file is released.

Workaround for ESX 4.1

Reboot the ESX 4.1 host.

The file /var/log/vmkiscsid.log is rotated to /var/log/vmkiscsid.log.previous during startup.

If you need the software iSCSI client logs for troubleshooting purposes, archive them following the reboot. See the Additional Information section.

Delete the older file using a command similar to:

rm /var/log/vmkiscsid.log.previous

Related Information

If there is rapid logging to the /var/log/vmkiscsid.log file, investigate underlying iSCSI storage connectivity issue by reviewing your storage target configuration and system logs.

Make a compressed backup of the /var/log/vmkiscsid.log or vmkiscsid.log.previous files before deleting them or rebooting the host, in case this information is needed for troubleshooting purposes. Archive the file to a location with sufficient space, such as a datastore. For example, use a command similar to:

tar czvf /vmfs/volumes/DatastoreName/vmkiscsid.tgz /var/log/vmkiscsid.log*

Note:

To view this file, you can extract the file using an archive manager.

The archive can be relocated back to /var/log/ after the system reboots to keep the system logs in a single location.

Investigating disk space on an ESX or ESXi host

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Support Assistant