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 resolve this problem, you must restore the encryption key that was originally configured, asdescribed below:1. Stop the <strong>vFabric</strong> <strong>Hyperic</strong> Server.2. Retrieve the server.encryption-key values from the EAM_ENCRYPTION_KEYStable in reverse chronological order, using this SQL statement:select * from EAM_ENCRYPTION_KEYS order by creation_date desc3. Set the value of the server.encryption-key property in server.conf <strong>with</strong> theEAM_ENCRYPTION_KEYS.ENCRYPTION_KEY value previous to the current one.4. Restart the <strong>vFabric</strong> <strong>Hyperic</strong> Server.5. Review server.log for encryption errors.o Lack of encryption errors indicates the problem is solved.o If encryption errors are still occurring, set the server.encryption-keyproperty to the next earlier value, and repeat the process as necessary until theproblem is solved.Agent Startup or Connection ProblemsThis section describes problems that could prevent the <strong>vFabric</strong> <strong>Hyperic</strong> Agent from starting upor connecting to the <strong>vFabric</strong> <strong>Hyperic</strong> Server.Agent Failed to Connect to Server at First StartupEvery time an agent starts up it attempts to contact the <strong>vFabric</strong> <strong>Hyperic</strong> Server. If, the first timeyou start up an agent, it cannot connect to the server, the agent will continue to have problemsconnecting to the server, even after the server is reachable.The first time a <strong>vFabric</strong> <strong>Hyperic</strong> Agent successfully connects <strong>with</strong> the <strong>vFabric</strong> <strong>Hyperic</strong> Server,the agent saves the server connection settings in its /data directory. If the server is notavailable (because the wrong address/port was configured for the agent, or because the serverhasn't been started or is still in the process of starting up) the agent will fail to connect, andhence fail to persist the server connection data. Upon agent restart, the agent will not be able tofind the connection data it requires, and fail to connect to the server. In this case, server.logwill contain a message similar to:2010-04-20 11:04:26,640 ERROR [Thread-1|Thread-1] [AutoinventoryCommandsServer]Unable to send autoinventory platform data to server, sleeping for 33 secs beforeretrying. Error: Unable to communicate <strong>with</strong> server -- provider not yet setup108

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

Saved successfully!

Ooh no, something went wrong!