2024-12-05T00:00:25,163+0000 ERROR [Metering Calculation worker thread 3] com.vmware.vcops.analytics.metering.meteringengine.MeteringCalculationEngine.calc - Unable to get any value for metric cost|effectiveDailyStoragecost in time range from 1733337000000 to 1733423400000: most probably cost and pricing engine start times are out of sync, please make sure that pricing engine is scheduled after cost engine completed
2024-12-05T00:00:25,184+0000 ERROR [Metering Calculation worker thread 1] com.vmware.vcops.analytics.metering.meteringengine.MeteringCalculationEngine.calc - Unable to get any value for metric cost|effectiveDailyStoragecost in time range from 1733337000000 to 1733423400000: most probably cost and pricing engine start times are out of sync, please make sure that pricing engine is scheduled after cost engine completed
This issue occurs when VMware Aria Operations and VMware Aria Automation are not configured to use the same time zone.
Log into the VMware Aria Operations admin UI as the local admin user.
Click Take Offline under Cluster Status.
Note: Wait for Cluster Status to show as Offline.
Log in to the desired node as root via SSH or Console.
Delete the current localtime
file by running this command:
rm /etc/localtime
Get a list of the time zone locations and cities by running the following command, and noting the desired timezone location and city:
ls -l /usr/share/zoneinfo/
Set the time zone by running this command:
ln -s /usr/share/zoneinfo/location/city /etc/localtime
Note: Replace location and city with the location and city noted in step 5.
Example: ln -s /usr/share/zoneinfo/America/city /etc/localtime
Reboot the node for the changes to take effect.
Repeat steps 3-7 on all desired nodes in the cluster.
Log into the VMware Aria Operations admin UI as the local admin user.
Click Bring Online under Cluster Status.
Note: Wait for the Cluster Status to show as Online.