Banner "Failed to process journal=>read. Check your gw_main log for more details" Appears in Usage Meter After Successful Login

Products

• VMware Usage Meter

Issue/Introduction

• Upon successful login to Usage Meter UI, a red banner message appears with the title: Failed to process journal=>read. Check your gw_main log for more details
• The Notifications section in the vCloud Usage Meter UI appears empty.

• The following errors may be observed in various log files within the Usage Meter appliance:

/var/logs/gw_error.log:
####-##-## 16:03:03.405 ERROR --- [gateway_Runner] com.vmware.um.gw.GW                      : Cannot start platform client, journaling will be disabled.
com.vmware.um.common.err.UmException: Unable to login [401]: {"error":"invalid_client"}

/opt/vmware/cloudusagemetering/vmware-um-login.service.log:
[timestamp] ERROR 634 --- [0.#-####-####-#] c.v.v.u.auth.UmAppsClientRepository      : Failed to read ot parse passwd file /opt/vmware/cloudusagemetering/platform/security/.passwd
##### 15:45:55 vCloud UsageMeter FQDN #####-#####-#######.sh[634]: java.io.FileNotFoundException: /opt/vmware/cloudusagemetering/platform/security/.passwd (Permission denied)

/var/logs/gw_main.log:
####-##-## 16:33:25.108 WARN --- [#####-#######-######-#] c.v.um. common. usage. UsageDataArchive : Month dir .. /umdata/Collection/2023/03 doesn't contain zip files
####-##-## 16:33:25.109 INFO --- [#####-#######-######-#] c.v.um. common. usage. UsageDataArchive : 2023 2

Environment

VMware vCloud Usage Meter 4.8

Cause

• The issue is caused by incorrect file ownership permissions for the .passwd file located in: /opt/vmware/cloudusagemetering/platform/security/
• Sample output of the ls -al command:
  usagemeter@test$ ls -al /opt/vmware/cloudusagemetering/platform/security/
  total 400
  -r-------- 1 usagemeter usagemeter 550 Mar 28 2024 .passwd
  -rw-rw-r-- 1 usagemeter usagemeter 179029 May 27 16:12 cacerts
  -rw-r----- 1 usagemeter usagemeter 4369 May 27 16:12 keystore
  -rw-r--r-- 1 login-service login-service 4363 May 27 16:01 sign-keystore
• The .passwd file should be owned by the login-service user, but currently it is owned by usagemeter, which results in a permission issue.

Resolution

To resolve the issue,

• Change the ownership of .passwd to login-service by running the below command
  
  chown login-service:login-service /opt/vmware/cloudusagemetering/platform/security/.passwd
  
  
• Reboot the Usage Meter appliance.