Definitely need more logs, but you might want to look at global parameters such as job.cancel.threshold.minutes and other primary storage and timeout values.
If the primary storage or network is slow, you may be exceeding the value and cloudstack cancels the job without completely finishing. Regards, Adrian Sender ---------- Original Message ----------- From: Gian Paolo Buono <gianpaolo.bu...@gesca.it> To: "users@cloudstack.apache.org" <users@cloudstack.apache.org> Sent: Sun, 15 Oct 2017 23:02:42 +0000 Subject: Re: [Issue Migrate Volume] > Hi, > > I have shutdown the vm and tried to migrate the volume, but I > received the message: > > Unable to serialize: Job is cancelled as it has been blocking others > for too long > > but the view of the volume in CS tells me migrating...what do I do ? > > Thanks > > On 10/16/2017 12:55 AM, Rafael Weingärtner wrote: > > To help you we would need more log entries > > On Sun, Oct 15, 2017 at 7:21 PM, Gian Paolo Buono <gianpaolo.bu...@gesca.it><mailto:gianpaolo.bu...@gesca.it> > wrote: > > Hello, > > I migrated a volume from a SR to another, but after the end I received > the message: > > unreachable: Migrate volume failed: com.cloud.utils.exception.CloudRuntimeException: > Failed to migrate volume org.apache.cloudstack.storage.volume > > On XenServer I see the volume is on the migrated storage, but on > cloudstack is still indicated the old SR. > > How can i fix it ? > Thanks ------- End of Original Message -------
