[
https://issues.apache.org/jira/browse/CLOUDSTACK-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626416#comment-13626416
]
Sateesh Chodapuneedi commented on CLOUDSTACK-1868:
--------------------------------------------------
Tried to reproduce this, but not seeing this issue in my 4.1 setup. Commit
6039a704a1a5df7253790ffc218017232c0b5908 (7th April 2013).
Could get VM statistics correctly. Please see the attached screen shot.
Complete mangement server log might help.
> 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
> Reporter: Francois Gaudreault
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.1.0
>
> Attachments: management.log
>
>
> 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
