红帽全球峰会此内容没有您所选择的语言版本。
7.3. Upgrading the Agent
7.3.1. Preparing the Agent for Automatic Updates
复制链接链接已复制到粘贴板!
Even for automatic upgrades for the agent, certain preparation has to be made to the JBoss ON agent to make sure that the upgrade process goes smoothly and the agent restarts successfully.
7.3.1.1. Configuring Agent Preferences
复制链接链接已复制到粘贴板!
Agent preferences for settings like the Java home directory can be set in environment variables for normal use. However, the environment variables set in the shell are lost when the upgrade process stops and restarts the agent, and that means that the agent may not automatically restart after upgrade. Custom settings for the agent, such as
RHQ_AGENT_HOME or RHQ_AGENT_ADDITIONAL_JAVA_OPTS, should be added to the rhq-agent-env.sh file. This file is preserved during upgrade so all of the settings are carried over.
Warning
Do not edit any of the scripts used to launch the JBoss ON agent. There are five files which should never be modified:
rhq-agent.shrhq-agent-wrapper.shrhq-agent.batrhq-agent-wrapper.bat- the rhq-agent runtime
Any changes to the launcher scripts are overwritten during the automatic update. Changes to the environment files (such as
rhq-agent-env.sh ) are preserved during the update.
The default location for the rhq-agent runtime is
$USERHOME/.java/.userPrefs/rhq-agent/default.
7.3.1.2. Configuring Keystores and Truststores
复制链接链接已复制到粘贴板!
If the original JBoss ON agent was configured to run over SSL using custom keystores and truststores, then make sure that those stores are configured so that the upgraded agent can still access them:
- The keystore files must have the word keystore in their filenames. For example,
my-agent-keystore.dat. - The truststore files must have the word truststore in their filenames. For example,
my-agent-truststore.dat. - Both the keystore and truststore files must be located in the agent's
agentRoot/rhq-agent/datadirectory.
As long as the SSL files are properly set up, then they will be copied over into the new agent configuration, and the new agent will automatically run in SSL.
The upgrade process will write new files to the agent's current installation directory, so the agent's system user must have write permissions to that directory.
If the agent's home directory is
/opt/rhq-agent, then the agent has to be able to write to the /opt/rhq-agent directory. If necessary, reset the permissions on the agent home directory. For example:
chown agent_user /opt/rhq-agent
chown agent_user /opt/rhq-agent7.3.1.4. Starting the Agent as a Background Service
复制链接链接已复制到粘贴板!
Section 4.4, “Running the JBoss ON Agent as a Service” describes how to configure the agent to run as a background service. On Windows, this runs as a service. On Linux and Unix systems, the agent starts at boot time from
init.d.
The auto-upgrade process assumes that the agent is running in the background. If the agent is not running as a background daemon, when the agent auto-updates itself, the old agent process running in the console is shutdown, and the new agent is restarted as a background service if possible. On Windows, if the agent is not installed as a service, the agent is restarted in a console window.
7.3.2. Automatically Updating the Agent
复制链接链接已复制到粘贴板!
By default, both JBoss ON servers and agents are configured to upgrade agents automatically. As soon as the JBoss ON server is upgraded, then the agents will be upgraded.
Note
The agent should be running in the background to upgrade properly, as in Section 4.4, “Running the JBoss ON Agent as a Service”.
The automatic upgrade process is part of the normal agent tasks of checking the server for updates:
- 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.
It is possible to instruct an agent to initiate an update or to check if updates are available using the
update through the agent command line:
agentRoot/rhq-agent/bin/rhq-agent.sh > update
agentRoot/rhq-agent/bin/rhq-agent.sh
> update7.3.3. Manually Upgrading the JBoss ON Agent
复制链接链接已复制到粘贴板!
To ensure compatibility with the JBoss ON server, each agent must be upgraded to the same version of JBoss ON as the server.
Agents have the ability to auto-update themselves. So, under most conditions, it isn't necessary to manually upgrade agents. However, if the auto-update fails for some reason or you disabled agent auto-update, then the agent can be upgraded manually.
Note
All agents must be upgraded at the same time. Having agents of different versions is not supported.
- Shut down the JBoss ON agent.
- Windows only.. If the agent is running as a Windows service, uninstall the Windows service:
cd old-agent-install-dir/bin ./rhq-agent-wrapper.bat remove
cd old-agent-install-dir/bin ./rhq-agent-wrapper.bat removeCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Upgrade the JBoss ON server, as in Section 7.1, “Upgrading the JBoss ON Server”. The JBoss ON server must be upgraded before any agents are upgraded.
- Restart the upgraded JBoss ON servers if they are not yet started.
- Download the agent update binary from the server.
- Copy the agent update binary JAR file into the parent directory where the agent is installed. For example:
cp agent-update-binary.jar /opt/rhq-agent
cp agent-update-binary.jar /opt/rhq-agentCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Extract the new JBoss ON agent from the agent update binary by running the following command:
java -jar agent-update-binary.jar --upgrade
java -jar agent-update-binary.jar --upgradeCopy to Clipboard Copied! Toggle word wrap Toggle overflow This will tell the agent update binary to extract the JBoss ON agent distribution and update the current agent that is found inrhq-agentsubdirectory. At this point, the upgraded JBoss ON agent is located in the originalrhq-agentdirectory. The old agent has been backed up to therhq-agent-olddirectory. Any upgrade errors are written to the agent's log files. - Finally, start the JBoss ON agent.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}