Access Keys:
Skip to content (Access Key - 0)


The selected root page could not be found.

2 Installing the patch version

Print this page

Install the patch version of Rhino on the servers

The second stage in installing a patch release, after [backing up and preparing], is to install the patch version of the software onto the servers and create the appropriate on-filesystem configuration for the new cluster. The configuration for the new cluster is based on the configuration settings of the original cluster, with some notable changes: it will use a different directory structure, SAVANNA_CLUSTER_ID, and MANAGEMENT_DATABASE_NAME.

Accept defaults when installing a patch version — except for destination diretory
If, for example, the original version of Rhino is Rhino 2.1_01, installed in /opt/rhino/rhino-2.1_01/, and you want to install Rhino 2.1_02 (a patch release), you would install the new version in /opt/rhino/rhino-2.1_02/ using the rhino-install.sh command. When following the patch release process, you replace the installation options post-installation. We recommend accepting all defaults in the new installation except the destination directory.
Step Description Command
1 Install the patch version of Rhino. rhino-install.sh
Repeat on every server.
2 Remove the configuration for the new cluster install rm -fr /opt/rhino/rhino-2.1_02/config
Repeat on every server.
3 Copy the original cluster file-based configuration to the new nodes rm -fr /opt/rhino/rhino-2.1_02/config
Repeat on every server.
4 Create the same nodes as the original cluster, for the new cluster /opt/rhino/rhino-2.1_02/create-node.sh
Repeat on every server.
5 Remove the new node's configuration rm -fr /opt/rhino/rhino-2.1_02/node-id/config
Repeat for each node on each server.
6 Copy the configuration for the nodes from the original cluster installation to the new cluster cp -r /opt/rhino/rhino-2.1_01/node-id/config /opt/rhino/rhino-2.1_02/node-id
Repeat for each node on each server.
7 Copy the security keys from the original cluster installation to the new cluster cp /opt/rhino/rhino-2.1_01/*.keystore /opt/rhino/rhino-2.1_02/ ; cp /opt/rhino/rhino-2.1_01/client/*.keystore /opt/rhino/rhino-2.1_02/client
Repeat for each node on each server.
8 Change the Savanna cluster ID and the management database name.

On every server in the cluster, and for each node on the server, edit the /opt/rhino/rhino-2.1_02/node-id/config_variables, changing:

  • the SAVANNA_CLUSTER_ID. (For example if the SAVANNA_CLUSTER_ID is set to the value 100, change it to be 101.)
  • the MANAGEMENT_DATABASE_NAME. (For example if the MANAGEMENT_DATABASE_NAME is set to managementDB, change it to be managementDB02.)
  1. June 26, 2014

    Clive Brennon says:

    Step 3 is incorrect - can this be corrected please

    Step 3 is incorrect - can this be corrected please

Adaptavist Theme Builder Powered by Atlassian Confluence