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.

To solve this problem:1. Delete the agent's /data directory.This forces the agent to obtain new agent - server communication properties.2. Verify the address and listen port for the <strong>vFabric</strong> <strong>Hyperic</strong> Server.Is there a firewall between agent and server? See the instructions in Configure Agent -Server Communication Interactively or Configure Agent - Server Communication inProperties File.3. Verify the <strong>vFabric</strong> <strong>Hyperic</strong> Server is up.4. Start the agent, supplying the correct server connection properties, either inagent.properties or interactively. See the instructions referenced in step 2 above.Server Does Not Have Agent TokenStarting in 4.6.5, if all platforms managed by an agent are removed from <strong>vFabric</strong> <strong>Hyperic</strong>inventory, the <strong>vFabric</strong> <strong>Hyperic</strong> Server also removes the saved authentication token for thatagent from the <strong>vFabric</strong> <strong>Hyperic</strong> database. So after you delete a platform that is managed by anagent that does not manage any other platforms (as in the case of an agent that manages onlythe platform it runs on), the <strong>vFabric</strong> <strong>Hyperic</strong> Server will not accept connections from that agent.If you want the agent to rediscover the platform, you must repeat the initial agent setup process.To force the agent setup dialog:While the agent is running, by running the agent launcher <strong>with</strong> the setup option, orBy deleting the agent's /data and restarting the agent.Agent Start Script TimeoutBy default, the agent start script times out after five minutes if the startup sequence is notsuccessful. Check the agent.log.startup file for messages.If desired, you can configure a longer timeout period – to give the agent more time to connect tothe server — by adding the agent.startupTimeOut property, defined below, to theagent.properties file.agent.startupTimeOutDescriptionThe number of seconds that the agent startup script will wait before determining that theagent did not startup successfully. If the agent is not determined to be listening for requests<strong>with</strong>in this period of time, an error is logged, and the startup script times out.DefaultAs installed, agent.properties does not contain a line that defines the value of this property.The default behavior of the agent is to timeout after 300 seconds.After editing the agent.properties file, save your changes and restart the agent.109

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

Saved successfully!

Ooh no, something went wrong!