13.07.2015 Views

Getting Started with vFabric Hyperic v.5.7 - VMware

Getting Started with vFabric Hyperic v.5.7 - VMware

Getting Started with vFabric Hyperic v.5.7 - VMware

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

For example:$ telnet 192.168.1.114 2144For a successful connection, the results are similar to:Trying 127.0.0.1...Connected to localhost.Escape character is '^\]'.GETConnection closed by foreign host.To verify that the agent can access the server's listen port, run the following from the agentplatform:$ telnet ServerIP ServerPortFor example:$ telnet 192.168.1.114 7080<strong>vFabric</strong> <strong>Hyperic</strong> Server ProblemsThis section describes problems that could prevent the <strong>vFabric</strong> <strong>Hyperic</strong> Server from starting up.Large Event TableA message like the following in server.log indicates that the EAM_EVENT_LOG is so largethat trigger initialization is taking more than 15 minutes.License IssuesIn <strong>vFabric</strong> <strong>Hyperic</strong>, the number of platforms you can manage is limited by your license. Formore information, see Install or Configure <strong>vFabric</strong> <strong>Hyperic</strong> License.Backlogged <strong>vFabric</strong> <strong>Hyperic</strong> ServerWhen the <strong>vFabric</strong> <strong>Hyperic</strong> Server starts after a period of downtime, it can be inundated <strong>with</strong>metric reports from agents that continued to run while the server was down. When the server isprocessing a large metric backlog from many agents, the maximum size of the agent-serverconnection pool size can become a bottleneck and affect server performance.You can check the "Current Thread Busy" metric for the <strong>vFabric</strong> <strong>Hyperic</strong> Server's internalTomcat server to determine whether connection pool size is an issue.106

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!