You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/07/25 10:43:49 UTC
[jira] [Resolved] (CLOUDSTACK-1868) GetVmStatsCommand throws
NullPointerException with VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinandan Prateek resolved CLOUDSTACK-1868.
--------------------------------------------
Resolution: Cannot Reproduce
Please, reopen if it is still an issues.
> GetVmStatsCommand throws NullPointerException with VMWare
> ---------------------------------------------------------
>
> Key: CLOUDSTACK-1868
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1868
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Francois Gaudreault
> Fix For: 4.2.0
>
> Attachments: management.log, management-server.log.tgz, screenshot-1.jpg
>
>
> We see bunch of these in the log files of CloudStack. Looks like the GetVmStatsCommand crash with a Null pointer exception. We don't think it's permission related since our CS user on vSphere can see all performance and VM statistics using the vSphere client.
> INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is determined to be up and running
> ERROR [vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics.
> ERROR [vmware.resource.VmwareResource] (DirectAgent-67:yul01vi12.ops.dot) Unable to execute GetVmStatsCommand due to : Exception: java.lang.NullPointerException
> Message: null
> java.lang.NullPointerException
> WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain VM statistics.
--
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