Hi Ara,

This might be a bug we find in 6.6.1, please open an support ticket so we can look deeper.

Regards

-Lee

Try disabling the historical data collection. Some customers have ran into this issue and is filed as a KB.

https://support.quest.com/Search/SolutionDetail.aspx?id=SOL91910&category=Solutions&SKB=1

From the vFoglight Webconsole->Administration-> Agent-> Agent Status-> Click Edit on the Vmware Performance agent

Modify the properties of the agent-> Click Edit on the Data Collection Scheduler

Under the Historical Data Collection-> Change the value from 10 to 0.

Save the settings

Lastly, Activate the agent

Thanks,

Jeffrey Chen

Thanks Jeffrey and Lee.

I'll try changing the agent settings first as suggested - will come back to you with an update.

Thanks,

A

Hi Jeffrey,

I changed the settings and sure enough the vCenter stopped crashing evvery ten minutes, however, the 'poker chips' have now stopped spinning - are the two linked?

Also, what does the 'Historic Data Resume Collection' process do and what will we not be collecting if its turned off?

I do appreciate your help - I thought this would be a lot more stable than it appears to be.

A

Hi Ara,

No, the issues are separate. The spinners are derived from the inventory and performance collections from the Vmware Performance agent.  A good place to check if the collections are running correctly is under the Vmware Environment-> Administration Dashboard. Click on column under Alarms for the VC.

The inventory, and performance collections should be collecting every 5 minutes by default with current time stamp. If they are not, Check under Administration->Agent Status->Highlight the Vmware Performance agent, click on get log.

Typically, by searching through this agent log and searching for ERROR in the file, it should give further indications of any failures.

WIth the Historical Data collection turned off, you will not be importing the previous 30 days worth of data from the VC.

After investigating the logs, and you are still not clear where to proceed, I would suggest opening a support case with us, and one of us will get back to you.

Regards,

Jeffrey Chen