This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VMWarePerformance - Storage Cartridge must be loaded before enabling storage collection

Hello, 

I'm facing some difficulties in utilizing the Foglight to monitor my VMWare Environment.. When I try to enable the storage collection while I'm adding the vCenter server, I'm getting an error (Storage Cartridge Must be loaded before enabling storage collection)

 

In the Agent Status, it shows Fatal Error, but its collecting data. All Utilization graphs, spinners are not showing up.. 

 

Any help?

 

Regards, 

  • Redeploy the agent and re-initialized the VMWarePerformance Agent, Restarted the Agent Manager, and all graphs, utilization, performance collection started normally.. a few minutes again crashed.. Please review the below logs and anything meaningful...

    2016-12-15 10:58:08.424 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> VERBOSE [Quartz[0]-44] com.quest.vmware.agent.performance.PerformanceMetricsCollector - Beginning Performance Data Collection, VC API = VMware vCenter Server 5.5.0 build-4180647 (win32-x64)
    2016-12-15 10:58:08.424 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> VERBOSE [Quartz[0]-44] com.quest.vmware.agent.performance.query.PerfMetricCollectionEngine - Performance Metrics will not be collected for Agent-Identified Blacklisted Entities: []
    2016-12-15 10:58:08.424 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-44] com.quest.vmware.agent.performance.query.PerfMetricCollectionEngine - Transformed 70 PerfQuerySpecs into 11 requests, largest batch size 18, 8 threads, min start Thu Dec 15 10:52:59 AST 2016, max end Thu Dec 15 10:58:00 AST 2016, split using SplitByESXPerfQuerySpecArraySplitterStrategy
    2016-12-15 10:58:08.549 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-0] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.126 seconds for 2 QuerySpecs
    2016-12-15 10:58:08.564 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-5] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.134 seconds for 2 QuerySpecs
    2016-12-15 10:58:08.580 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-4] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.15 seconds for 3 QuerySpecs
    2016-12-15 10:58:08.580 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-2] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.158 seconds for 3 QuerySpecs
    2016-12-15 10:58:08.580 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-1] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.158 seconds for 4 QuerySpecs
    2016-12-15 10:58:08.580 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-6] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.161 seconds for 3 QuerySpecs
    2016-12-15 10:58:08.596 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-3] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.168 seconds for 3 QuerySpecs
    2016-12-15 10:58:08.674 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-7] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.246 seconds for 3 QuerySpecs
    2016-12-15 10:58:08.877 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-4] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.303 seconds for 13 QuerySpecs
    2016-12-15 10:58:08.924 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-0] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.382 seconds for 16 QuerySpecs
    2016-12-15 10:58:08.986 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49/vm-svcrequest-retrievePropertiesEx(id=726)] com.quest.vmware.api.util.ServiceRequestFactory - 100 properties received, getting more with token 2
    2016-12-15 10:58:09.064 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [vm-perfcollect-5] com.quest.vmware.agent.performance.query.CollectionRunner - Total elapsed time for QueryPerf method is : 0.502 seconds for 18 QuerySpecs
    2016-12-15 10:58:09.064 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-44] com.quest.vmware.agent.performance.query.PerfMetricCollectionEngine - Total elapsed time for run method is : 0.641 seconds, 16406 metric batches
    2016-12-15 10:58:09.064 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> VERBOSE [Quartz[0]-44] com.quest.vmware.agent.performance.PerformanceMetricsCollector - Performance Data Collection Finished
    2016-12-15 10:58:09.064 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-44] com.quest.vmware.agent.performance.PerformanceMetricsCollector - Total elapsed time for collect method is : 0.641 seconds
    2016-12-15 10:58:09.064 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> VERBOSE [Quartz[0]-44] com.quest.vmware.agent.performance.PerformanceMetricsCollector - Processing performance results
    2016-12-15 10:58:09.127 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49] com.quest.vmware.api.property.collector.DirectPropertyCollector - Total elapsed time for collect method is : 1.964 seconds, 133 properties
    2016-12-15 10:58:09.127 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> VERBOSE [Quartz[0]-49] com.quest.vmware.api.view.ViewRefresher - Refreshing Views
    2016-12-15 10:58:09.142 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49] com.quest.vmware.api.view.ViewRefresher - Total elapsed time for refresh method is : 0.01 seconds, 2 updated objects
    2016-12-15 10:58:09.142 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49] com.quest.vmware.agent.inventory.properties.InventoryPropertyUpdateProcessor - Total elapsed time for processUpdate(objectContent) method is : 0.003 seconds, processed 673 entities, discarded 73 entities
    2016-12-15 10:58:09.142 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49] com.quest.vmware.agent.inventory.properties.InventoryPropertyUpdateProcessor - Total elapsed time for processUpdate(updateSet) method is : 0.0 seconds, processed 24 entities
    2016-12-15 10:58:09.142 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49] com.quest.vmware.agent.inventory.properties.InventoryPropertyUpdateProcessor - Total elapsed time for processUpdate method is : 0.007 seconds
    2016-12-15 10:58:09.236 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-44] com.quest.vmware.agent.performance.PerformanceMetricsCollector - Total elapsed time for parseRawMetrics method is : 0.166 seconds, processed 246090 metrics
    2016-12-15 10:58:09.314 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> FATAL [Quartz[0]-44] com.quest.agent.esx.task.PerformanceTask - An unexpected issue occurred during data collection from the VirtualCenter. Please review your environment to ensure that data collection has resumed in a normal fashion. If there is a persistent problem or this message recurs regularly please contact Quest Support.
    2016-12-15 10:58:09.314 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> ERROR [Quartz[0]-44] com.quest.agent.esx.task.PerformanceTask - Error during execution: ERROR: Infinite or NaN
    java.lang.NumberFormatException: Infinite or NaN
    at java.math.BigDecimal.<init>(BigDecimal.java:808)
    at com.quest.vmware.agent.performance.util.Calc.calculateMetrics(Calc.java:72)
    at com.quest.vmware.agent.performance.util.RollupMetricsProcessor.generateMetricValueObject(RollupMetricsProcessor.java:366)
    at com.quest.vmware.agent.performance.util.RollupMetricsProcessor.reConstructParsedMetric(RollupMetricsProcessor.java:315)
    at com.quest.vmware.agent.performance.util.RollupMetricsProcessor.access$000(RollupMetricsProcessor.java:43)
    at com.quest.vmware.agent.performance.util.RollupMetricsProcessor$1.apply(RollupMetricsProcessor.java:64)
    at com.quest.vmware.agent.performance.util.RollupMetricsProcessor$1.apply(RollupMetricsProcessor.java:62)
    at com.google.common.collect.Iterators$8.transform(Iterators.java:860)
    at com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
    at com.quest.vmware.agent.performance.processing.ParsedMetricProcessor.process(ParsedMetricProcessor.java:52)
    at com.quest.vmware.agent.performance.PerformanceMetricsCollector.process(PerformanceMetricsCollector.java:145)
    at com.quest.vmware.agent.performance.PerformanceMetricsCollector.collectAndProcess(PerformanceMetricsCollector.java:174)
    at com.quest.agent.esx.task.PerformanceTask.retrieveDataAndCreateSubmissionSet(PerformanceTask.java:574)
    at com.quest.agent.esx.task.PerformanceTask.processMetrics(PerformanceTask.java:295)
    at com.quest.agent.esx.task.ESXAgentTask.collectData(ESXAgentTask.java:137)
    at com.quest.agent.esx.task.ESXAgentTask.run(ESXAgentTask.java:193)
    at com.quest.agent.esx.ESXAgent.runTask(ESXAgent.java:502)
    at com.quest.agent.esx.ESXAgent.esxPerformanceCollection(ESXAgent.java:730)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at com.quest.glue.core.services.EquivalenceInvocationHandler.invoke(EquivalenceInvocationHandler.java:75)
    at com.quest.glue.core.agent.AgentInteractionHandler.invoke(AgentInteractionHandler.java:177)
    at com.sun.proxy.$Proxy94.esxPerformanceCollection(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at com.quest.glue.core.agent.scheduler.CollectorCallback.invokeCollector(CollectorCallback.java:238)
    at com.quest.glue.core.agent.scheduler.CollectorCallback.execute(CollectorCallback.java:146)
    at com.quest.glue.common.util.scheduler.quartz.QuartzScheduler$ScheduledTaskSequentialJob.execute(QuartzScheduler.java:738)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)

    2016-12-15 10:58:09.314 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-44] com.quest.agent.esx.task.PerformanceTask - Execution Complete (submitted timestamp Thu Dec 15 10:58:09 AST 2016)
    2016-12-15 10:58:09.314 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-44] com.quest.agent.esx.ESXAgent - Total elapsed time for PerformanceTask.runTask method is : 2.168 seconds
    2016-12-15 10:58:09.517 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49] com.quest.agent.esx.task.HardwareTask - Total elapsed time for processMetrics method is : 2.355 seconds
    2016-12-15 10:58:09.517 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49] com.quest.agent.esx.task.HardwareTask - Total elapsed time for run method is : 2.382 seconds
    2016-12-15 10:58:09.830 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.13/VMwarePerformance/vCenter01.esx.local-agent> INFO [Quartz[0]-49] com.quest.agent.esx.task.HardwareTask - Execution Complete (submitted timestamp Thu Dec 15 10:58:09 AST 2016)
  • 12/15/16 11:08 AM
    An unexpected issue occurred during data collection from the VirtualCenter. Please review your environment to ensure that data collection has resumed in a normal fashion. If there is a persistent problem or this message recurs regularly please contact Quest Support. Host Port: 443, Host URL: sdk, Host Name: vCenter01.esx.local
  • Followed this KB article and did the same permission required and deactivated the agent and re-activated it again...

    (message: VI SDK invoke exception:com.vmware.vim25.SystemError)
    support.software.dell.com/.../135244


    vCenter it shows green under the VMWare Environment, and data collection is green too.. But again, the utilization / spinners and granule performance details are not showing..
  • Hi Helpdesk

    It looks like Performance (metric) collections are being interrupted by an unexpected value (Infinite or NaN). Your VMware cartridge is 5.6.13, released in 2014, so updating it to a newer release in that branch might solve the issue:
    support.quest.com/.../Foglight for VMware

    Otherwise I would upgrade to the latest release (5.7.1). That might require upgrading Foglight/Agent manager as well. Please look at the release notes for upgrade procedure.

    The error about enabling Storage collections (VFOG-11596) used to happen when the Storage cartridge was an older release, so upgrading also the storage cartridges should allow you to enable storage collection as well. This has been fixed since VMware cartridge 5.7.0 http://documents.software.dell.com/foglight-for-vmware/5.7.0/release-notes/resolved-issues-and-enhancements?ParentProduct=856

    To get Support involved, you can open a Service Request here:
    support.quest.com/create-service-request

    Regards

    Gaston

  • Hello Gaston,

    A case already opened since 27th November... Service Request # 3777402

    Download portal providing me a message that I'm not supported and not entitled for this download :)

    Unable to Process Your Request

    We’re sorry but we cannot process your download request at this time.

    Our records do not indicate a valid Support Maintenance contract for Foglight.
    If you would like to evaluate one of our products, please visit our trial download page at Trial Downloads where you can determine which solution best fits your needs. For purchase information, contact your local sales representative at quest.com.

    If you believe you have received this in error, please contact a Support Administrator at supportadmin@software.dell.com . For local hours of operation and contact numbers view Contact Support.

    Thank you,

    Quest | One Identity
    https://support.quest.com
    Regards,
  • Hi Helpdesk.
    I was out of the office. I have found your case and I have asked Support if we can have a WebEx so I can help you upgrading the cartridge and make sure everything works as expected.
    Regards
    Gaston
  • Hi Gaston,
    thank you for your update... will wait your reply then.

    regards,