2 Replies Latest reply on Nov 22, 2019 5:52 AM by scott28tt

    SRM Plug In disappear after vCenter upgrade

    alextsa Novice

      Hi all

       

      We are using vCenter 6.0 and SRM 6.1.1, and working well for few years, and then we need to upgrade the vCenter 6.0 to U3. Once updated, then the SRM plug-in disappear in the vCenter. Then I go to check the compatibility matrix and found that vCenter 6.0 U3 need to work with 6.1.2, so I go to upgrade the SRM to 6.1.2. But unfortunately I still cannot see the SRM plug-in in the vCenter after upgrade. Then I go to check the vsphere_client_virgo.log and find the below error? Anyone have experience on this?

       

      Log search by Error

       

      [2019-11-22T13:44:58.216+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/rsls' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/rsls' already exists

      [2019-11-22T13:44:58.220+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.rsls' version '6.1.2': a web application with context path '/vsphere-client/srm/rsls' already exists.

      [2019-11-22T13:44:58.223+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.rsls' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

      [2019-11-22T13:45:06.923+08:00] [ERROR] srm-topology-thread-4         c.v.srm.client.topology.impl.vmomi.osgi.VmodlContextInitializer   Failed to load package 'com.vmware.vim.binding.cis.metadata'. org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [com/vmware/vim/binding/cis/metadata/context.xml]; nested exception is java.io.FileNotFoundException: class path resource [com/vmware/vim/binding/cis/metadata/context.xml] cannot be opened because it does not exist

      [2019-11-22T13:45:11.523+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/srm-bootstrap' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/srm-bootstrap' already exists

      [2019-11-22T13:45:11.526+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.srmbootstrap' version '6.1.2': a web application with context path '/vsphere-client/srm/srm-bootstrap' already exists.

      [2019-11-22T13:45:11.529+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.srmbootstrap' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

      [2019-11-22T13:45:15.735+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/inventory-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/inventory-ui' already exists

      [2019-11-22T13:45:15.738+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.inventoryui' version '6.1.2': a web application with context path '/vsphere-client/srm/inventory-ui' already exists.

      [2019-11-22T13:45:15.741+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.inventoryui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

      [2019-11-22T13:45:18.062+08:00] [INFO ] region-dm-12                  o.s.beans.factory.support.DefaultListableBeanFactory              Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1b1ee5b5: defining beans [addEditArrayManagerMutationProviderImpl,rescanSraMutationProviderImpl,arrayPairsMutationProviderImpl,discoverArrayPairsMutationProviderImpl,discoveredArrayPairsProvider,connectionParamProvider,arrayManagerStatusProvider,arrayManagerInformationProvider,arrayPairProvider,arrayManagerSiteProvider,storageDevicesProvider,arrayDiscoveryStatusFaultProvider,collectDatastoresProvider,discoveredArrayPairsIssueAdapterImpl,sraErrorIssueAdapterImpl,pingFailedIssueAdapterImpl,arrayManagersRootsProviderImpl,storageManagersProviderImpl,addEditArrayManagerMutationProvider,rescanSraMutationProvider,arrayPairsMutationProvider,discoverArrayPairsMutationProvider,org.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean#0,org.eclipse.g...

      [2019-11-22T13:45:18.062+08:00] [INFO ] region-dm-12                  o.s.beans.factory.support.DefaultListableBeanFactory              Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1b1ee5b5: defining beans [addEditArrayManagerMutationProviderImpl,rescanSraMutationProviderImpl,arrayPairsMutationProviderImpl,discoverArrayPairsMutationProviderImpl,discoveredArrayPairsProvider,connectionParamProvider,arrayManagerStatusProvider,arrayManagerInformationProvider,arrayPairProvider,arrayManagerSiteProvider,storageDevicesProvider,arrayDiscoveryStatusFaultProvider,collectDatastoresProvider,discoveredArrayPairsIssueAdapterImpl,sraErrorIssueAdapterImpl,pingFailedIssueAdapterImpl,arrayManagersRootsProviderImpl,storageManagersProviderImpl,addEditArrayManagerMutationProvider,rescanSraMutationProvider,arrayPairsMutationProvider,discoverArrayPairsMutationProvider,org.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean#0,org.eclipse.g...

      [2019-11-22T13:45:20.143+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/abr-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/abr-ui' already exists

      [2019-11-22T13:45:20.146+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.abrui' version '6.1.2': a web application with context path '/vsphere-client/srm/abr-ui' already exists.

      [2019-11-22T13:45:20.149+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.abrui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

      [2019-11-22T13:45:24.440+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/group-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/group-ui' already exists

      [2019-11-22T13:45:24.443+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.groupui' version '6.1.2': a web application with context path '/vsphere-client/srm/group-ui' already exists.

      [2019-11-22T13:45:24.446+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.groupui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

      [2019-11-22T13:45:28.706+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/plan-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/plan-ui' already exists

      [2019-11-22T13:45:28.709+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.planui' version '6.1.2': a web application with context path '/vsphere-client/srm/plan-ui' already exists.

      [2019-11-22T13:45:28.712+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.planui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

      [2019-11-22T13:45:37.293+08:00] [ERROR] start-signalling-1            org.eclipse.gemini.web.internal.StandardWebApplication            Failed to start web application at context path '/vsphere-client/srm/vm-ui' org.eclipse.gemini.web.core.spi.ContextPathExistsException: Context path '/vsphere-client/srm/vm-ui' already exists

      [2019-11-22T13:45:37.296+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         WE0004E Failed to start web bundle 'com.vmware.srm.client.vmui' version '6.1.2': a web application with context path '/vsphere-client/srm/vm-ui' already exists.

      [2019-11-22T13:45:37.298+08:00] [ERROR] start-signalling-1            org.eclipse.virgo.medic.eventlog.default                         DE0006E Start failed for bundle 'com.vmware.srm.client.vmui' version '6.1.2'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Web application failed to start

      [2019-11-22T13:45:37.306+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.core.model.CompositeException                     CompositeException

      [2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException

      [2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException

       

      Log search by vcDr

       

      [2019-11-22T13:44:56.415+08:00] [INFO ] vc-extensionmanager-pool-271  com.vmware.vise.vim.extension.VcExtensionManager                  Done expanding plugin package to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353

      [2019-11-22T13:44:56.416+08:00] [WARN ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin id mismatch between the registered extension key (com.vmware.vcDr)

      [2019-11-22T13:44:56.416+08:00] [WARN ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackageManifestParser            Plugin version mismatch for com.vmware.vcDr between the plugin registration info (6.1.2.16353)

      [2019-11-22T13:44:56.421+08:00] [INFO ] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Deploying plugin package 'com.vmware.vcDr:6.1.2.16353'.

      [2019-11-22T13:45:37.307+08:00] [ERROR] vc-extensionmanager-pool-271  com.vmware.vise.extensionfw.impl.PackagesDeployer                 Error deploying one of more bundles for the plugin package /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.vmware.vcDr-6.1.2.16353 com.vmware.vise.core.model.CompositeException: CompositeException

      [2019-11-22T13:45:39.448+08:00] [WARN ] data-service-pool-307        70004163 100050 200040 com.vmware.vise.vim.data.adapters.search.impl.QueryExecutor       object with no server guid: urn:vri:cm:Service:e207e0da-b30c-4fb7-896b-2776ac26a58b_com.vmware.vcDr/MTAuMC4yMzMuMTA1 (class java.net.URI)

       

      Best regards

       

      Alex Tsang

        • 1. Re: SRM Plug In disappear after vCenter upgrade
          KocPawel Hot Shot

          First reboot vCenter web client and check again.

          Then check this from release notes for SRM 6.1.2:

          Site Recovery Manager disappears from the vSphere Web Client.

          In a setup with federated vCenter Single Sign-On, Site Recovery Manager can disappear from the vSphere Web Client for one of the following reasons:

          • You log in to either the protected site or the recovery site and the Platform Services Controller for that site is offline. The plug-in that was loaded last time you logged in is not deployed because a Platform Services Controller, vCenter Server, or Site Recovery Manager Server instance on that site that serves the Site Recovery Manager plug-in might be offline.
            Workaround: Restart the vSphere Web Client service.
          • You installed Site Recovery Manager in a shared recovery site configuration, and you uninstalled one of the Site Recovery Manager instances that is registered with vCenter Server on the shared site. If you deleted all Site Recovery Manager data when you uninstalled the Site Recovery Manager Server instance, Site Recovery Manager disappears from the vSphere Web Client. None of the remaining Site Recovery Manager instances is available.
            Workaround: Restart the vSphere Web Client service.
          • Site Recovery Manager Server on either the protected or the recovery site is offline. In this case, vSphere Web Client should download the Site Recovery Manager client plug-in from the remaining active site, but does not do so.
            Workarounds: Attempt these workarounds in order.
            1. Restart the Site Recovery Manager Server instance that is offline, or repair the connection between Site Recovery Manager Server and Platform Services Controller.
            2. If you cannot bring Site Recovery Manager Server online, uninstall and reinstall this instance of Site Recovery Manager Server.
            3. If you cannot uninstall Site Recovery Manager Server, for example because the virtual machine that it runs in cannot be started, unregister the Site Recovery Manager Server extension from the Managed Object Browser (MOB) of the vCenter Server instance for this site. You must then reinstall Site Recovery Manager.

           

          And you can try:

          Go to page: http://vCenter_Server_name_or_IP/mob

          and check if you have registered SRM plugin, maybe you have plugin registered twice or something (login on administrator@vsphere.local user).

          Here is KB how to do that:

          VMware Knowledge Base

           

          You can unregister SRM plugin and try to register it again.

           

          Before you do anything, make a backup of vCenter, DB, SRM....

          • 2. Re: SRM Plug In disappear after vCenter upgrade
            scott28tt Champion
            Community WarriorsUser ModeratorsVMware Employees

            Moderator: Moved to Site Recovery Manager