Spurious vStats and vTSDB Service Warnings During VCSA 8.0.3 File-Based Backups
search cancel

Spurious vStats and vTSDB Service Warnings During VCSA 8.0.3 File-Based Backups

book

Article ID: 372804

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • After upgrading vCenter Server Appliance (VCSA) to version 8.0.3, users may encounter warnings about vStats and vTSDB services failing to start when attempting to run VAMI file-based backups.
  • Logs show warnings about deprecated key derivation methods used for backup encryption. These warnings may be spurious, as the services are often running correctly despite the alerts.
  • Recently upgraded from an earlier version (e.g., 8.0.2)
  • vCenter High Availability (VCHA) may be enabled

Environment

  • vCenter Server Appliance 8.0.3 Build 24022515

Cause

The root cause appears to be related to how the backup process interacts with these services after the upgrade. While warnings may suggest service failures, the services are often running correctly, and backups may complete successfully despite these warnings.

Resolution

  1. Verify service status in VAMI:
    • Log in to the VCSA management interface (VAMI).
    • Navigate to the Services section.
    • Check the status of vStats and vTSDB services. They should be listed as running.
  2. Verify service status via command line:
    • Access the VCSA via SSH or console.
    • Run the following commands to check service status:
        service-control --status vmware-vpostgres
        service-control --status vmware-vmon
    • Ensure both services are listed as "running".
  3. Check service logs:
    • Still in the SSH/console session, examine the service logs:
        tail -n 100 /var/log/vmware/vmon/vmon.log
        tail -n 100 /var/log/vmware/vmware-vpostgres/postgresql-db.log
    • Look for any recent error messages or indications of service issues.
  4. Attempt a manual file-based backup:
    • In the VAMI, go to the Backup section.
    • Initiate a manual file-based backup.
    • Monitor the backup process for completion.
  5. Review backup logs:
    • Check /var/log/vmware/applmgmt/backup.log for warnings or errors.
    • Look for messages about "deprecated key derivation" which may appear as warnings but don't necessarily indicate backup failure.
  6. If services are verified as running and backups complete:
    • Consider these warnings as informational.
    • Continue to monitor backup success and verify backed up data integrity.
  7. If issues persist:
    • Collect a new set of VCSA log bundles.
    • Contact VMware Support for further assistance.
    1.  

Additional Information

Powered by Wolken Software