4.6. About Agent Automatic Updates
4.6.1. The Process When an Agent Autoupgrades
- The updated server puts the updated agent packages in a directory accessible to the agent.
- The server notifies the agent that the agent needs to update as soon as the server detects that the agent is running an older version.
- As the agent prepares to update, it begins shutting down its other process. This can take several minutes, as it gracefully shuts down each thread.
- The agent downloads the new binaries from the server.
- The agent spawns a new Java process.
- The Java process backs up the old agent configuration and applies the update.
- The Java process then restarts the agent and kills itself.
updatethrough the agent command line:
agentRoot/rhq-agent/bin/rhq-agent.sh > update
4.6.2. Configuring Agent Preferences
RHQ_AGENT_ADDITIONAL_JAVA_OPTS, should be added to the
rhq-agent-env.shfile. This file is preserved during upgrade so all of the settings are carried over.
rhq-agent-env.sh) are preserved during the update.
4.6.3. Upgrading Custom log4j Settings
rhq-agent-env.shfile are preserved between upgrades. However, any changes to the log settings (
log4j.xml) and other files are lost between upgrades.
4.6.4. Configuring Keystores and Truststores
- The keystore files must have the word keystore in their filenames. For example,
- The truststore files must have the word truststore in their filenames. For example,
- Both the keystore and truststore files should be located in the agent's
agentRoot/rhq-agent/conf/directory. Any trust files in the agent's
conf/directory will be preserved when the agent configuration is cleaned or purged, including during upgrade.
4.6.5. Setting Write Permissions on the Agent Home Directory
/opt/rhq/rhq-agent, then the agent user should have write permissions to the
[root@server ~]# chown agent_user /opt/rhq
4.6.6. Starting the Agent as a Background Service