You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/29 03:06:20 UTC
[jira] [Commented] (CLOUDSTACK-3145) StorageManager-Scavenger NPEs
when cleaning up templates
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695990#comment-13695990 ]
ASF subversion and git services commented on CLOUDSTACK-3145:
-------------------------------------------------------------
Commit 2c31f38c05c16d661812cb89317eb2d4e6c8faf3 in branch refs/heads/master from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2c31f38 ]
CLOUDSTACK-3145:StorageManager-Scavenger NPEs when cleaning up
templates.
> StorageManager-Scavenger NPEs when cleaning up templates
> --------------------------------------------------------
>
> Key: CLOUDSTACK-3145
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3145
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Prasanna Santhanam
> Assignee: Min Chen
> Priority: Critical
>
> This is possibly related to the issue seen in CLOUDSTACK-3144. In this case the storage cleanup thread is set to run every 5 minutes and after the template deletion fails during account gc. The following NPE is notieced from the storagemanager scavenger:
> Jun 23 12:18:52 cloudstack-centos63 local0: 2013-06-23 19:18:52,384 WARN [cloud.storage.StorageManagerImpl] (StorageManager-Scavenger-1:null) problem cleaning up templates in secondary storage store nfs://nfs.fmt.vmops.com:/export/automation/acs/secondary
> Jun 23 12:18:52 java.lang.NullPointerException
> Jun 23 12:18:52 java.lang.NullPointerException
> Jun 23 12:18:52 cloudstack-centos63 at org.apache.cloudstack.storage.image.store.TemplateObject.getInstallPath(TemplateObject.java:325)
> Jun 23 12:18:52 cloudstack-centos63 at org.apache.cloudstack.storage.to.TemplateObjectTO.<init>(TemplateObjectTO.java:59)
> Jun 23 12:18:52 cloudstack-centos63 at org.apache.cloudstack.storage.image.store.TemplateObject.getTO(TemplateObject.java:312)
> Jun 23 12:18:52 cloudstack-centos63 at com.cloud.storage.StorageManagerImpl.cleanupSecondaryStorage(StorageManagerImpl.java:1134)
> Jun 23 12:18:52 cloudstack-centos63 at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> Jun 23 12:18:52 cloudstack-centos63 at com.cloud.storage.StorageManagerImpl.cleanupStorage(StorageManagerImpl.java:1025)
> Jun 23 12:18:52 cloudstack-centos63 at com.cloud.storage.StorageManagerImpl$StorageGarbageCollector.run(StorageManagerImpl.java:1328)
> Jun 23 12:18:52 cloudstack-centos63 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> Jun 23 12:18:52 cloudstack-centos63 at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> Jun 23 12:18:52 cloudstack-centos63 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> Jun 23 12:18:52 cloudstack-centos63 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> Jun 23 12:18:52 cloudstack-centos63 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> Jun 23 12:18:52 cloudstack-centos63 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> Jun 23 12:18:52 cloudstack-centos63 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> Jun 23 12:18:52 cloudstack-centos63 at java.lang.Thread.run(Thread.java:679)
> Jun 23 12:18:52 cloudstack-centos63 local0: 2013-06-23 19:18:52,386 DEBUG [cloud.storage.StorageManagerImpl] (StorageManager-Scavenger-1:null) Secondary storage garbage collector found 0 snapshots to cleanup on secondary storage host: n
> fs://nfs.fmt.vmops.com:/export/automation/acs/secondary
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira