
Upgrading Version 4.1.1
51
1. Log in as zenoss, and stop all daemons.
zenoss stop
Occasionally, the stop command does not terminate all of the Resource Manager daemons. To check, enter the
following command:
pgrep -fl ${ZENHOME}
If the pgrep command returns a result, kill the processes.
pkill -f ${ZENHOME}
2. Perform a dry run of the RPS install.
zenup install --dry-run zenoss_resmgr-version.zup
If the dry run returns errors, the error messages may include commands to perform. Perform the commands, and
then repeat the dry run.
Note
Depending on your system, several dry runs, and different sets of commands, may be required.
If the dry run completes without errors, repeat the command, without the --dry-run argument.
zenup install zenoss_resmgr-version.zup
Note
The zenup command works for a while and then prompts you to confirm the installation. It will not continue
without your response.
3. Review the customizations that you saved earlier. If they are still required and their code works with the new version,
apply the customizations with the ZenUp tool. For example:
zenup patch feature_XYZ.diff -m"add feature XYZ to 4.2.5"
4. Start Resource Manager.
zenoss start
7.10. Migrating the MySqlMonitor ZenPack
This upgrade installs a major revision of the MySqlMonitor ZenPack, which collects data through a customized mod-
eler plugin. Existing devices get the plugin automatically, but the old monitoring template must be removed manually.
For more information, refer to Zenoss Service Dynamics Extended Monitoring.
7.11. Upgrading remote hubs
Perform these steps on each remote hub host to upgrade.
Note
Review the current port requirements in Appendix B, "Port Requirements", to determine whether hub hosts
have new or changed port requirements.
1. Log in to the hub host as root, or as a user with root privileges.
Komentarze do niniejszej Instrukcji