We are currently on version 4.3.0. Hypervisor is XenServer. None of the settings are set to 7200 seconds (or any variation that would yield 7200 seconds) but i have provided them below as a reference. Is there any other place where 7200 might be hard coded? We are planning on an upgrade to 4.5.2 next month but this migration needs to happen. We have become pretty proficient at the post volume migration cleanup by manually mucking with the database but it is annoying and I would much rather have cloudstack just wait like i told it to.
copy.volume.wait = 10800 (3 hours) job.cancel.threshold.minutes = 60 (1 hour) job.expire.minutes = 1440 (24 hours) ________________________________________ From: Jan-Arve Nygård [jan.arve.nyg...@gmail.com] Sent: Monday, October 12, 2015 6:19 PM To: users@cloudstack.apache.org Subject: [Questionable] Re: Timeout with live migration What version are you running? Check if the copy.volume.wait setting is set to 7200 and increase it. If not you could also check job.cancel.threshold.minutes and job.expire.minutes. -Jan-Arve 2015-10-13 0:46 GMT+02:00 Ryan Farrington <rfarring...@remitdata.com>: > We are experiencing a failure in cloudstack waiting for an async job > performing a live migration of a volume to finish. I've copied the relevant > log entries below.We acknowledge that the migration will take a few hours > based on the volume of the data and we are looking for a way to increase > the timeout of 7200 seconds into something we know we can work with. > > > 2015-10-12 00:19:36,043 DEBUG [o.a.c.s.RemoteHostEndPoint] > (Job-Executor-62:ctx-802065a9 ctx-bb27a168) Failed to send command, due to > Agent:27, com.cloud.exception.OperationTimedoutException: Commands > 835325398 to Host 27 timed out after 7200 > > >
