[
https://issues.apache.org/jira/browse/CLOUDSTACK-5133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827412#comment-13827412
]
huangtao87 commented on CLOUDSTACK-5133:
----------------------------------------
installed inotify on ssvm ,and find the time of template vhd been deleted
check the log found at cloudstack
2013-11-15 06:02:17,348 WARN [storage.template.UploadManagerImpl]
(agentRequest-Handler-1:null) handleDeleteEntityDownloadURLCommand
Path:template/tmpl/3/324/bdda7f65-a049-4853-a247-cdbedc0fc348.vhd Type:VOLUME
the type is volume, is that right ?caused vhd missing?is that a bug of
cloudstack 4.2?
thanks
> few templates lost, cause can not download and launch vm from that
> -------------------------------------------------------------------
>
> Key: CLOUDSTACK-5133
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5133
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Environment: cloudstack 4.2
> xenserver 6.2
> Reporter: huangtao87
> Priority: Critical
> Labels: lost, missing, template
>
> used this version for a while, when i gonna download template, report error.
> then i try to find in ssvm and secondary storage.
> root@s-1-VM:~# cd /var/www/html/userdata/
> root@s-1-VM:/var/www/html/userdata# ls -l
> f6b31479-7fd8-4ffb-b978-2f3490576704.vhd
> lrwxrwxrwx 1 root root 113 Nov 11 07:58
> f6b31479-7fd8-4ffb-b978-2f3490576704.vhd ->
> /mnt/SecStorage/59ee7371-e695-3ae4-afd6-01640d61a49b/template/tmpl/3/305/29c49727-eb59-4781-978e-342e9c00a944.vhd
> root@s-1-VM:/var/www/html/userdata#
> root@s-1-VM:/var/www/html/userdata#
> root@s-1-VM:/var/www/html/userdata# cd
> /mnt/SecStorage/59ee7371-e695-3ae4-afd6-01640d61a49b/template/tmpl/3/305/
> root@s-1-VM:/mnt/SecStorage/59ee7371-e695-3ae4-afd6-01640d61a49b/template/tmpl/3/305#
> ls
> template.properties ******* no templatefile******
> root@s-1-VM:/mnt/SecStorage/59ee7371-e695-3ae4-afd6-01640d61a49b/template/tmpl/3/305#
>
> i check the logs, there is no information why it has been delete. BTW, in
> cloudstack web UI ,that template is already there and status is ready.
> there is a Warn in log below:
> 2013-11-07 11:09:51,863 WARN [xen.resource.CitrixResourceBase]
> (DirectAgent-476:null) Error while collecting disk stats from :
> You gave an invalid object reference. The object may have recently been
> deleted. The class parameter gives the type of reference given, and the
> handle parameter echoes the bad value given.
> at com.xensource.xenapi.Types.checkResponse(Types.java:209)
> at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
> at
> com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909)
> at com.xensource.xenapi.VBDMetrics.getIoReadKbs(VBDMetrics.java:210)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.getVmStats(CitrixResourceBase.java:2749)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2649)
> at
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:493)
> at
> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
> at
> com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:104)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
>
> why does this happen?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
