Log bundle filename shows UTC instead of the configured timezone after upgrading to vCenter Server 8.x
Article ID: 449702
Updated On:
Products
Issue/Introduction
After upgrading vCenter Server to version 8.x from 7.x, you may observe the following conditions:
- When generating and downloading a log bundle via the vSphere Client, the timestamp included in the filename (e.g., [email protected]) is recorded in UTC, rather than the timezone configured on the appliance (such as JST).
- Prior to the upgrade, the log bundle filename reflected the configured local timezone.
- Checking the OS-level time on the appliance (using the date command) displays the correctly configured local timezone.
Environment
VMware vCenter Server 8.x
Cause
During the upgrade process, the newly deployed vCenter Server appliance initially starts its core services in the UTC timezone. In the subsequent data migration phase, the OS-level timezone configuration from the legacy vCenter Server is copied and applied to the new appliance.
However, the services that are already running retain the UTC timezone information from their initial startup. The updated timezone configuration is not dynamically applied to these active processes.
As a result, the services continue to generate logs and output filenames based on UTC until they are restarted.
Resolution
To resolve this issue, restart the vCenter Server services to force them to reload the timezone configuration.
For detailed instructions on restarting (stopping, starting) vCenter Server Appliance services, please refer to KB 344633 (linked in the Additional Information section).
1. Connect to the vCenter Server Appliance via SSH using the root account.
2. Run the following command to restart all services:
service-control --stop --all && service-control --start --all
Additional Information
Feedback
