Unsolved
This post is more than 5 years old
5 Posts
0
3867
March 29th, 2016 06:00
RecoverPoint for Virtual Machines Deployment Error
Hello,
I'm trying to install RP4VM (4.3.P1) and am seeing an error from the Deployment Manager during the step "configuring rpa cluster repository on the selected datastore." I see the virtual disks created successfully and the vRPAs (I have 2) reconfigured to see an additional virtual disk, but the wizard looks to timeout after this. I checked the DM.log and copied the associated errors below. It looks like "RescanDisksAndWaitForDeviceCommand" isn't finding what it's looking for. Any help on how to troubleshoot or how to manually configure the virtual repository would be appreciated.
2016-03-29 06:05:11,114 [pool-1-thread-25] (BaseInstallationServerAdapter.java:281) DEBUG - Result from Installation Server: Result [completedSuccessfully=true, errorMessage=null, errorType=null, value=SanView [volumesVector=null]]
2016-03-29 06:05:11,114 [pool-1-thread-25] (RescanDisksAndWaitForDeviceCommand.java:42) DEBUG - Didn't find device in SAN view, waiting...
2016-03-29 06:05:11,555 [pool-1-thread-26] (BaseInstallationServerAdapter.java:240) DEBUG - transaction: 136 ended, calling get method for result
2016-03-29 06:05:11,569 [pool-1-thread-26] (BaseInstallationServerAdapter.java:281) DEBUG - Result from Installation Server: Result [completedSuccessfully=true, errorMessage=null, errorType=null, value=SanView [volumesVector=null]]
2016-03-29 06:05:11,569 [pool-1-thread-26] (RescanDisksAndWaitForDeviceCommand.java:42) DEBUG - Didn't find device in SAN view, waiting...
2016-03-29 06:05:21,115 [pool-1-thread-25] (BaseDMCommand.java:150) ERROR - RescanDisksAndWaitForDeviceCommand FAILED
com.emc.recoverpoint.utils.state_observer.StateException: State wasn't reached.
at com.emc.recoverpoint.utils.state_observer.StateObserver.waitUntilStateIsReached(Predicate.scala:22)
at com.emc.dm.commands.concrete.RescanDisksAndWaitForDeviceCommand.inner(RescanDisksAndWaitForDeviceCommand.java:47)
at com.emc.dm.commands.infra.BaseDMCommand.execute(BaseDMCommand.java:39)
at com.emc.dm.commands.infra.BaseDMCommand.call(BaseDMCommand.java:159)
at com.emc.dm.commands.infra.BaseDMCommand.call(BaseDMCommand.java:32)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-03-29 06:05:21,115 [pool-1-thread-25] (ReturnValue.java:51) ERROR -
2016-03-29 06:05:21,115 [pool-1-thread-25] (BaseDMCommand.java:235) DEBUG - Command RescanDisksAndWaitForDeviceCommand FINISHED with returnValue=[ReturnValue [_isSuccess=false, _message=Internal Error, please contact Customer Support, _data=null, _throwable=com.emc.recoverpoint.utils.state_observer.StateException: State wasn't reached., _failureReason=UNKNOWN]]
2016-03-29 06:05:21,115 [pool-1-thread-25] (BaseDMCommand.java:205) DEBUG - Command:RescanDisksAndWaitForDeviceCommand Finished
2016-03-29 06:05:21,570 [pool-1-thread-26] (BaseDMCommand.java:150) ERROR - RescanDisksAndWaitForDeviceCommand FAILED
com.emc.recoverpoint.utils.state_observer.StateException: State wasn't reached.
at com.emc.recoverpoint.utils.state_observer.StateObserver.waitUntilStateIsReached(Predicate.scala:22)
at com.emc.dm.commands.concrete.RescanDisksAndWaitForDeviceCommand.inner(RescanDisksAndWaitForDeviceCommand.java:47)
at com.emc.dm.commands.infra.BaseDMCommand.execute(BaseDMCommand.java:39)
at com.emc.dm.commands.infra.BaseDMCommand.call(BaseDMCommand.java:159)
at com.emc.dm.commands.infra.BaseDMCommand.call(BaseDMCommand.java:32)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-03-29 06:05:21,570 [pool-1-thread-26] (ReturnValue.java:51) ERROR -
2016-03-29 06:05:21,570 [pool-1-thread-26] (BaseDMCommand.java:235) DEBUG - Command RescanDisksAndWaitForDeviceCommand FINISHED with returnValue=[ReturnValue [_isSuccess=false, _message=Internal Error, please contact Customer Support, _data=null, _throwable=com.emc.recoverpoint.utils.state_observer.StateException: State wasn't reached., _failureReason=UNKNOWN]]
2016-03-29 06:05:21,570 [pool-1-thread-26] (BaseDMCommand.java:205) DEBUG - Command:RescanDisksAndWaitForDeviceCommand Finished
2016-03-29 06:05:21,570 [ModalContext] (BaseDMCommand.java:150) ERROR - CreateVirtualRepositoryCommand FAILED
com.emc.dm.exception.InstallationFlowException: Internal Error, please contact Customer Support
at com.emc.dm.commands.infra.Commands.throwFirstRVExceptionIfThereAreAny(Commands.java:53)
at com.emc.dm.commands.infra.Commands.invokeAllAndVerifySuccess(Commands.java:131)
at com.emc.dm.commands.infra.BaseDMCommand.invokeAllAndVerifySuccess(BaseDMCommand.java:99)
at com.emc.dm.commands.concrete.vm.CreateVirtualRepositoryCommand.inner(CreateVirtualRepositoryCommand.java:66)
at com.emc.dm.commands.infra.BaseDMCommand.execute(BaseDMCommand.java:39)
at com.emc.dm.logic.DMLogic.allocateVirtualRepositoryDisk(DMLogic.java:650)
at com.emc.recoverpoint.deploy.rpi.wizard.RPInstallationWizard$4.run(RPInstallationWizard.java:233)
at com.emc.recoverpoint.deploy.utils.TaskRunnerWithProgress$1.run(TaskRunnerWithProgress.java:55)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: com.emc.recoverpoint.utils.state_observer.StateException: State wasn't reached.
at com.emc.recoverpoint.utils.state_observer.StateObserver.waitUntilStateIsReached(Predicate.scala:22)
at com.emc.dm.commands.concrete.RescanDisksAndWaitForDeviceCommand.inner(RescanDisksAndWaitForDeviceCommand.java:47)
at com.emc.dm.commands.infra.BaseDMCommand.execute(BaseDMCommand.java:39)
at com.emc.dm.commands.infra.BaseDMCommand.call(BaseDMCommand.java:159)
at com.emc.dm.commands.infra.BaseDMCommand.call(BaseDMCommand.java:32)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2016-03-29 06:05:21,571 [ModalContext] (ReturnValue.java:51) ERROR -
2016-03-29 06:05:21,571 [ModalContext] (BaseDMCommand.java:235) DEBUG - Command CreateVirtualRepositoryCommand FINISHED with returnValue=[ReturnValue [_isSuccess=false, _message=Internal Error, please contact Customer Support, _data=null, _throwable=com.emc.dm.exception.InstallationFlowException: Internal Error, please contact Customer Support, _failureReason=UNKNOWN]]
2016-03-29 06:05:21,571 [ModalContext] (BaseDMCommand.java:205) DEBUG - Command:CreateVirtualRepositoryCommand Finished
2016-03-29 06:05:21,575 [main] (DMUtils.java:108) ERROR - Internal Error, please contact Customer Support
2016-03-29 06:05:21,576 [main] (AbstractDMWizard.java:123) WARN - Failed to move forward from page: SelectDataStorePage
Idan
675 Posts
0
March 29th, 2016 13:00
Hi there,
There are several of possible reasons for that to happen. I would start with checking if the splitter has enough disk space to run by running vdf -h and df -h.
Generally I would recommend to deploy RP4VM 4.3.1 (released over a month ago) which features a Web-based Deployer with built-in verifications and generally streamlines the deployment flow quite substantially.
Regards,
Idan Kentor
RecoverPoint Corporate Systems Engineering
mcgeek1
5 Posts
0
March 29th, 2016 17:00
Thanks Idan,
I spent some time today also trying 4.3.1. The web based deployer is a really nice feature. Unfortunately it failed at exactly the same spot. There is also plenty of disk space. Any other thoughts would be appreciated.
Thanks,
Mike
mcgeek1
5 Posts
0
March 30th, 2016 07:00
The issue appears to be around exposing the repository volume to the vRPAs. The virtual repository is created fine but it's not being discovered. How is this virtual disk being presented to the vRPAs?
Thanks,
Mike
Idan
675 Posts
0
March 31st, 2016 04:00
This also might be due to a timeout being reached when detecting the repository, if the RPAs are up and it's a VMFS as Rich suggested, the we would need logs to further investigate.
Regards,
Idan
forshr
2 Intern
•
1.1K Posts
0
March 31st, 2016 04:00
Check that all vRPA are online, ensure you have iSCSI Software Adapters configured on the ESXi hosts and can you confirm that the datastore is a VMDK virtual device and the type.
Regards,
Rich Forshaw
Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA)
Data Protection and Availability Solutions
EMC Europe Limited
Mobile: 44 (0) 7730 781169 44%20(0)%207730%20781169>
E-mail: richard.forshaw@emc.com
Twitter: @rw4shaw
mcgeek1
5 Posts
0
March 31st, 2016 05:00
Thanks Rich and Idan,
vRPAs are online and iSCSI is configured. I also manually entered the vRPAs as targets to test iSCSI and Kashya LUNs were discovered. The datastore is not VMFS however, it's NFS. Could that be the issue?
Thanks,
Mike
Idan
675 Posts
0
March 31st, 2016 06:00
We fully support NFS (as we're storage agnostic), as long as VMW would support the storage array, we would as well.
It's possible though that latency is high from that NFS DS, I would recommend a VMFS datastore to place the repository VMDK on, especially for troubleshooting purposes.
Regards,
Idan
mcgeek1
5 Posts
0
March 31st, 2016 08:00
Thanks Idan. I can try iSCSI also, but if I wanted to troubleshoot NFS further, would following this be the best way to collect logs? RecoverPoint: How to collect logs for RecoverPoint.
Thanks for the support!
forshr
2 Intern
•
1.1K Posts
0
March 31st, 2016 12:00
The last time I worked with an NFS volume for the repository the was a timeout issue. This can be increased with assistance from Support or alternatively you can contact Idan or myself offline.
ksun87
32 Posts
0
May 14th, 2016 18:00
how can this timeout value be modified in 4.3.1? I found a KB that mentions dm.properties but DM is no longer involved.
Idan
675 Posts
0
May 14th, 2016 22:00
Hi there,
There is a way to customize timeout values in the Web-based Deployer but it currently requires support involvement since the timeout changes are on the RPA side. Please contact Rich or myself directly to troubleshoot your specific issue.
Regards,
Idan Kentor
RecoverPoint Corporate Systems Engineering
ksun87
32 Posts
0
May 14th, 2016 22:00
Thanks Idan, how can I Contact you?
Idan
675 Posts
0
May 14th, 2016 23:00
NP,
idan.kentor@emc.com
Regards,
Idan