"Error creating bean with name offlineSyncStopper" error when starting the Replicator service in vCloud Availability 3.0
search cancel

"Error creating bean with name offlineSyncStopper" error when starting the Replicator service in vCloud Availability 3.0

book

Article ID: 301234

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:
  • When you navigate to the vCloud Availabillity On-Premises Management Portal, you see the following message:
This site can't be reached.
vcav-op.corp.local refused to connect.
  • In /opt/vmware/h4/replicator/logs/replicator.log on the On-Premises appliance, you see a similar error:
2019-07-23 10:46:12.677 ERROR - [69b1d182-7b21-4f4c-b6c7-abd61a09caa8] [main] o.s.boot.SpringApplication              : Application run failed

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'offlineSyncStopper': Invocation of init method failed; nested exception is com.vmware.vdr.error.exceptions.PermissionDeniedException: Permission denied.
       at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:139)
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:414)
       at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1754)
       ...
Caused by: com.vmware.vdr.error.exceptions.PermissionDeniedException: Permission denied.
       at com.vmware.h4.replicator.util.ReplicatorSecurityHolder.getPeerDetails(ReplicatorSecurityHolder.java:26)
       at com.vmware.h4.replicator.util.ReplicatorSecurityHolder.getManagerId(ReplicatorSecurityHolder.java:44)
       at com.vmware.h4.replicator.repo.SourceReplicationRepo.getSourceReplicationEntity(SourceReplicationRepo.java:113)
      ...

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCloud Availability 3.0.x

Cause

This issue occurs because of an incorrectly set flag indicating an ongoing offline synchronization on the Replicator database. When this flag is set incorrectly, it can impact the ability for the Replicator service to successfully start.

Resolution

This is a known issue affecting vCloud Availability 3.0.
Currently, there is no resolution.

Workaround:
To work around this issue, contact VMware Support and note this Article ID (71216) in the problem description. For more information, see How to Submit a Support Request.