This is a known issue and will be resolved in a future vCloud Usage Meter release.
Workaround:
To solve this issue, do the following:
- Log in to the vCloud Usage Meter appliance as root.
- Stop the journal service.
systemctl stop vmware-um-journal.service
- Go to the directory where the journal service database is located.
cd /opt/vmware/cloudusagemetering/platform/data/
- Connect to the database.
sqlite3 journal-service.db
- (Optional) Check the table names of the database.
.tables
- Delete the following data from the 'settings' table of the journal service database:
delete from settings where 1=1;
- Delete the following data from the 'custom_properties' table of the journal service database:
delete from custom_properties where 1=1;
- Quit the sqlite3 shell program.
.quit
- Start the Usage Meter journal service.
systemctl start vmware-um-journal.service