SRM appliance unable to connect with Error "503 Service Unavailable".
search cancel

SRM appliance unable to connect with Error "503 Service Unavailable".

book

Article ID: 389617

calendar_today

Updated On:

Products

Issue/Introduction

Symptoms:

  • While accessing SRM UI, below error appears on the banner:
               

        Unable to retrieve pairs from extension server at xxxxxxxxxxx. Unable to connect to Site Recovery Manager Server at xxxxxxxxxxx. Reason: Unable to download versions file from Site Recovery Manager Server at xxxxxxxxxxx. Http response: HTTP/1,1 503 Service Unavailable.

  • SRM pairing shows disconnected as below screenshot,

  • This is expected as the services are in stopped state, due to this communication fails between SRM pairs.

Steps To Validate:

  • From below dr-client.log we have error,
    2025-02-28 16:13:03,184 [srm-reactive-thread-15] WARN  com.vmware.srm.client.infrastructure.requestHandlers.navigation.SitePairHelper -5521004966068210375 593d3eb4-5c51-4157-b69a-6786fd8b3905 getDrSitePairs - Fail to get SRM sitePairData for SrmServerImpl {_guid = 7e366da4-4b7a-4365-ace0-e91317e0f197_url = https://xxxxSRM:443/drserver/vcdr/vmomi/sdk
    }:
    com.vmware.srm.client.topology.client.view.availability.ExtensionServer$GetPairFailedException: Unable to retrieve pairs from extension server at https://xxxxSRM:443/drserver/vcdr/vmomi/sdk.Unable to connect to Site Recovery Manager Server at https://xxxxSRM:443/drserver/vcdr/vmomi/sdk. Reason: java.net.UnknownHostException: xxxxSRM: 503 Service Unavailable

            at com.vmware.srm.client.topology.impl.view.availability.ExtensionServerImpl.complete(ExtensionServerImpl.java:51)
            at com.vmware.srm.client.reactive.impl.PromiseImpl$ErrorCompletion.complete(PromiseImpl.java:178)
            at com.vmware.srm.client.reactive.impl.PromiseImpl$Result.complete(PromiseImpl.java:41)
            at com.vmware.srm.client.reactive.impl.PromiseImpl$Completion.lambda$null$8(PromiseImpl.java:71)
            at com.vmware.srm.client.utilities.ThreadContext.lambda$wrap$12(ThreadContext.java:38)
            at com.vmware.srm.client.utilities.ThreadContext.execute(ThreadContext.java:183)
            at com.vmware.srm.client.utilities.ThreadContext.execute(ThreadContext.java:193)
            at com.vmware.srm.client.utilities.ThreadContext.execute(ThreadContext.java:176)
            at com.vmware.srm.client.utilities.ThreadContext.setupContext(ThreadContext.java:59)
            at com.vmware.srm.client.utilities.ThreadContext.setupContext(ThreadContext.java:87)
            at com.vmware.srm.client.reactive.impl.PromiseImpl$Completion.lambda$setResult$9(PromiseImpl.java:71)
            at com.vmware.srm.client.utilities.AsyncConsumer$Worker.run(AsyncConsumer.java:37)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
            at java.lang.Thread.run(Thread.java:748)

  • Due to services not running, SRM fails to pair or communicate with Remote SRM server.

  • Service for SRM server is in stopped state. Recent vCenter certificate change had been performed.

Environment

VMware Live Site Recovery 9.x
Site Recovery Manager 8.x

Cause

  • If vCenter server certificates are renewed or upgraded, the token that was previously granted to SRM becomes null and needs to be renewed. The SRM appliance will fail to authenticate against the updated vCenter certificate.

  • SRM services stop working when the SRM is unable to authenticate the vCenter server due to 'panic' caused by certificate changes.

Resolution

Run the following steps on SRM appliance:
  1. Log into SRM appliance VAMI using https://<SRM_IP>:5480

  2. From Summary tab of SRM VAMI perform 'Reconfigure'.

  3. Log into vCenter and verify both SRM and VRMS are showing with OK status (as seen below) and click on OPEN Site Recovery.

  4. Ensure SRM pairs listed and connected.


Note : Do not manually start SRM services as this may crash the appliance and sometimes corrupt it.

If the above steps are performed and error still persists, please contact Broadcom Support to investigate the issue.

Powered by Wolken Software