cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-3922) NPE when running the systemVm load scanner. fails systemvm creation
Date Sun, 11 Aug 2013 08:20:49 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prasanna Santhanam closed CLOUDSTACK-3922.
------------------------------------------

    
> NPE when running the systemVm load scanner. fails systemvm creation
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3922
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3922
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Prasanna Santhanam
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: mslog
>
>
> Following NPE is noticed when setting up a zone with the simulator hypervisor.
> The 4.2 branch was stable until yesterday but seems to have regressed on this.
> 2013-07-30 10:39:58,806 WARN  [cloud.vm.SystemVmLoadScanner] (consoleproxy-1:null) Unexpected
exception null
> java.lang.NullPointerException
>         at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isZoneReady(ConsoleProxyManagerImpl.java:941)
>         at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:1614)
>         at com.cloud.consoleproxy.ConsoleProxyManagerImpl.isPoolReadyForScan(ConsoleProxyManagerImpl.java:157)
>         at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:103)
>         at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
>         at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
>         at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>         at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>         at java.lang.Thread.run(Thread.java:680)
> Attaching management server logs
> (HEAD: 238815759664eb2a0e8c000389c976a8b1c5b269)

--
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

Mime
View raw message