Vpxd logs are not captured during vCenter log bundle collection
search cancel

Vpxd logs are not captured during vCenter log bundle collection

book

Article ID: 438932

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

When generating a VMware vCenter Server log bundle, the resulting bundle is missing the contents of the /var/log/vmware/vpxd/ directory, even though the logs are present on the vCenter Server Appliance (VCSA) filesystem.

During the log collection process using the vc-support command, the following error message is seen:

INFO errlog.py:22 Execution of action "copy IGNORE_MISSING,RECURSE /var/log/vmware/vpxd/" raised exception of type "EOFError": Compressed file ended before the end-of-stream marker was reached

Environment

vCenter 8.x

Cause

The issue is caused by a corrupted or incomplete compressed file within the vpxd log directory, specifically files ending in .gz.part.

The vc-support tool attempts to parse or copy all files in the directory. When it encounters a .part file (which is an incomplete download or a partial write), the compression stream is malformed. This triggers an EOFError (End of File Error), causing the log collector to abort the copy operation for the entire directory to prevent a crash.

Resolution

Identify and remove the invalid .part file from the VCSA.

1. Identify the Corrupt File

  1. Log in to the vCenter Server Appliance via SSH as root.

  2. Navigate to the vpxd log directory: cd /var/log/vmware/vpxd/

  3. List any files with the .part extension: ls -lh *.gz.part (Example found: vpxd-profiler-38.log.gz.part)

2. Remove the Invalid File

Remove the identified file to allow the log collector to skip over the corruption: rm vpxd-profiler-38.log.gz.part

3. Validate the Fix

Rerun the log bundle collection command: vc-support

The collector should now bypass the error and successfully include the /var/log/vmware/vpxd/ directory in the final bundle.

Additional Information

Removing these .part files is safe, as they are incomplete fragments and do not contain usable diagnostic data. Their presence usually indicates a previous log rotation or copy process that was interrupted.

Powered by Wolken Software