[ https://issues.apache.org/jira/browse/CLOUDSTACK-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516296#comment-14516296 ]
ASF subversion and git services commented on CLOUDSTACK-8410: ------------------------------------------------------------- Commit de7173a0ed6434d1809d0471fe8f28bd339f208e in cloudstack's branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=de7173a ] CLOUDSTACK-8410. ESXi host stuck disconnects frequently. During ping task, while scanning and updating status of all VMs on the host that are stuck in a transitional state and are missing from the power report, do so only for VMs that are not removed. > VMware ESXi host disconnects frequently > --------------------------------------- > > Key: CLOUDSTACK-8410 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8410 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware > Reporter: Likitha Shetty > Assignee: Likitha Shetty > Fix For: 4.6.0 > > > Even though CS is able to successfully ping a host, the host is found to be > behind on ping. > Below failure is seen in the logs during every ping- > {noformat} > 2015-04-23 00:02:07,457 WARN [agent.manager.DirectAgentAttache] > (DirectAgent-283:ctx-c17caf7a) Unable to complete the ping task > java.lang.NullPointerException > at > com.cloud.vm.VirtualMachineManagerImpl.handlePowerOffReportWithNoPendingJobsOnVM(VirtualMachineManagerImpl.java:4230) > at > com.cloud.vm.VirtualMachineManagerImpl.scanStalledVMInTransitionStateOnUpHost(VirtualMachineManagerImpl.java:4306) > at > com.cloud.vm.VirtualMachineManagerImpl.processCommands(VirtualMachineManagerImpl.java:3121) > at > com.cloud.agent.manager.AgentManagerImpl.handleCommands(AgentManagerImpl.java:292) > at > com.cloud.agent.manager.DirectAgentAttache$PingTask.runInContext(DirectAgentAttache.java:157) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:50) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:47) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)