To resolve the issue, ensure that this vpxd.json file is formatted correctly, compared to vCenter which is in a healthy state on a similar version and if necessary can use its contents to update the file.
Note - Take a valid backup/snapshot of the vCenter VM before making any changes
Steps to be Taken -
- Navigate to the directory highlighted below -
- cd /etc/vmware/vmware-vmon/svcCfgfiles/
- Do not copy the backup file in /etc/vmware/vmware-vmon/svcCfgfiles, make a copy or take a backup of the file to /var/tmp or /root directories.
- cp vpxd.json /var/tmp/vpxd.json.bkp
- Edit the file now
- Press "I" or Insert to edit the file content.
- Delete the contents currently there
- Paste in contents retrieved from the healthy VCSA node (right click)
- Press "Esc" then ":wq!" to save
- Restart all of the VCSA services now -
- service-control --stop --all && service-control --start --all
- VPXD should now be showing up as valid and trying to start up - if it still fails, check the location /var/log/vmware/vmon/vmon.log to see if issues with reading file /var/run/vpxd/vmware-vpxd-health-status.xml
- If it is missing when you check the directory - run a "vi" command to create this in the directory:
- vi vmware-vpxd-health-status.xml
- Start the remaining services now
- service-control --start --all
- Services should now all be up and running and vCenter server accessible