vmware-updatemgr service does not start in the vCenter
search cancel

vmware-updatemgr service does not start in the vCenter

book

Article ID: 383946

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • The output of command service-control --status --all on the vCenter shows vmware-updatemgr is in stopped state.
  • When accessing Lifecycle Manager in the vCenter UI the following error is observed "Problem occurred while connecting to Lifecycle Manager server".
  • In the /var/log/vmware/vpxd/vpxd.log, an error similar to the one below relating the vpxd-extension user is logged:

    YYYY-MM-DDTHH:MM:SS vcenter-FQDN vpxd[8407]: Event [140584360] [1-1] [YYYY-MM-DDTHH:MM:SS.831645Z] [vim.event.EventEx] [warning] [] [] [140584360] [Privilege check failed for user VSPHERE.LOCAL\vpxd-extension-xxxx-xxxx-xxxx for missing permission Extension.Update. Session user performing the check: ]

Environment

vCenter Server Appliance 7.x

Cause

This issue occurs because the vpxd-extension user is missing from the vCenter Global Permissions.

Resolution

Note: Take a snapshot of the vCenter.

  • Add the vpxd-extension user: VSPHERE.LOCAL\vpxd-extension-xxxx-xxxx-xxxx user to the Global Permissions and give it the Administrator role.

  • Restart the vCenter services:

    service-control --stop --all

    service-control --start --all

  • The vmware-updatemgr service should now start, this can be verified by running command: service-control --status --all