lcm.service - VMware Cloud Foundation Lifecycle Management Service
Loaded: loaded (/etc/systemd/system/lcm.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since
Process: 34524 ExecStart=/opt/vmware/vcf/lcm/lcm-app/bin/lcm (code=exited, status=1/FAILURE)
Process: 34525 ExecStartPost=/usr/bin/sh -c /bin/test -f /var/log/vmware/vcf/lcm/lcm.out && /bin/chown vcf_lcm:vcf /var/log/vmware/vcf/lcm/lcm.out (code=exited, status=0/SUCCESS)
Process: 34528 ExecStartPost=/usr/bin/sh -c /bin/test -f /var/log/vmware/vcf/lcm/lcm.err && /bin/chown vcf_lcm:vcf /var/log/vmware/vcf/lcm/lcm.err (code=exited, status=0/SUCCESS)
Main PID: 34524 (code=exited, status=1/FAILURE)
CPU: 2.394s
/opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties is empty or missing essential configuration parameters.systemctl status lcm shows the service repeatedly attempting to restart.The application-prod.properties configuration file has been corrupted, cleared, or lost.
This may result from a previous system error or transient failure. As this file contains essential connectivity parameters (e.g., database credentials, depot adapter settings), the LCM service cannot initialize without a valid configuration.
If the application-prod.properties file is empty and no local backups are available, the configuration must be restored from a known-good source, such as a lab environment running the exact same VCF version.
Caution: Make sure to use a source configuration from an environment running the identical VCF/SDDC Manager version to avoid configuration mismatches.
# systemctl stop lcm
/opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties file./opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties.# chown vcf_lcm:vcf /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties
# chmod 644 /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties
# systemctl start lcm