After rebooting the VMware vCenter Appliance (VCSA) VM  the Appliance Monitoring Service and vami service does not start automatically.

If we manually start  vmware-statsmonitor & vami it starts  fine, but not at normal boot.

In the /var/log/vmware/applmgmt.log you may see errors similar to:

============
<statsmonitor> Service api-health command’s stderr: Error getting service health. Error: Failed to read health xml file: /var/vmware/applmgmt/statsmonitor_health.xml. Error: [Errno 2] No such file or directory: ‘/var/vmware/applmgmt/statsmonitor_health.xml’
——
2019-12-23T08:23:17.112 [39525]DEBUG:vmware.appliance.update.update_functions:Error reading fss override file [Errno 2] No such file or directory: ‘/etc/vmware/vsphereFeatures/b2b_fss_override.json’
2019-12-23T08:23:17.112 [39525]DEBUG:vmware.appliance.update.update_functions:Error reading fss override file 
============

Follow these steps in order to workaround the issue:

1. Modify statsmonitor service config for vMon to set higher startup timeout:

sed -i '/StartTimeout/d' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json
sed -i '/ApiHealthFile/a "StartTimeout": 600,' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json

2.  kill -HUP $(cat /var/run/vmon.pid)

3.  # Stop and start statsmonitor service explicitly.

  /usr/lib/vmware-vmon/vmon-cli -k statsmonitor
  /usr/lib/vmware-vmon/vmon-cli -i statsmonitor

Now reboot the VCSA and check after 10-15 mins and the Statsmonitor Service should start up automatically.

Note: Increasing the boot-up start delay for the statsmonitor service  fixes the issue

Advertisement