VMware.IaaS.Management.Agent.exe.Config file corrupted - unable to start the management agent
search cancel

VMware.IaaS.Management.Agent.exe.Config file corrupted - unable to start the management agent

book

Article ID: 319622

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • In the VAMI update tab, you see an error message similar to:
Management Agent automatic upgrade failed. For details refer to /opt/vmware/var/log/vami/updatecli.log file.
  • In /var/log/bootstrap/preupdate.log file on the main VA, you see an error similar to:
The Management Agent upgrade did not finish within the expected time on the nodes listed below. Make sure the Management Agent is up and running on them and that it has connectivity to the VA. Check the Management Agent log for details.<br / >vra01dem01b.rainpole.local<br / >
  • In VAMI Cluster tab the above mentioned node(s) show longer "Last connected" period than expected (for IaaS nodes the default interval is 30 seconds unless configured differently).
  • After logging on the affected node(s) and opening the Services console the "vCloud Automation Center Management Agent" service is not running.
  • The Management Agent's configuration file (located at <management_agent_installation_folder>\VMware.IaaS.Management.Agent.exe.config) is corrupted - it is either blank or filled only with tabs/NULs depending on the text editor used.


Environment

VMware vRealize Automation 7.4.x
VMware vRealize Automation 7.3.x

Resolution

  1. Rename file "<management_agent_installation_folder>\VMware.IaaS.Management.Agent.exe.Config.bak" to "<management_agent_installation_folder>\VMware.IaaS.Management.Agent.exe.config" overwriting the corrupted configuration file.
  2. Restart the "vCloud Automation Center Management Agent" service from Services console.
  3. Open the VAMI Cluster page and make sure the node's connectivity is restored looking at the "Last connected" column.


Powered by Wolken Software