root [ /opt/vmware/support/logs/dr ]# systemctl status srm-server.srm-server. service - VMware Site Recovery Manager ServerLoaded: loaded (/usr/lib/systemd/system/srm-server.service; disabled; vendor preset: enabled)Active: failed (Result: signal) since Tue 2026-01-20 04:03:48 UTC; 6min agoProcess: 2359482 ExecStart=/opt/vmware/srm/bin/vmware-dr /opt/vmware/srm/conf/vmware-dr.xml (code=killed, signal=ABRT)Main PID: 2359482 (code=killed, signal=ABRT)
Jan 20 04:03:48 srm-server systemd[1]: srm-server. service: Main process exited, code=killed, status=6/ABRTJan 20 04:03:48 srm-server systemd[1]: srm-server. service: Failed with result 'signal'.Jan 20 04:03:48 srm-server systemd[1]: Failed to start VMware Site Recovery Manager Server.Jan 20 04:03:48 srm-server systemd[1]: srm-server. service: Scheduled restart job, restart counter is at 3.Jan 20 04:03:48 srm-server systemd[1]: Stopped VMware Site Recovery Manager Server.Jan 20 04:03:48 srm-server systemd[1]: srm-server. service: Start request repeated too quickly.Jan 20 04:03:48 srm-server systemd[1]: srm-server. service: Failed with result 'signal'.Jan 20 04:03:48 srm-server systemd[1]: Failed to start VMware Site Recovery Manager Server.
The issue is seen when the SRM site is missing license and shows "Unlicensed". If you validate the license, one of the site may show "Unlicensed"
You can validate this under licensing section on vCenter as below.
In order to resolve the issue, we need to apply the license for the site showing "Unlicensed".
You may refer the instructions in the KB article How to Install and Activate the VMware Live Site Recovery (formerly Site Recovery Manager) License Key for fixing the license.
Fixing the license and starting the SRM service on SRM server is expected to start the issue and resolve connectivity issues with vCenter server.