CS4.4.3 KVM(CentOS6.6) Volume Snapshot失败
CloudStack4.4下 对KVM虚拟机拍磁盘快照好用吗? 全局参数已经修改kvm.snapshot.enabled=true ~~~ 2015-06-10 17:47:34,542 DEBUG [c.c.a.t.Request] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Seq 8-4411275835009401462: Sending { Cmd , MgmtId: 345052689640, via: 8(cloudstack.aclome), Ver: v1, Flags: 100011, [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache. cloudstack.storage.to.SnapshotObjectTO:{path:/mnt/9d641cdd-95a7-3086-9ef 6-b78f8759847e/92d7e6ab-83ec-496e-9324-f30919c9117d/1ccc2115-0fa6-410f-b31a- 6ef7ec41818c,volume:{uuid:92d7e6ab-83ec-496e-9324-f30919c9117d,volum eType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStor eTO:{uuid:9d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolType:Netwo rkFilesystem,host:10.4.41.110,path:/export/186kvmprimary,port:204 9,url:NetworkFilesystem://10.4.41.110/export/186kvmprimary/?ROLE=Primary STOREUUID=9d641cdd-95a7-3086-9ef6-b78f8759847e}},name:ROOT-222,size:5 368709120,path:92d7e6ab-83ec-496e-9324-f30919c9117d,volumeId:227,vmNa me:i-2-222-VM,accountId:2,format:QCOW2,id:227,deviceId:0,hyper visorType:KVM},dataStore:{org.apache.cloudstack.storage.to.PrimaryData StoreTO:{uuid:9d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolType:N etworkFilesystem,host:10.4.41.110,path:/export/186kvmprimary,port :2049,url:NetworkFilesystem://10.4.41.110/export/186kvmprimary/?ROLE=Prim arySTOREUUID=9d641cdd-95a7-3086-9ef6-b78f8759847e}},vmName:i-2-222-VM, name:BC-VM-2a063eb5b7144c2baaf8042a5156a4aa_ROOT-222_20150610094732,hyp ervisorType:KVM,id:7,quiescevm:false,physicalSize:0}},destTO:{or g.apache.cloudstack.storage.to.SnapshotObjectTO:{path:snapshots/2/227, volume:{uuid:92d7e6ab-83ec-496e-9324-f30919c9117d,volumeType:ROOT, dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:9 d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolType:NetworkFilesystem, host:10.4.41.110,path:/export/186kvmprimary,port:2049,url:Networ kFilesystem://10.4.41.110/export/186kvmprimary/?ROLE=PrimarySTOREUUID=9d641 cdd-95a7-3086-9ef6-b78f8759847e}},name:ROOT-222,size:5368709120,path :92d7e6ab-83ec-496e-9324-f30919c9117d,volumeId:227,vmName:i-2-222-VM ,accountId:2,format:QCOW2,id:227,deviceId:0,hypervisorType:KVM },dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.4.41.110/ex port/186kvmsecondary,_role:Image}},vmName:i-2-222-VM,name:BC-VM- 2a063eb5b7144c2baaf8042a5156a4aa_ROOT-222_20150610094732,hypervisorType: KVM,id:7,quiescevm:false,physicalSize:0}},executeInSequence:false, options:{fullSnapshot:true},wait:21600}}] } 2015-06-10 17:47:34,768 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-12:null) SeqA 9-3511: Processing Seq 9-3511: { Cmd , MgmtId: -1, via: 9, Ver: v1, Flags: 11, [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:214,_lo adInfo:{\n \connections\: []\n},wait:0}}] } 2015-06-10 17:47:34,773 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-12:null) SeqA 9-3511: Sending Seq 9-3511: { Ans: , MgmtId: 345052689640, via: 9, Ver: v1, Flags: 100010, [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] } 2015-06-10 17:47:34,982 DEBUG [c.c.a.t.Request] (AgentManager-Handler-14:null) Seq 8-4411275835009401462: Processing: { Ans: , MgmtId: 345052689640, via: 8, Ver: v1, Flags: 10, [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,det ails:Failed to backup 1ccc2115-0fa6-410f-b31a-6ef7ec41818c for disk /mnt/9d641cdd-95a7-3086-9ef6-b78f8759847e/92d7e6ab-83ec-496e-9324-f30919c911 7d to /mnt/d336139b-a6b0-308f-b23f-ec814ebd3cb6/snapshots/2/227,wait:0}}] } 2015-06-10 17:47:34,983 DEBUG [c.c.a.t.Request] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Seq 8-4411275835009401462: Received: { Ans: , MgmtId: 345052689640, via: 8, Ver: v1, Flags: 10, { CopyCmdAnswer } } 2015-06-10 17:47:35,010 DEBUG [c.c.s.s.SnapshotManagerImpl] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Failed to create snapshot com.cloud.utils.exception.CloudRuntimeException: Failed to backup 1ccc2115-0fa6-410f-b31a-6ef7ec41818c for disk /mnt/9d641cdd-95a7-3086-9ef6-b78f8759847e/92d7e6ab-83ec-496e-9324-f30919c911 7d to /mnt/d336139b-a6b0-308f-b23f-ec814ebd3cb6/snapshots/2/227 at org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(Sn apshotServiceImpl.java:282) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy. backupSnapshot(XenserverSnapshotStrategy.java:137) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy. takeSnapshot(XenserverSnapshotStrategy.java:304) at com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerI mpl.java:966) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:43) at
Re: [BUG?] ACS 4.5.1 can't create VM from template on CEPH, bigger than 20GB
Actually, my collegue made a patch for the plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/LibvirtStorageAdaptor.java, where we first check if the image is already present on CEPH, and if not, only then it tries to copy it to the CEPH. But this is not permanent solution, since in the first place, ACS should not try to copy image 2 times, but only 1... Anybody possible to test creating VM from bigger template on CEPH ? Thanks, On 10 June 2015 at 10:55, Andrija Panic andrija.pa...@gmail.com wrote: Hi guys, we just experienced a very strange problem: ACS 4.5.1 vanila Ubuntu 14.04.2 - latest Qemu* binaries (2.0.0+dfsg-2ubuntu1.11) CEPH 0.94.1 We are unable to create VM from template that is bigger than 20GB - on CEPH. Works with 10,14,18GB, but not with templates 20GB or bigger... Problem with 20GB or more: mgmt server / agent tries 2 times to move/create CEPH/RAW volume from NFS/QCOW2, although the first execution is successfull. (some timeout problem?) So, first time it detects it needs to copy from Qcow2/NFS to RAW/CEPH, it issues qemu-img convert and gets success on execution. Than again it tries to do EXACT same thing, so of course CEPH gives error because destinatin image already exists and VM provisioning fails. We dont see this behaviour with 10GB,14GB,18GB, but only with 20GB and bigger. Please find logs from a host, I marked critical points with !!!: [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/2/204/475f79e4-82ef-36f8-b1f2-acfcf541ca95.qcow2,origUrl: http://xxx.yyy.180.244/userdata/d3494552-eb13-478e-84d6-da16f06a01a6.qcow2 ,uuid:9a61c577-e74f-4c22-b7f8-5e642ea69cc2,id:204,format:QCOW2,accountId:2,checksum:b62eb99b8dd4ecfe40b61c91c8c037c0,hvm:true,displayText:andrija-debian7,imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs:// 10.23.2.1/data/tank/secondary ,_role:Image}},name:204-2-f7d41a8b-de2e-3a71-a8cf-301bc76cb2ab,hypervisorType:KVM}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{origUrl: http://xxx.yyy.180.244/userdata/d3494552-eb13-478e-84d6-da16f06a01a6.qcow2 ,uuid:9a61c577-e74f-4c22-b7f8-5e642ea69cc2,id:204,format:QCOW2,accountId:2,checksum:b62eb99b8dd4ecfe40b61c91c8c037c0,hvm:true,displayText:andrija-debian7,imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:8457c284-cf5d-3979-b82e-32ea5efeb97b,id:1,poolType:RBD,host:mon.swiss2.local,path:cold-storage,port:6789,url:RBD://mon.swiss2.local/cold-storage/?ROLE=PrimarySTOREUUID=8457c284-cf5d-3979-b82e-32ea5efeb97b}},name:204-2-f7d41a8b-de2e-3a71-a8cf-301bc76cb2ab,hypervisorType:KVM}},executeInSequence:true,options:{},wait:21600}}] 2015-06-10 01:42:36,661 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:null) Processing command: org.apache.cloudstack.storage.command.CopyCommand 2015-06-10 01:42:36,661 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) Attempting to create storage pool b6d6c679-8475-31f6-b28f-a2e56746c7b9 (NetworkFilesystem) in libvirt 2015-06-10 01:42:36,669 DEBUG [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) pool type='netfs' nameb6d6c679-8475-31f6-b28f-a2e56746c7b9/name uuidb6d6c679-8475-31f6-b28f-a2e56746c7b9/uuid source host name='10.23.2.1'/ dir path='/data/tank/secondary/template/tmpl/2/204'/ /source target path/mnt/b6d6c679-8475-31f6-b28f-a2e56746c7b9/path /target /pool 2015-06-10 01:42:37,764 DEBUG [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) Trying to fetch storage pool b6d6c679-8475-31f6-b28f-a2e56746c7b9 from libvirt 2015-06-10 01:42:37,775 DEBUG [kvm.storage.KVMStorageProcessor] (agentRequest-Handler-4:null) Copying template to primary storage, template format is qcow2 2015-06-10 01:42:37,775 DEBUG [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) Trying to fetch storage pool 8457c284-cf5d-3979-b82e-32ea5efeb97b from libvirt 2015-06-10 01:42:37,781 DEBUG [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) copyPhysicalDisk: disk size:1203378688, virtualsize:25769803776 format:qcow2 2015-06-10 01:42:37,781 DEBUG [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) The source image is not RBD, but the destination is. We will convert into RBD format 2 2015-06-10 01:42:37,782 DEBUG [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-4:null) Starting copy from source image /mnt/b6d6c679-8475-31f6-b28f-a2e56746c7b9/475f79e4-82ef-36f8-b1f2-acfcf541ca95.qcow2 to RBD image cold-storage/9a61c577-e74f-4c22-b7f8-5e642ea69cc2 (!!) 2015-06-10 01:42:37,782 DEBUG [utils.script.Script] (agentRequest-Handler-4:null) Executing: qemu-img convert -O raw /mnt/b6d6c679-8475-31f6-b28f-a2e56746c7b9/475f79e4-82ef-36f8-b1f2-acfcf541ca95.qcow2
AW: Problem Upload Windows volume to ACS 4.5.1
What if you remove the file extension? -Ursprüngliche Nachricht- Von: Andrija Panic [mailto:andrija.pa...@gmail.com] Gesendet: Mittwoch, 10. Juni 2015 10:06 An: users@cloudstack.apache.org Cc: d...@cloudstack.apache.org Betreff: Re: Problem Upload Windows volume to ACS 4.5.1 Marcus, Since file on the old ACS is really RAW (template, created from snapshot, and snapshot created from CEPH volume) - why didn't ACS convert it to qcow2? It has named it x. qcow2 on secondary NFS. ... I get folowing error in the new ACS, when I select RAW as the source format to Upload volume: Please specify a valid URL. URL:/userdata/7a27330d-0080-444d-9807-3fa9bd3997c5.qcow2 is an invalid for the format raw So source image has QCOW2 extension, RAW format, and destination ACS doesnt allow RAW format download if the extension is QCOW2... :( So basically I'm unable to extract CEPH volumes at all and move them to another ACS installation :( On 10 June 2015 at 07:51, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: qemu-img info filename will also give you the information what type the file is. -Ursprüngliche Nachricht- Von: Marcus [mailto:shadow...@gmail.com] Gesendet: Mittwoch, 10. Juni 2015 01:54 An: d...@cloudstack.apache.org Cc: users@cloudstack.apache.org Betreff: Re: Problem Upload Windows volume to ACS 4.5.1 Looks like it is seeing a raw disk, when you specified it was QCOW2. That's what the 'file' command is doing. We used to just trust the name of the file, but this was enhanced to inspect the first 1MB of the download and validate that you are supplying the image format that CS expects. Because the first 1MB shows that this image has a boot sector, I'm assuming it is a raw disk image, instead of a qcow2. Note that CloudStack 4.5 should support raw format for KVM images, but you have to specify it on the API. [root@devcloud-kvm7 tmp]# qemu-img create -f qcow2 img.qcow2 1G Formatting 'img.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off [root@devcloud-kvm7 tmp]# qemu-img create -f raw img.raw 1G Formatting 'img.raw', fmt=raw size=1073741824 [root@devcloud-kvm7 tmp]# file img.qcow2 img.qcow2: QEMU QCOW Image (v3), 1073741824 bytes [root@devcloud-kvm7 tmp]# parted img.raw mklabel New disk label type? msdos [root@devcloud-kvm7 tmp]# file img.raw img.raw: x86 boot sector, code offset 0xb8 On Tue, Jun 9, 2015 at 3:01 AM, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: Hi Andrija, have you tried to convert (qemu-img convert) it to RAW and upload then? Ceph is using RAW devices. The conversion takes place on storage migration but on upload? Regards, Ingo -Ursprüngliche Nachricht- Von: Andrija Panic [mailto:andrija.pa...@gmail.com] Gesendet: Dienstag, 9. Juni 2015 10:24 An: d...@cloudstack.apache.org; users@cloudstack.apache.org Betreff: Problem Upload Windows volume to ACS 4.5.1 HI guys, we try to move some volumes from one ACS installation to another (from 4.3.2 to 4.5.1). Since we are using CEPH, and volume extract/download doesn't work at the moment, we do workarround, we snapshots Windows DATA volume, convert to template, and then we extract URL / download. Then we use this URL to Upload Volume to ACS 4.5.1 - but it fails almoust imiddiately with error inside SSVM (nothing usefull in management log) - and the volume is deleted from ACS: I see there is inspecting disk with file commands...any thought why is this failing ? These are source Windows DATA disk btw: 2015-06-09 07:58:47,811 DEBUG [cloud.agent.Agent] (agentRequest-Handler-10:null) Request:Seq 81-4133460032995983410: { Cmd , MgmtId: 90520741174948, via: 81, Ver: v1, Flags: 100011, [{org.apache.cloudstack.storage.command.DownloadCommand:{hvm:fal se ,maxDownloadSizeInBytes:5497558138880,id:468,resourceType:VOL UM E,installPath:volumes/2/468,_store:{com.cloud.agent.api.to.N fs TO:{_url:nfs:// 10.13.2.1/data/tank/secondary,_role:Image}},url: http://46.232.180.244/userdata/6f2280e7-86d6-4fc7-abe8-e2bbfdeed442. qc ow2 ,format:QCOW2,accountId:2,name:andrija2,wait:0}}] } 2015-06-09 07:58:47,814 DEBUG [cloud.agent.Agent] (agentRequest-Handler-10:null) Processing command: org.apache.cloudstack.storage.command.DownloadCommand 2015-06-09 07:58:47,815 INFO [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-10:null) Determined host 10.13.2.1 corresponds to IP 10.13.2.1 2015-06-09 07:58:47,873 INFO [storage.template.HttpTemplateDownloader] (agentRequest-Handler-10:null) No credentials configured for host= 46.232.180.244:80 2015-06-09 07:58:47,895 INFO [storage.template.HttpTemplateDownloader] (pool-1-thread-3:null) Starting download from http://46.232.180.244/userdata/6f2280e7-86d6-4fc7-abe8-e2bbfdeed442. qc ow2 to
AW: Problem Upload Windows volume to ACS 4.5.1
Didn't you download the file locally? You can rename it there. Then put it on a webserver for upload. -Ursprüngliche Nachricht- Von: Andrija Panic [mailto:andrija.pa...@gmail.com] Gesendet: Mittwoch, 10. Juni 2015 13:05 An: users@cloudstack.apache.org Cc: d...@cloudstack.apache.org Betreff: Re: Problem Upload Windows volume to ACS 4.5.1 How do I do that :) it's auto generated hash/filename inside SSVM - sumlink to reall file... I can try to edit this link name maybe...and try ? On 10 June 2015 at 12:51, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: What if you remove the file extension? -Ursprüngliche Nachricht- Von: Andrija Panic [mailto:andrija.pa...@gmail.com] Gesendet: Mittwoch, 10. Juni 2015 10:06 An: users@cloudstack.apache.org Cc: d...@cloudstack.apache.org Betreff: Re: Problem Upload Windows volume to ACS 4.5.1 Marcus, Since file on the old ACS is really RAW (template, created from snapshot, and snapshot created from CEPH volume) - why didn't ACS convert it to qcow2? It has named it x. qcow2 on secondary NFS. ... I get folowing error in the new ACS, when I select RAW as the source format to Upload volume: Please specify a valid URL. URL:/userdata/7a27330d-0080-444d-9807-3fa9bd3997c5.qcow2 is an invalid for the format raw So source image has QCOW2 extension, RAW format, and destination ACS doesnt allow RAW format download if the extension is QCOW2... :( So basically I'm unable to extract CEPH volumes at all and move them to another ACS installation :( On 10 June 2015 at 07:51, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: qemu-img info filename will also give you the information what type the file is. -Ursprüngliche Nachricht- Von: Marcus [mailto:shadow...@gmail.com] Gesendet: Mittwoch, 10. Juni 2015 01:54 An: d...@cloudstack.apache.org Cc: users@cloudstack.apache.org Betreff: Re: Problem Upload Windows volume to ACS 4.5.1 Looks like it is seeing a raw disk, when you specified it was QCOW2. That's what the 'file' command is doing. We used to just trust the name of the file, but this was enhanced to inspect the first 1MB of the download and validate that you are supplying the image format that CS expects. Because the first 1MB shows that this image has a boot sector, I'm assuming it is a raw disk image, instead of a qcow2. Note that CloudStack 4.5 should support raw format for KVM images, but you have to specify it on the API. [root@devcloud-kvm7 tmp]# qemu-img create -f qcow2 img.qcow2 1G Formatting 'img.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off [root@devcloud-kvm7 tmp]# qemu-img create -f raw img.raw 1G Formatting 'img.raw', fmt=raw size=1073741824 [root@devcloud-kvm7 tmp]# file img.qcow2 img.qcow2: QEMU QCOW Image (v3), 1073741824 bytes [root@devcloud-kvm7 tmp]# parted img.raw mklabel New disk label type? msdos [root@devcloud-kvm7 tmp]# file img.raw img.raw: x86 boot sector, code offset 0xb8 On Tue, Jun 9, 2015 at 3:01 AM, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: Hi Andrija, have you tried to convert (qemu-img convert) it to RAW and upload then? Ceph is using RAW devices. The conversion takes place on storage migration but on upload? Regards, Ingo -Ursprüngliche Nachricht- Von: Andrija Panic [mailto:andrija.pa...@gmail.com] Gesendet: Dienstag, 9. Juni 2015 10:24 An: d...@cloudstack.apache.org; users@cloudstack.apache.org Betreff: Problem Upload Windows volume to ACS 4.5.1 HI guys, we try to move some volumes from one ACS installation to another (from 4.3.2 to 4.5.1). Since we are using CEPH, and volume extract/download doesn't work at the moment, we do workarround, we snapshots Windows DATA volume, convert to template, and then we extract URL / download. Then we use this URL to Upload Volume to ACS 4.5.1 - but it fails almoust imiddiately with error inside SSVM (nothing usefull in management log) - and the volume is deleted from ACS: I see there is inspecting disk with file commands...any thought why is this failing ? These are source Windows DATA disk btw: 2015-06-09 07:58:47,811 DEBUG [cloud.agent.Agent] (agentRequest-Handler-10:null) Request:Seq 81-4133460032995983410: { Cmd , MgmtId: 90520741174948, via: 81, Ver: v1, Flags: 100011, [{org.apache.cloudstack.storage.command.DownloadCommand:{hvm:f al se ,maxDownloadSizeInBytes:5497558138880,id:468,resourceType:V OL UM E,installPath:volumes/2/468,_store:{com.cloud.agent.api.to .N fs TO:{_url:nfs:// 10.13.2.1/data/tank/secondary,_role:Image}},url: http://46.232.180.244/userdata/6f2280e7-86d6-4fc7-abe8-e2bbfdeed442. qc ow2 ,format:QCOW2,accountId:2,name:andrija2,wait:0}}] } 2015-06-09 07:58:47,814 DEBUG [cloud.agent.Agent]
Re: Problem Upload Windows volume to ACS 4.5.1
How do I do that :) it's auto generated hash/filename inside SSVM - sumlink to reall file... I can try to edit this link name maybe...and try ? On 10 June 2015 at 12:51, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: What if you remove the file extension? -Ursprüngliche Nachricht- Von: Andrija Panic [mailto:andrija.pa...@gmail.com] Gesendet: Mittwoch, 10. Juni 2015 10:06 An: users@cloudstack.apache.org Cc: d...@cloudstack.apache.org Betreff: Re: Problem Upload Windows volume to ACS 4.5.1 Marcus, Since file on the old ACS is really RAW (template, created from snapshot, and snapshot created from CEPH volume) - why didn't ACS convert it to qcow2? It has named it x. qcow2 on secondary NFS. ... I get folowing error in the new ACS, when I select RAW as the source format to Upload volume: Please specify a valid URL. URL:/userdata/7a27330d-0080-444d-9807-3fa9bd3997c5.qcow2 is an invalid for the format raw So source image has QCOW2 extension, RAW format, and destination ACS doesnt allow RAW format download if the extension is QCOW2... :( So basically I'm unable to extract CEPH volumes at all and move them to another ACS installation :( On 10 June 2015 at 07:51, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: qemu-img info filename will also give you the information what type the file is. -Ursprüngliche Nachricht- Von: Marcus [mailto:shadow...@gmail.com] Gesendet: Mittwoch, 10. Juni 2015 01:54 An: d...@cloudstack.apache.org Cc: users@cloudstack.apache.org Betreff: Re: Problem Upload Windows volume to ACS 4.5.1 Looks like it is seeing a raw disk, when you specified it was QCOW2. That's what the 'file' command is doing. We used to just trust the name of the file, but this was enhanced to inspect the first 1MB of the download and validate that you are supplying the image format that CS expects. Because the first 1MB shows that this image has a boot sector, I'm assuming it is a raw disk image, instead of a qcow2. Note that CloudStack 4.5 should support raw format for KVM images, but you have to specify it on the API. [root@devcloud-kvm7 tmp]# qemu-img create -f qcow2 img.qcow2 1G Formatting 'img.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off [root@devcloud-kvm7 tmp]# qemu-img create -f raw img.raw 1G Formatting 'img.raw', fmt=raw size=1073741824 [root@devcloud-kvm7 tmp]# file img.qcow2 img.qcow2: QEMU QCOW Image (v3), 1073741824 bytes [root@devcloud-kvm7 tmp]# parted img.raw mklabel New disk label type? msdos [root@devcloud-kvm7 tmp]# file img.raw img.raw: x86 boot sector, code offset 0xb8 On Tue, Jun 9, 2015 at 3:01 AM, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: Hi Andrija, have you tried to convert (qemu-img convert) it to RAW and upload then? Ceph is using RAW devices. The conversion takes place on storage migration but on upload? Regards, Ingo -Ursprüngliche Nachricht- Von: Andrija Panic [mailto:andrija.pa...@gmail.com] Gesendet: Dienstag, 9. Juni 2015 10:24 An: d...@cloudstack.apache.org; users@cloudstack.apache.org Betreff: Problem Upload Windows volume to ACS 4.5.1 HI guys, we try to move some volumes from one ACS installation to another (from 4.3.2 to 4.5.1). Since we are using CEPH, and volume extract/download doesn't work at the moment, we do workarround, we snapshots Windows DATA volume, convert to template, and then we extract URL / download. Then we use this URL to Upload Volume to ACS 4.5.1 - but it fails almoust imiddiately with error inside SSVM (nothing usefull in management log) - and the volume is deleted from ACS: I see there is inspecting disk with file commands...any thought why is this failing ? These are source Windows DATA disk btw: 2015-06-09 07:58:47,811 DEBUG [cloud.agent.Agent] (agentRequest-Handler-10:null) Request:Seq 81-4133460032995983410: { Cmd , MgmtId: 90520741174948, via: 81, Ver: v1, Flags: 100011, [{org.apache.cloudstack.storage.command.DownloadCommand:{hvm:fal se ,maxDownloadSizeInBytes:5497558138880,id:468,resourceType:VOL UM E,installPath:volumes/2/468,_store:{com.cloud.agent.api.to.N fs TO:{_url:nfs:// 10.13.2.1/data/tank/secondary,_role:Image}},url: http://46.232.180.244/userdata/6f2280e7-86d6-4fc7-abe8-e2bbfdeed442. qc ow2 ,format:QCOW2,accountId:2,name:andrija2,wait:0}}] } 2015-06-09 07:58:47,814 DEBUG [cloud.agent.Agent] (agentRequest-Handler-10:null) Processing command: org.apache.cloudstack.storage.command.DownloadCommand 2015-06-09 07:58:47,815 INFO [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-10:null) Determined host 10.13.2.1 corresponds to IP 10.13.2.1 2015-06-09 07:58:47,873 INFO [storage.template.HttpTemplateDownloader] (agentRequest-Handler-10:null) No
Re: Problem Upload Windows volume to ACS 4.5.1
Marcus, Since file on the old ACS is really RAW (template, created from snapshot, and snapshot created from CEPH volume) - why didn't ACS convert it to qcow2? It has named it x. qcow2 on secondary NFS. ... I get folowing error in the new ACS, when I select RAW as the source format to Upload volume: Please specify a valid URL. URL:/userdata/7a27330d-0080-444d-9807-3fa9bd3997c5.qcow2 is an invalid for the format raw So source image has QCOW2 extension, RAW format, and destination ACS doesnt allow RAW format download if the extension is QCOW2... :( So basically I'm unable to extract CEPH volumes at all and move them to another ACS installation :( On 10 June 2015 at 07:51, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: qemu-img info filename will also give you the information what type the file is. -Ursprüngliche Nachricht- Von: Marcus [mailto:shadow...@gmail.com] Gesendet: Mittwoch, 10. Juni 2015 01:54 An: d...@cloudstack.apache.org Cc: users@cloudstack.apache.org Betreff: Re: Problem Upload Windows volume to ACS 4.5.1 Looks like it is seeing a raw disk, when you specified it was QCOW2. That's what the 'file' command is doing. We used to just trust the name of the file, but this was enhanced to inspect the first 1MB of the download and validate that you are supplying the image format that CS expects. Because the first 1MB shows that this image has a boot sector, I'm assuming it is a raw disk image, instead of a qcow2. Note that CloudStack 4.5 should support raw format for KVM images, but you have to specify it on the API. [root@devcloud-kvm7 tmp]# qemu-img create -f qcow2 img.qcow2 1G Formatting 'img.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off [root@devcloud-kvm7 tmp]# qemu-img create -f raw img.raw 1G Formatting 'img.raw', fmt=raw size=1073741824 [root@devcloud-kvm7 tmp]# file img.qcow2 img.qcow2: QEMU QCOW Image (v3), 1073741824 bytes [root@devcloud-kvm7 tmp]# parted img.raw mklabel New disk label type? msdos [root@devcloud-kvm7 tmp]# file img.raw img.raw: x86 boot sector, code offset 0xb8 On Tue, Jun 9, 2015 at 3:01 AM, Jochim, Ingo ingo.joc...@bautzen-it.de wrote: Hi Andrija, have you tried to convert (qemu-img convert) it to RAW and upload then? Ceph is using RAW devices. The conversion takes place on storage migration but on upload? Regards, Ingo -Ursprüngliche Nachricht- Von: Andrija Panic [mailto:andrija.pa...@gmail.com] Gesendet: Dienstag, 9. Juni 2015 10:24 An: d...@cloudstack.apache.org; users@cloudstack.apache.org Betreff: Problem Upload Windows volume to ACS 4.5.1 HI guys, we try to move some volumes from one ACS installation to another (from 4.3.2 to 4.5.1). Since we are using CEPH, and volume extract/download doesn't work at the moment, we do workarround, we snapshots Windows DATA volume, convert to template, and then we extract URL / download. Then we use this URL to Upload Volume to ACS 4.5.1 - but it fails almoust imiddiately with error inside SSVM (nothing usefull in management log) - and the volume is deleted from ACS: I see there is inspecting disk with file commands...any thought why is this failing ? These are source Windows DATA disk btw: 2015-06-09 07:58:47,811 DEBUG [cloud.agent.Agent] (agentRequest-Handler-10:null) Request:Seq 81-4133460032995983410: { Cmd , MgmtId: 90520741174948, via: 81, Ver: v1, Flags: 100011, [{org.apache.cloudstack.storage.command.DownloadCommand:{hvm:false ,maxDownloadSizeInBytes:5497558138880,id:468,resourceType:VOLUM E,installPath:volumes/2/468,_store:{com.cloud.agent.api.to.Nfs TO:{_url:nfs:// 10.13.2.1/data/tank/secondary,_role:Image}},url: http://46.232.180.244/userdata/6f2280e7-86d6-4fc7-abe8-e2bbfdeed442.qc ow2 ,format:QCOW2,accountId:2,name:andrija2,wait:0}}] } 2015-06-09 07:58:47,814 DEBUG [cloud.agent.Agent] (agentRequest-Handler-10:null) Processing command: org.apache.cloudstack.storage.command.DownloadCommand 2015-06-09 07:58:47,815 INFO [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-10:null) Determined host 10.13.2.1 corresponds to IP 10.13.2.1 2015-06-09 07:58:47,873 INFO [storage.template.HttpTemplateDownloader] (agentRequest-Handler-10:null) No credentials configured for host= 46.232.180.244:80 2015-06-09 07:58:47,895 INFO [storage.template.HttpTemplateDownloader] (pool-1-thread-3:null) Starting download from http://46.232.180.244/userdata/6f2280e7-86d6-4fc7-abe8-e2bbfdeed442.qc ow2 to /mnt/SecStorage/dd40674b-575d-3bd2-87b3-7f1e1db4c02e/volumes/2/468/dnl d855093017660470tmp_ remoteSize=21474836480 , max size=5497558138880 2015-06-09 07:58:47,909 DEBUG [utils.script.Script] (pool-1-thread-3:null) Executing: /bin/bash -c file /mnt/SecStorage/dd40674b-575d-3bd2-87b3-7f1e1db4c02e/volumes/2/468/dnl d855093017660470tmp_ | cut -d: -f2 2015-06-09
Re: CS4.4.3 KVM(CentOS6.6) Volume Snapshot失败
centos 6吧,qemu-img什么版本 2015-06-10 13:11 GMT+02:00 zhangyan zy.zhang...@neusoft.com: CloudStack4.4下 对KVM虚拟机拍磁盘快照好用吗? 全局参数已经修改kvm.snapshot.enabled=true ~~~ 2015-06-10 17:47:34,542 DEBUG [c.c.a.t.Request] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Seq 8-4411275835009401462: Sending { Cmd , MgmtId: 345052689640, via: 8(cloudstack.aclome), Ver: v1, Flags: 100011, [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache. cloudstack.storage.to.SnapshotObjectTO:{path:/mnt/9d641cdd-95a7-3086-9ef 6-b78f8759847e/92d7e6ab-83ec-496e-9324-f30919c9117d/1ccc2115-0fa6-410f-b31a- 6ef7ec41818c,volume:{uuid:92d7e6ab-83ec-496e-9324-f30919c9117d,volum eType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStor eTO:{uuid:9d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolType:Netwo rkFilesystem,host:10.4.41.110,path:/export/186kvmprimary,port:204 9,url:NetworkFilesystem:// 10.4.41.110/export/186kvmprimary/?ROLE=Primary STOREUUID=9d641cdd-95a7-3086-9ef6-b78f8759847e }},name:ROOT-222,size:5 368709120,path:92d7e6ab-83ec-496e-9324-f30919c9117d,volumeId:227,vmNa me:i-2-222-VM,accountId:2,format:QCOW2,id:227,deviceId:0,hyper visorType:KVM},dataStore:{org.apache.cloudstack.storage.to.PrimaryData StoreTO:{uuid:9d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolType:N etworkFilesystem,host:10.4.41.110,path:/export/186kvmprimary,port :2049,url:NetworkFilesystem:// 10.4.41.110/export/186kvmprimary/?ROLE=Prim arySTOREUUID=9d641cdd-95a7-3086-9ef6-b78f8759847e }},vmName:i-2-222-VM, name:BC-VM-2a063eb5b7144c2baaf8042a5156a4aa_ROOT-222_20150610094732,hyp ervisorType:KVM,id:7,quiescevm:false,physicalSize:0}},destTO:{or g.apache.cloudstack.storage.to.SnapshotObjectTO:{path:snapshots/2/227, volume:{uuid:92d7e6ab-83ec-496e-9324-f30919c9117d,volumeType:ROOT, dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:9 d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolType:NetworkFilesystem, host:10.4.41.110,path:/export/186kvmprimary,port:2049,url:Networ kFilesystem:// 10.4.41.110/export/186kvmprimary/?ROLE=PrimarySTOREUUID=9d641 cdd-95a7-3086-9ef6-b78f8759847e }},name:ROOT-222,size:5368709120,path :92d7e6ab-83ec-496e-9324-f30919c9117d,volumeId:227,vmName:i-2-222-VM ,accountId:2,format:QCOW2,id:227,deviceId:0,hypervisorType:KVM },dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs:// 10.4.41.110/ex port/186kvmsecondary ,_role:Image}},vmName:i-2-222-VM,name:BC-VM- 2a063eb5b7144c2baaf8042a5156a4aa_ROOT-222_20150610094732,hypervisorType: KVM,id:7,quiescevm:false,physicalSize:0}},executeInSequence:false, options:{fullSnapshot:true},wait:21600}}] } 2015-06-10 17:47:34,768 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-12:null) SeqA 9-3511: Processing Seq 9-3511: { Cmd , MgmtId: -1, via: 9, Ver: v1, Flags: 11, [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:214,_lo adInfo:{\n \connections\: []\n},wait:0}}] } 2015-06-10 17:47:34,773 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-12:null) SeqA 9-3511: Sending Seq 9-3511: { Ans: , MgmtId: 345052689640, via: 9, Ver: v1, Flags: 100010, [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] } 2015-06-10 17:47:34,982 DEBUG [c.c.a.t.Request] (AgentManager-Handler-14:null) Seq 8-4411275835009401462: Processing: { Ans: , MgmtId: 345052689640, via: 8, Ver: v1, Flags: 10, [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,det ails:Failed to backup 1ccc2115-0fa6-410f-b31a-6ef7ec41818c for disk /mnt/9d641cdd-95a7-3086-9ef6-b78f8759847e/92d7e6ab-83ec-496e-9324-f30919c911 7d to /mnt/d336139b-a6b0-308f-b23f-ec814ebd3cb6/snapshots/2/227,wait:0}}] } 2015-06-10 17:47:34,983 DEBUG [c.c.a.t.Request] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Seq 8-4411275835009401462: Received: { Ans: , MgmtId: 345052689640, via: 8, Ver: v1, Flags: 10, { CopyCmdAnswer } } 2015-06-10 17:47:35,010 DEBUG [c.c.s.s.SnapshotManagerImpl] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Failed to create snapshot com.cloud.utils.exception.CloudRuntimeException: Failed to backup 1ccc2115-0fa6-410f-b31a-6ef7ec41818c for disk /mnt/9d641cdd-95a7-3086-9ef6-b78f8759847e/92d7e6ab-83ec-496e-9324-f30919c911 7d to /mnt/d336139b-a6b0-308f-b23f-ec814ebd3cb6/snapshots/2/227 at org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(Sn apshotServiceImpl.java:282) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy. backupSnapshot(XenserverSnapshotStrategy.java:137) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy. takeSnapshot(XenserverSnapshotStrategy.java:304) at com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerI mpl.java:966) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
管理服务器和mysql分开安装之问题
大家好: 我想将管理服务器和数据库服务器分开安装,但是在运行数据库初始化脚本时总是过不去,grant权限已经OK,管理服务器已经可以mysql -uroot -p 输入密码后登录到数据库服务器了,请问大家是什么地方还需要授权还是什么地方需要配置,谢谢大家不吝赐教,谢谢! 发自张荣的 iPad mini2
Re: Unable to create template
Anybody? On Tue, Jun 9, 2015 at 6:24 PM, Carlos Reategui create...@gmail.com wrote: ACS: 4.4.0 on Ubuntu 12.04.5 Hosts: XenServer 6.2 I am seeing the following error when trying to create a template from a stopped instance (no problems stopping/starting it). How do I figure out what is using the VDI and not allowing the template? 2015-06-10 06:29:12,653 DEBUG [o.a.c.h.x.XenServerResourceNewBase] (DirectAgent-210:ctx-b2317482) Task: ref:OpaqueRef:4d80dd35-8958-75b6-8075-a721a4d9ed38, UUID:e8287b80-2fad-21bb-873f-994692660f fd progress: 0.15 2015-06-10 06:29:12,663 WARN [o.a.c.h.x.XenServerResourceNewBase] (DirectAgent-210:ctx-b2317482) No event for task OpaqueRef:4d80dd35-8958-75b6-8075-a721a4d9ed38 2015-06-10 06:29:12,694 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-460:ctx-cbb40517) Vm cpu utilization 0.2039705882352941 2015-06-10 06:29:12,694 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-460:ctx-cbb40517) Vm cpu utilization 0.1217647058823529 2015-06-10 06:29:12,694 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-460:ctx-cbb40517) Vm cpu utilization 0.5583088235294118 2015-06-10 06:29:12,730 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-210:ctx-b2317482) Host 10.120.60.14 OpaqueRef:c53c50a0-df68-61c4-7588-fa155dbf7fdf: Removing SR 2015-06-10 06:29:12,740 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-210:ctx-b2317482) Host 10.120.60.14 OpaqueRef:c53c50a0-df68-61c4-7588-fa155dbf7fdf: Catch XenAPIException: This operation cannot be performed because this VDI is in use by some other operation 2015-06-10 06:29:12,750 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-210:ctx-b2317482) Host 10.120.60.14 OpaqueRef:c53c50a0-df68-61c4-7588-fa155dbf7fdf: Catch XenAPIException: This operation cannot be performed because this VDI is in use by some other operation 2015-06-10 06:29:12,750 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-210:ctx-b2317482) Host 10.120.60.14 OpaqueRef:c53c50a0-df68-61c4-7588-fa155dbf7fdf: Unable to remove SR 2015-06-10 06:29:12,800 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-460:ctx-cbb40517) Seq 4-611645124392274755: Response Received: 2015-06-10 06:29:12,800 DEBUG [c.c.a.t.Request] (StatsCollector-2:ctx-e5ed46af) Seq 4-611645124392274755: Received: { Ans: , MgmtId: 159090355471823, via: 4, Ver: v1, Flags: 10, { GetVmStatsAnsw er } } 2015-06-10 06:29:12,838 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-140:ctx-9021c3b3) Seq 5-5799510420146382967: Executing request 2015-06-10 06:29:12,898 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-308:ctx-6d6e0d53) Seq 6-7127227885290520578: Executing request 2015-06-10 06:29:13,059 DEBUG [c.c.a.ApiServlet] (catalina-exec-4:ctx-06e7f44b) ===START=== 172.30.36.108 -- GET command=queryAsyncJobResultjobId=3ed63d71-bfd1-45b7-a09a-301990772208response= jsonsessionkey=yOqyUHVLV64YAywOKxDzR8JCSaU%3D_=1433897964855 2015-06-10 06:29:13,079 DEBUG [c.c.a.ApiServlet] (catalina-exec-4:ctx-06e7f44b ctx-e53477e4) ===END=== 172.30.36.108 -- GET command=queryAsyncJobResultjobId=3ed63d71-bfd1-45b7-a09a-30199077220 8response=jsonsessionkey=yOqyUHVLV64YAywOKxDzR8JCSaU%3D_=1433897964855 2015-06-10 06:29:13,415 ERROR [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-210:ctx-b2317482) Creating template from volume 624c9601-9034-40ca-a0c2-1705078e5c00 failed due to java.util.concu rrent.TimeoutException: No event for task OpaqueRef:4d80dd35-8958-75b6-8075-a721a4d9ed38 java.util.concurrent.TimeoutException: No event for task OpaqueRef:4d80dd35-8958-75b6-8075-a721a4d9ed38 at org.apache.cloudstack.hypervisor.xenserver.XenServerResourceNewBase.waitForTask(XenServerResourceNewBase.java:124) at com.cloud.hypervisor.xen.resource.Xenserver625StorageProcessor.createTemplateFromVolume(Xenserver625StorageProcessor.java:556) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:90) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:546) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:61) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:102) at com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:65) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at
Re: Unable to create template
Hi Carlos, You can execute below command to see what is using the VDI. xe vdi-list vdi-uuid=e8287b80-2fad-21bb-873f-994692660f params=vm-uuid xe vm-list uuid=vm-uuid Regards Sudhansu Sahu CPG-Orchestration sudhansu.s...@citrix.com mailto:%20sudhansu.s...@citrix.com http://www.citrix.com Powering mobile workstyles and cloud services On 10/06/15 9:27 pm, Carlos Reategui create...@gmail.com wrote: Anybody? On Tue, Jun 9, 2015 at 6:24 PM, Carlos Reategui create...@gmail.com wrote: ACS: 4.4.0 on Ubuntu 12.04.5 Hosts: XenServer 6.2 I am seeing the following error when trying to create a template from a stopped instance (no problems stopping/starting it). How do I figure out what is using the VDI and not allowing the template? 2015-06-10 06:29:12,653 DEBUG [o.a.c.h.x.XenServerResourceNewBase] (DirectAgent-210:ctx-b2317482) Task: ref:OpaqueRef:4d80dd35-8958-75b6-8075-a721a4d9ed38, UUID:e8287b80-2fad-21bb-873f-994692660f fd progress: 0.15 2015-06-10 06:29:12,663 WARN [o.a.c.h.x.XenServerResourceNewBase] (DirectAgent-210:ctx-b2317482) No event for task OpaqueRef:4d80dd35-8958-75b6-8075-a721a4d9ed38 2015-06-10 06:29:12,694 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-460:ctx-cbb40517) Vm cpu utilization 0.2039705882352941 2015-06-10 06:29:12,694 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-460:ctx-cbb40517) Vm cpu utilization 0.1217647058823529 2015-06-10 06:29:12,694 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-460:ctx-cbb40517) Vm cpu utilization 0.5583088235294118 2015-06-10 06:29:12,730 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-210:ctx-b2317482) Host 10.120.60.14 OpaqueRef:c53c50a0-df68-61c4-7588-fa155dbf7fdf: Removing SR 2015-06-10 06:29:12,740 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-210:ctx-b2317482) Host 10.120.60.14 OpaqueRef:c53c50a0-df68-61c4-7588-fa155dbf7fdf: Catch XenAPIException: This operation cannot be performed because this VDI is in use by some other operation 2015-06-10 06:29:12,750 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-210:ctx-b2317482) Host 10.120.60.14 OpaqueRef:c53c50a0-df68-61c4-7588-fa155dbf7fdf: Catch XenAPIException: This operation cannot be performed because this VDI is in use by some other operation 2015-06-10 06:29:12,750 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-210:ctx-b2317482) Host 10.120.60.14 OpaqueRef:c53c50a0-df68-61c4-7588-fa155dbf7fdf: Unable to remove SR 2015-06-10 06:29:12,800 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-460:ctx-cbb40517) Seq 4-611645124392274755: Response Received: 2015-06-10 06:29:12,800 DEBUG [c.c.a.t.Request] (StatsCollector-2:ctx-e5ed46af) Seq 4-611645124392274755: Received: { Ans: , MgmtId: 159090355471823, via: 4, Ver: v1, Flags: 10, { GetVmStatsAnsw er } } 2015-06-10 06:29:12,838 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-140:ctx-9021c3b3) Seq 5-5799510420146382967: Executing request 2015-06-10 06:29:12,898 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-308:ctx-6d6e0d53) Seq 6-7127227885290520578: Executing request 2015-06-10 06:29:13,059 DEBUG [c.c.a.ApiServlet] (catalina-exec-4:ctx-06e7f44b) ===START=== 172.30.36.108 -- GET command=queryAsyncJobResultjobId=3ed63d71-bfd1-45b7-a09a-301990772208re sponse= jsonsessionkey=yOqyUHVLV64YAywOKxDzR8JCSaU%3D_=1433897964855 2015-06-10 06:29:13,079 DEBUG [c.c.a.ApiServlet] (catalina-exec-4:ctx-06e7f44b ctx-e53477e4) ===END=== 172.30.36.108 -- GET command=queryAsyncJobResultjobId=3ed63d71-bfd1-45b7-a09a-30199077220 8response=jsonsessionkey=yOqyUHVLV64YAywOKxDzR8JCSaU%3D_=1433897964855 2015-06-10 06:29:13,415 ERROR [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-210:ctx-b2317482) Creating template from volume 624c9601-9034-40ca-a0c2-1705078e5c00 failed due to java.util.concu rrent.TimeoutException: No event for task OpaqueRef:4d80dd35-8958-75b6-8075-a721a4d9ed38 java.util.concurrent.TimeoutException: No event for task OpaqueRef:4d80dd35-8958-75b6-8075-a721a4d9ed38 at org.apache.cloudstack.hypervisor.xenserver.XenServerResourceNewBase.waitF orTask(XenServerResourceNewBase.java:124) at com.cloud.hypervisor.xen.resource.Xenserver625StorageProcessor.createTemp lateFromVolume(Xenserver625StorageProcessor.java:556) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(Sto rageSubsystemCommandHandlerBase.java:90) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStora geCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(Citri xResourceBase.java:546) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenS erver56Resource.java:61) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(Xen Server610Resource.java:102) at com.cloud.hypervisor.xen.resource.XenServer620SP1Resource.executeRequest(
Re: Unable to create template
Hi Suhansu, Thanks for the help. The command you provided complained about unknown field 'vdi-uuid'. I tried with just uuid but the id from the log (which you had in your command) does not exist. Instead I fetched all the params by name-label of the root disk we were trying to create a template from. I don't quite understand why there are 3 vdi or how they are related to each other. # xe vdi-list name-label=ROOT-167 params=all uuid ( RO): 3dd52d1f-bb68-498f-aefb-441951dd9306 name-label ( RW): ROOT-167 name-description ( RW): is-a-snapshot ( RO): false snapshot-of ( RO): not in database snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z allowed-operations (SRO): clone; snapshot current-operations (SRO): sr-uuid ( RO): 83869571-ac77-405c-8849-949374b78680 sr-name-label ( RO): b5090b36-27c4-46d2-9023-edc8e737f65b/var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/254 vbd-uuids (SRO): 87d32128-09fc-68c3-fe19-e8eb439fd9af crashdump-uuids (SRO): virtual-size ( RO): 10737418240 physical-utilisation ( RO): 195440640 location ( RO): 3dd52d1f-bb68-498f-aefb-441951dd9306 type ( RO): User sharable ( RO): false read-only ( RO): false storage-lock ( RO): false managed ( RO): true parent ( RO): not in database missing ( RO): false other-config (MRW): content_id: 926d84fc-ca87-343a-edee-01f6765dde94 xenstore-data (MRO): sm-config (MRO): host_OpaqueRef:0efe83aa-1594-b027-21fe-63b868d2755e: RW on-boot ( RW): persist allow-caching ( RW): false metadata-latest ( RO): false metadata-of-pool ( RO): not in database tags (SRW): uuid ( RO): 1bc9f9c3-8a8f-4cea-829e-1ad2f92a0e15 name-label ( RW): ROOT-167 name-description ( RW): is-a-snapshot ( RO): false snapshot-of ( RO): not in database snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z allowed-operations (SRO): clone; snapshot current-operations (SRO): sr-uuid ( RO): 9bf958cb-fc5e-4e54-ab22-b1850d1dd487 sr-name-label ( RO): b5090b36-27c4-46d2-9023-edc8e737f65b/var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/256 vbd-uuids (SRO): 23e501b7-945a-3399-bfb2-88082612a08c crashdump-uuids (SRO): virtual-size ( RO): 10737418240 physical-utilisation ( RO): 24064 location ( RO): 1bc9f9c3-8a8f-4cea-829e-1ad2f92a0e15 type ( RO): User sharable ( RO): false read-only ( RO): false storage-lock ( RO): false managed ( RO): true parent ( RO): not in database missing ( RO): false other-config (MRW): content_id: decfe93c-63a7-a90d-2593-a764fab317f9 xenstore-data (MRO): sm-config (MRO): host_OpaqueRef:0efe83aa-1594-b027-21fe-63b868d2755e: RW on-boot ( RW): persist allow-caching ( RW): false metadata-latest ( RO): false metadata-of-pool ( RO): not in database tags (SRW): uuid ( RO): 624c9601-9034-40ca-a0c2-1705078e5c00 name-label ( RW): ROOT-167 name-description ( RW): is-a-snapshot ( RO): false snapshot-of ( RO): not in database snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z allowed-operations (SRO): forget; generate_config; update; resize; destroy; clone; copy; snapshot current-operations (SRO): sr-uuid ( RO): 6a318cfe-4f49-4a00-ec12-7445ea8a05c9 sr-name-label ( RO): d660baaa-db1e-3d11-872f-10c69d748764 vbd-uuids (SRO): crashdump-uuids (SRO): virtual-size ( RO): 10737418240 physical-utilisation ( RO): 2286182912 location ( RO): 624c9601-9034-40ca-a0c2-1705078e5c00 type ( RO): User sharable ( RO): false read-only ( RO): false storage-lock ( RO): false managed ( RO): true parent ( RO): not in database missing ( RO): false other-config (MRW): content_id: 13d71fcb-5849-3162-6d53-6bf762b87097 xenstore-data (MRO): sm-config (MRO): vhd-parent: 7f3a9636-af79-4cdb-a062-96317610b260 on-boot ( RW): persist allow-caching ( RW): false metadata-latest ( RO): false
Re: Unable to create template
Hi Sudhansu, I tried with the vbd-list command instead and got the following: # xe vbd-list vdi-name-label=ROOT-167 params=vm-uuid vm-uuid ( RO): 1b4becc4-7255-4670-bdee-b86d42c26977 vm-uuid ( RO): 1b4becc4-7255-4670-bdee-b86d42c26977 And then checked that vm but it is the dom0 of one of my hosts: # xe vm-list uuid=1b4becc4-7255-4670-bdee-b86d42c26977 uuid ( RO) : 1b4becc4-7255-4670-bdee-b86d42c26977 name-label ( RW): Control domain on host: noilabxen04 power-state ( RO): running If I go to that host and check what is mounted is see: # mount /dev/sda1 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw) none on /dev/shm type tmpfs (rw) /opt/xensource/packages/iso/XenCenter.iso on /var/xen/xc-install type iso9660 (ro,loop=/dev/loop0) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) 192.xxx.xxx.xxx:/export/primary/ on /var/run/sr-mount/6a318cfe-4f49-4a00-ec12-7445ea8a05c9 type nfs (rw,soft,timeo=133,retrans=2147483647,tcp,actimeo=0,addr=192.xxx.xxx.xxx) 10.yyy.yyy.yyy:/store/secondary on /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1 type nfs (rw,soft,tcp,timeo=133,retrans=1,addr=10.yyy.yyy.yyy) /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/207 on /var/run/sr-mount/884cd015-d1f4-446c-9f5a-fdb37987cc75 type none (rw,bind) /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/216 on /var/run/sr-mount/967eb3e1-9fee-40ef-a76d-5e5aa134a93d type none (rw,bind) /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/snapshots/3/240 on /var/run/sr-mount/c2296c1c-ea22-4754-a1e0-60978e189123 type none (rw,bind) /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/232 on /var/run/sr-mount/9c229ee2-e6a8-4c07-9fee-3bb36337a6ee type none (rw,bind) /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/234 on /var/run/sr-mount/bed2ca3a-2df9-496f-b246-db7d287f5006 type none (rw,bind) /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/235 on /var/run/sr-mount/9c7a3b19-4047-40a1-8a0f-f95c30936398 type none (rw,bind) /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/254 on /var/run/sr-mount/83869571-ac77-405c-8849-949374b78680 type none (rw,bind) /var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/256 on /var/run/sr-mount/9bf958cb-fc5e-4e54-ab22-b1850d1dd487 type none (rw,bind) I think template 254 and 256 where mentioned in the vdi list I send in the previous email. What to do? thanks Carlos On Wed, Jun 10, 2015 at 1:19 PM, Carlos Reategui car...@reategui.com wrote: Hi Suhansu, Thanks for the help. The command you provided complained about unknown field 'vdi-uuid'. I tried with just uuid but the id from the log (which you had in your command) does not exist. Instead I fetched all the params by name-label of the root disk we were trying to create a template from. I don't quite understand why there are 3 vdi or how they are related to each other. # xe vdi-list name-label=ROOT-167 params=all uuid ( RO): 3dd52d1f-bb68-498f-aefb-441951dd9306 name-label ( RW): ROOT-167 name-description ( RW): is-a-snapshot ( RO): false snapshot-of ( RO): not in database snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z allowed-operations (SRO): clone; snapshot current-operations (SRO): sr-uuid ( RO): 83869571-ac77-405c-8849-949374b78680 sr-name-label ( RO): b5090b36-27c4-46d2-9023-edc8e737f65b/var/cloud_mount/0d6bd883-fffb-3586-9dae-98b2e64995f1/template/tmpl/3/254 vbd-uuids (SRO): 87d32128-09fc-68c3-fe19-e8eb439fd9af crashdump-uuids (SRO): virtual-size ( RO): 10737418240 physical-utilisation ( RO): 195440640 location ( RO): 3dd52d1f-bb68-498f-aefb-441951dd9306 type ( RO): User sharable ( RO): false read-only ( RO): false storage-lock ( RO): false managed ( RO): true parent ( RO): not in database missing ( RO): false other-config (MRW): content_id: 926d84fc-ca87-343a-edee-01f6765dde94 xenstore-data (MRO): sm-config (MRO): host_OpaqueRef:0efe83aa-1594-b027-21fe-63b868d2755e: RW on-boot ( RW): persist allow-caching ( RW): false metadata-latest ( RO): false metadata-of-pool ( RO): not in database tags (SRW): uuid ( RO): 1bc9f9c3-8a8f-4cea-829e-1ad2f92a0e15 name-label ( RW): ROOT-167 name-description ( RW): is-a-snapshot ( RO): false snapshot-of ( RO): not in database
Re: 管理服务器和mysql分开安装之问题
���s,您好! “管理服务器已经可以mysql -uroot -p 输入密码后登录到数据库服务器了” ? 你确定?不用写数据库服务器地址也能登录? === 2015-06-10 23:01:41 您在来信中写道:=== 大家好: 我想将管理服务器和数据库服务器分开安装,但是在运行数据库初始化脚本时总是过不去,grant权限已经OK,管理服务器已经可以mysql -uroot -p 输入密码后登录到数据库服务器了,请问大家是什么地方还需要授权还是什么地方需要配置,谢谢大家不吝赐教,谢谢! 发自张荣的 iPad mini2 = = = = = = = = = = = = = = = = = = = = 致 礼! 贝为标 beiweib...@163.com 2015-06-11
答复: CS4.4.3 KVM(CentOS6.6) Volume Snapshot失败
对,是Centos6.6,qemu是 qemu-img-0.12.1.2-2.445.el6.x86_64 这个版本有问题吗? -邮件原件- 发件人: Wei ZHOU [mailto:ustcweiz...@gmail.com] 发送时间: 2015年6月10日 21:52 收件人: users-cn@cloudstack.apache.org 主题: Re: CS4.4.3 KVM(CentOS6.6) Volume Snapshot失败 centos 6吧,qemu-img什么版本 2015-06-10 13:11 GMT+02:00 zhangyan zy.zhang...@neusoft.com: CloudStack4.4下 对KVM虚拟机拍磁盘快照好用吗? 全局参数已经修改kvm.snapshot.enabled=true ~~ ~~ ~~~ 2015-06-10 17:47:34,542 DEBUG [c.c.a.t.Request] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Seq 8-4411275835009401462: Sending { Cmd , MgmtId: 345052689640, via: 8(cloudstack.aclome), Ver: v1, Flags: 100011, [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache. cloudstack.storage.to.SnapshotObjectTO:{path:/mnt/9d641cdd-95a7-30 86-9ef 6-b78f8759847e/92d7e6ab-83ec-496e-9324-f30919c9117d/1ccc2115-0fa6-410f -b31a- 6ef7ec41818c,volume:{uuid:92d7e6ab-83ec-496e-9324-f30919c9117d, volum eType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDa taStor eTO:{uuid:9d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolType: Netwo rkFilesystem,host:10.4.41.110,path:/export/186kvmprimary,por t:204 9,url:NetworkFilesystem:// 10.4.41.110/export/186kvmprimary/?ROLE=Primary STOREUUID=9d641cdd-95a7-3086-9ef6-b78f8759847e }},name:ROOT-222,size:5 368709120,path:92d7e6ab-83ec-496e-9324-f30919c9117d,volumeId:227 ,vmNa me:i-2-222-VM,accountId:2,format:QCOW2,id:227,deviceId:0, hyper visorType:KVM},dataStore:{org.apache.cloudstack.storage.to.Prima ryData StoreTO:{uuid:9d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolTy pe:N etworkFilesystem,host:10.4.41.110,path:/export/186kvmprimary,port :2049,url:NetworkFilesystem:// 10.4.41.110/export/186kvmprimary/?ROLE=Prim arySTOREUUID=9d641cdd-95a7-3086-9ef6-b78f8759847e }},vmName:i-2-222-VM, name:BC-VM-2a063eb5b7144c2baaf8042a5156a4aa_ROOT-222_20150610094732 ,hyp ervisorType:KVM,id:7,quiescevm:false,physicalSize:0}},destTO :{or g.apache.cloudstack.storage.to.SnapshotObjectTO:{path:snapshots/2/227, volume:{uuid:92d7e6ab-83ec-496e-9324-f30919c9117d,volumeType:ROOT, dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uu id:9 d641cdd-95a7-3086-9ef6-b78f8759847e,id:4,poolType:NetworkFilesystem, host:10.4.41.110,path:/export/186kvmprimary,port:2049,url: Networ kFilesystem:// 10.4.41.110/export/186kvmprimary/?ROLE=PrimarySTOREUUID=9d641 cdd-95a7-3086-9ef6-b78f8759847e }},name:ROOT-222,size:5368709120,path :92d7e6ab-83ec-496e-9324-f30919c9117d,volumeId:227,vmName:i-2- 222-VM ,accountId:2,format:QCOW2,id:227,deviceId:0,hypervisorType :KVM },dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs:// 10.4.41.110/ex port/186kvmsecondary ,_role:Image}},vmName:i-2-222-VM,name:BC-VM- 2a063eb5b7144c2baaf8042a5156a4aa_ROOT-222_20150610094732,hypervisorType: KVM,id:7,quiescevm:false,physicalSize:0}},executeInSequence:false, options:{fullSnapshot:true},wait:21600}}] } 2015-06-10 17:47:34,768 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-12:null) SeqA 9-3511: Processing Seq 9-3511: { Cmd , MgmtId: -1, via: 9, Ver: v1, Flags: 11, [{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:21 4,_lo adInfo:{\n \connections\: []\n},wait:0}}] } 2015-06-10 17:47:34,773 DEBUG [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-12:null) SeqA 9-3511: Sending Seq 9-3511: { Ans: , MgmtId: 345052689640, via: 9, Ver: v1, Flags: 100010, [{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] } 2015-06-10 17:47:34,982 DEBUG [c.c.a.t.Request] (AgentManager-Handler-14:null) Seq 8-4411275835009401462: Processing: { Ans: , MgmtId: 345052689640, via: 8, Ver: v1, Flags: 10, [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:fals e,det ails:Failed to backup 1ccc2115-0fa6-410f-b31a-6ef7ec41818c for disk /mnt/9d641cdd-95a7-3086-9ef6-b78f8759847e/92d7e6ab-83ec-496e-9324-f309 19c911 7d to /mnt/d336139b-a6b0-308f-b23f-ec814ebd3cb6/snapshots/2/227,wait:0}}] } 2015-06-10 17:47:34,983 DEBUG [c.c.a.t.Request] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Seq 8-4411275835009401462: Received: { Ans: , MgmtId: 345052689640, via: 8, Ver: v1, Flags: 10, { CopyCmdAnswer } } 2015-06-10 17:47:35,010 DEBUG [c.c.s.s.SnapshotManagerImpl] (Work-Job-Executor-25:ctx-e27ebe1b job-1297/job-1298 ctx-40323cd4) Failed to create snapshot com.cloud.utils.exception.CloudRuntimeException: Failed to backup 1ccc2115-0fa6-410f-b31a-6ef7ec41818c for disk /mnt/9d641cdd-95a7-3086-9ef6-b78f8759847e/92d7e6ab-83ec-496e-9324-f309 19c911 7d to /mnt/d336139b-a6b0-308f-b23f-ec814ebd3cb6/snapshots/2/227 at org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnaps hot(Sn apshotServiceImpl.java:282) at org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy. backupSnapshot(XenserverSnapshotStrategy.java:137)
Re: 我遇到一个在yum重装也没解决的问题
Hi, Mysql 和mgmt在一台机器上么?状态如何?可以清空下cs的日志,重新启动下mgmt服务 --- Thanks, Yitao(依涛 姜) jiangyt.github.io On Wed, Jun 10, 2015 at 3:07 PM, 范 sharefant...@163.com wrote: 大家好! 我安装cloudstack management的机子,/目录下空间过少,有天报出low disk error后,即使已经留出空间,也无法正常启动。重装management后,访问管理页面会出现404。打开catalina.out则出现了以下错误。尽管它说不影响运行但是这是在catalina.out中唯一的错误。打开management-server.log也没有显示错误。 我做过 1.cloud-setup-database 2.cloud-setup-management 3. 在yum中重装cloudstack 4.4.3和tomcat6 都没有效果。 还请各位大牛不吝赐教。感谢! Jun 09, 2015 10:14:56 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.cloudstack.managed.context.ManagedContextTimerTask$1. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1369) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) at org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Exception in thread Timer-2 java.lang.NoClassDefFoundError: org/apache/cloudstack/managed/context/ManagedContextTimerTask$1 at org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) Caused by: java.lang.ClassNotFoundException: org.apache.cloudstack.managed.context.ManagedContextTimerTask$1 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1483) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) ... 3 more 范啟能 --