Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Federated collections are slow, fail to complete, or contain continuous gaps in aggregated samples

Federated collections are slow, fail to complete, or contain continuous gaps in aggregated samples

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 721 Votes: 0 Revisions: 8

You may be out of disk space on the federated collector because of a known issue that causes the hyper9 log fileto grow and consume all available disk space.

To check whether you are out of disk space because of large log files:

  1. Log on to the federated collector as the hyper9 user either through the console or using an SSH client.
    User name: hyper9
    Password: ******
    <-- contact Michael Nels or Scott Carter. Keep this password confidential if at all possible by using GoToMeeting or similar remote control software to enter the password yourself.
  2. Verify you are out of disk space — at the shell prompt, type:
    df -h
  3. Verify the log files are the cause — at the shell prompt, type:
    ls -lh /var/log/hyper9

To recover disk space and resume normal collection activities:

  1. Delete the log files — at the shell prompt, type:
    sudo find /var/log/hyper9 -mtime +7 -exec rm -vf {} \;
  2. Verify the recovered disk space — at the shell prompt, type:
    df -h
  3. Open a web browser to the collector on port 80 and do the following:
    1. Edit log4j.properties and turn off DEBUG settings
    2. Restart the application.

To verify that normal collection activities have resumed:

  1. Open a web browser to Hyper9 and use the Run Now command to start a performance job on the federated collector.
  2. Open a web browser to the collector and view the progress on the View Recent Activity page.
  3. Review the data in the Hyper 9 Performance Graph tool to confirm the presence of the new data.
Last modified

Tags

Classifications

Public