Storage Replication Adapter (SRA) missing from the SRM UI and a message is displayed in the UI as 'No storage replication adapters installed'

Products

• VMware Live Recovery

Issue/Introduction

When accessing the Site Recovery Manager UI (https://SRM-FQDN/dr), and selecting the 'Storage Replications Tab', the following message is displayed:

'No storage replication adapters installed'

When clicking on 'Rescan Adapters' the following message is displayed:

Description: * 

ERROR Unable to find the storage replication adapter. 
ERROR Storage replication adapter is not installed.

Environment

Site Recovery Manager 8.x, 9.x

Cause

• The SRA log partition is full.
  
  root@srm [ ~ ]# df -h
  Filesystem                      Size  Used Avail Use% Mounted on
  devtmpfs                        4.0M     0  4.0M   0% /dev
  tmpfs                           4.9G   44K  4.9G   1% /dev/shm
  tmpfs                           2.0G  856K  2.0G   1% /run
  tmpfs                           4.0M     0  4.0M   0% /sys/fs/cgroup
  /dev/sda4                        14G  5.5G  7.4G  43% /
  tmpfs                           4.9G  488K  4.9G   1% /tmp
  /dev/sda2                       238M   36M  190M  16% /boot
  /dev/mapper/support_vg-support  3.9G  555M  3.2G  15% /opt/vmware/support
  /dev/loop0                      378M  358M     0 100% /opt/vmware/support/logs/srm/SRAs
  
  
  
• Unmanaged SRM or SRA logs within the appliance can fill up support partition disk. This results in failure of the SRM server service because there's no space left on the disk for the services to write logs. 
• srm-server service stops unexpectedly 
  
  vmware-dr.log: 

--> Panic: Scheduled function triggered exception:
--> NSt10filesystem7__cxx1116filesystem_errorE filesystem error: cannot create directory: No space left on device [/var/log/vmware/srm/SRAs/sha256_#####################################]
--> Backtrace:
--> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 9.0.2, build: build-24401761, tag: vmware-dr, cpu: x86_64, os: linux, buildType: release
--> backtrace[00] libvmacore.so[0x00252482]: Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
--> backtrace[01] libvmacore.so[0x0022B207]: Vmacore::System::SystemFactory::CreateBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)
--> backtrace[02] libvmacore.so[0x0048CA7B]
--> backtrace[03] libvmacore.so[0x0048CB82]: Vmacore::PanicExit(char const*)
--> backtrace[04] libdr-storage.so[0x000EB55B]
--> backtrace[05] libdr-storage.so[0x0014CB40]
--> backtrace[06] libvmacore.so[0x003429CE]
--> backtrace[07] libvmacore.so[0x003442D2]
--> backtrace[08] libvmacore.so[0x00497DE0]
--> backtrace[09] libpthread.so.0[0x00008EB0]
--> backtrace[10] libc.so.6[0x000FFADF]
--> backtrace[11] (no module)
--> [backtrace end]

         Or:

2026-03-10T13:34:23.143-04:00 error vmware-dr[03448] [SRM@6876 sub=Storage] Command queryInfo's stderr:
--> --- Logging error ---
--> Traceback (most recent call last):
-->   File "logging/__init__.py", line 1114, in emit
-->   File "logging/__init__.py", line 1094, in flush
--> OSError: [Errno 28] No space left on device
--> Call stack:
-->   File "__main__.py", line 12, in <module>
-->   File "sra/executor.py", line 108, in start
-->   File "logging/__init__.py", line 1489, in info
-->   File "logging/__init__.py", line 1634, in _log
-->   File "logging/__init__.py", line 1644, in handle
-->   File "logging/__init__.py", line 1706, in callHandlers
-->   File "logging/__init__.py", line 978, in handle
-->   File "logging/__init__.py", line 1230, in emit
-->   File "logging/__init__.py", line 1118, in emit
--> Message: 'Version SRA Framework: 3.1.0.167'
--> Arguments: ()
--> --- Logging error ---
--> Traceback (most recent call last):
-->   File "logging/__init__.py", line 1114, in emit
-->   File "logging/__init__.py", line 1094, in flush
--> OSError: [Errno 28] No space left on device
--> Call stack:
-->   File "__main__.py", line 12, in <module>
-->   File "sra/executor.py", line 113, in start
-->   File "logging/__init__.py", line 1489, in info
-->   File "logging/__init__.py", line 1634, in _log
-->   File "logging/__init__.py", line 1644, in handle
-->   File "logging/__init__.py", line 1706, in callHandlers
-->   File "logging/__init__.py", line 978, in handle
-->   File "logging/__init__.py", line 1230, in emit
-->   File "logging/__init__.py", line 1118, in emit

The SRM appliance has two main disks: system and support.
The support disk is partitioned into lvm ext4 filesystem & is used to store the logs of VMware-related services. The mount point of the partition is "/opt/vmware/support"
Some SRAs (Storage Replication Adapter) lack an inbuilt log rotation & compression software or don't have a limit on the size of logs they produce. This will result in the unplanned failure of the SRM server services due to the lack of any space available on disk for the log files.

 

Resolution

Delete/move old logs files from location " /opt/vmware/support/logs/srm/SRAs" or create a cron job to execute SRAs log rotation everyday following KB : SRM services stop due to unmanaged SRA log files