Generating logs from ESXi host fails with error: "Operation request timeout"
search cancel

Generating logs from ESXi host fails with error: "Operation request timeout"

book

Article ID: 334698

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Generating logs from ESXi host through vSphere Client or vCenter Server fails with the error:

    Operation request timeout
  • This issue is observed on all ESXi 5.5 hosts in the cluster.
  • Collecting logs through command line creates .tgz files with the log bundle and fails with the error:

    cmd /usr/lib/vmware/vm-support/bin/partedUtil.sh timed out after 20.0039680004 seconds due to lack of progress in last 10 seconds (0 bytes read)
    cmd /usr/lib/vmware/vm-support/bin/storageHostProfiles.sh timed out after 1800.00476694 seconds due to lack of progress in last 900 seconds (0 bytes read)

  • Running the command /usr/lib/vmware/vm-support/bin/storageHostProfiles.sh fails with the error:

    Warning: Device /dev/disks/naa.####################### has a logical sector size of 4096. Not all parts of GNU Parted support this at the moment, and the working code is HIGHLY EXPERIMENTAL.
    *** glibc detected *** <unknown>: double free or corruption (!prev): 0x1f000200 ***
    *** glibc detected *** <unknown>: malloc(): memory corruption: 0x1f000440 ***

Environment

VMware vSphere ESXi 5.5

Cause

The issue occurs if one of the LUN mounted on the host is created with 4096 byte sectors instead of the traditional 512 byte sectors.

Resolution

To resolve this issue, detach the LUN formatted with 4096 bytes from all the hosts.