"Error in method invocation Timeout happens while sending message to microservice" when updating or patching vCenter Server Appliance from VAMI or CLI
search cancel

"Error in method invocation Timeout happens while sending message to microservice" when updating or patching vCenter Server Appliance from VAMI or CLI

book

Article ID: 345487

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Updating or Patching vCenter Server Appliance fails with this error during pre-checks:

"Error in method invocation Timeout happens while sending message to microservice"

In the /var/log/vmware/applmgmt/applmgmt.log file, there are see entries similar to:

ERROR - Checksum does not match, expected [HASH], found [HASH]
ERROR - Checkoum failed for file (...blob)
DEBUG: vmware.appliance.update.update_functions:Exception happens while sending message to microservice: ConnectionRefusedError(111, 'Connection refused')
DEBUG: vmware.appliance.update.update_functions:Exception happens while sending message to microservice: FileNotFoundError (, 'No such file or directory')

The following entries may appear in /var/log/vmware/applmgmt/applmgmt.log if the attached patch file is corrupted:

DEBUG: vmware.appliance.update.update_functions:Exception happens while sending message to microservice:FileNotFoundError (, 'No such file or directory')
INFO: vmware.appliance.update.update_functions:Timeout
ERROR: vmware.vapi.provider.local:Error in invoking com.vmware.appliance.update.pending in precheck sending message to microservice

Environment

  • VMware vCenter 6.x
  • VMware vCenter 7.x
  • VMware vCenter 8.x

Cause

This issue occurs due to a stale PID file of the update microservice or a corrupted/incomplete FP.ISO file used for the upgrade.

Resolution

Workaround 1: 

Clear Stale PID

  1. Connect to the VCSA using SSH.
  2. Navigate to /var/run/vmware/applmgmt/.
  3. Check for the PID file: ls update_microservice.pid.
  4. Remove the file: rm /var/run/vmware/applmgmt/update_microservice.pid.
  5. Restart the management service: service-control --restart applmgmt.
  6. Retry the patching process.

Workaround 2: 

Verify Media Integrity

  1. Re-download the FP.ISO from the official Broadcom Support Portal.
  2. Verify the SHA-256 checksum of the downloaded file against the value listed on the download page.
  3. Mount the new ISO and re-initiate the patching process via VAMI or CLI.

Additional Information

Clear VAMI installation progress

Check media checksum