SDDC Manager services fail to start due to invalid permissions on files

Products

• VMware SDDC Manager

Issue/Introduction

SDDC Manager services (like Operations Manager, Domain Manager, LCM) fails to start after making changes to the application-prod.properties file. 

Environment

SDDC 4.x
SDDC 5.x

Cause

Ownership of the application-prod.properties / application.properties file was incorrectly set, where the expected ownership should be under vcf_servicename:vcf 

The file ownership might change during copy operation while creating backups for the files. 

For Example - 

Resolution

Change the ownership of the application-prod.properties/application.properties file to vcf_servicename:vcf

1. Take a snapshot of the SDDC manager 
2. Take SSH session to SDDC manager with vcf user and elevate to root 

3. If LCM service is impacted -

• Navigate to the directory - /opt/vmware/vcf/lcm/lcm-app/conf
• Command to change the ownership -

chown vcf_lcm:lcm filename

• LCM service should be in ACTIVE (Running) state now. Command to check the status of the LCM service - 

systemctl status lcm 

4. If Operationsmanager service is impacted - 

• Navigate to the directory - /etc/vmware/vcf/operationsmanager/
• Command to change ownership - 

chown vcf_operationsmanager:vcf filename

•  Operationsmanager service should be in ACTIVE (Running) state now. Command to check the status of the Operationsmanager service - 

systemctl status operationsmanager

5. If Domainmanager service is impacted - 

• Navigate to the directory - /etc/vmware/vcf/domainmanager/
• Command to change ownership - 

chown vcf_domainmanager:vcf filename

• Domainmanager service should be in ACTIVE (Running) state now. Command to check the status of the Domainmanager service - 

systemctl status domainmanager

Additional Information

Example log snippets for operations manager service from operationsmanager.out file