Please follow these upgrade instructions in our Administration Guide:
https://severalnines.com/docs/administration.html#upgrading-clustercontrol
[DEPRECATED - DON'T READ BELOW]
We have built an automatic upgrade script which is available under our Git repository:
https://github.com/severalnines/s9s-admin.git
IMPORTANT CHANGE! Port 9500 must be opened on the Controller. The Apache Server needs to connect to the Controller on localhost:9500/127.0.0.1:9500.
To upgrade to the latest version, clone the Git repo in ClusterControl host:
$ git clone https://github.com/severalnines/s9s-admin.git
If you already have that clone, it is very important you update it:
$ cd s9s-admin
$ git pull
Navigate to the s9s_upgrade_cmon script folder:
$ cd s9s-admin/ccadmin
Start the upgrade process:
./s9s_upgrade_cmon --latest
The script will compare the current ClusterControl version with the latest version available at our download site and perform the upgrade in all hosts if necessary. For safety precaution, it will backup ClusterControl on every host (default backup path will be /$HOME/s9s_backup/s9s_backup_[date & time]) before performing any upgrade.
Other Parameters
To force upgrade, even though the script detects installed ClusterControl version is already up-to-date, specify the --force (-f) option:
./s9s_upgrade_cmon --latest --force
By default, the upgrade will skip CMON and dcps databases backup as in some cases this behavior can eaten up a lot of disk space. You may instruct the script to perform the DB backup during the upgrade by using --backup-db option (-n) and make sure you have sufficient free space beforehand:
./s9s_upgrade_cmon --latest --backup-db
You can restore back your ClusterControl to the original version by with --restore and --backupdir option:
./s9s_upgrade_cmon --restore=all --backupdir=/tmp/s9s_backup_0-0-0-00/
If you are using non-default installation path (default is /usr/local/cmon for Debian/Ubuntu and /usr for Redhat/CentOS), you can use the topdir option (-t) to specify the custom path as example below:
./s9s_upgrade_cmon --latest --topdir=/opt/cmon
It is also possible to define custom backup path to override the default path during upgrade/backup process using backupdir option (-d) as example below:
./s9s_upgrade_cmon --latest --backupdir=/root/backup/s9s_backup
or
./s9s_upgrade_cmon --backup=all --backupdir=/root/backup/s9s_backup
So, your restoration process (if needed) will be using the custom backup path as well:
./s9s_upgrade_cmon --restore=all --backupdir=/root/backup/s9s_backup
Option restore and backup can take 3 arguments:
- all - restore/backup all hosts (ClusterControl controller host and agent hosts)
- controller - restore/backup controller host only
- agent - restore/backup all agent host only
**For sudoers, kindly run the command with 'sudo'.
Comments
32 comments
Hey,
I did. Now UI says:
|
ClusterControl UI version:
| 1.2.4
|
|
ClusterControl Server Version:
| 1.2.4a
|
|
CMON API Version:
| 1.2.4
|
How do I update rest?
Hi,
That is fine. The UI and the CMON API (a RESTful API) is still on 1.2.4, but the ClusterControl server needed a patch (fixes for the comments above saying upgrade did not work) and became 1.2.4a .
Best regards
Johan
Please sign in to leave a comment.