Search the VMware Knowledge Base (KB)
View by Article ID

Redirecting system logs to a vSAN object causes an ESXi host lock up (2147541)

  • 1 Ratings

Symptoms

When systems logs or the ESXi host scratch partition are stored on the vSAN datastore, it can cause the ESXi host to become unresponsive to vCenter Server and the host CLI.

Cause

In certain rare scenarios, the system logger and other processes on the ESXi host may not be able to update files in the scratch space. This is typically, though not exclusively, associated with another event that causes vSAN storage operations to fail to process IO from these processes. When this issue occurs, it can cause the host to become completely non-responsive, including the inability to interact with the host via a command-line interface.

Resolution

If this issue occurs, reboot the ESXi host to recover manageability of the host.

To prevent this issue occurring, do not store system logs or scratch locations on the vSAN datastore. 

For more information about configuring system scratch partitions and the syslog configuration, see: 

See Also

Update History

04/18/2017 - Added vSAN 6.6 to Products

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.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 1 Ratings
Actions
KB: