This topic provides instructions to upgrade from Unravel v4.6.1.x TAR installation to v4.7.4.x
The following upgrade path is supported for upgrading from Unravel v4.6.1.x TAR installation to v4.7.4.x
v4.6.1.x → v4.7.4.x
Caution
Before upgrading Unravel, you must take a backup of the data
directory and external database (if using). Perform the following steps:
Download and extract the Unravel binaries of the Unravel version that you want to upgrade/downgrade to.
For example:
$ curl -v https://preview.unraveldata.com/unravel/RPM/4.7.4/unravel-4.7.4.0.tar.gz -u username:password | tar xvz -C /path/to/installation/directory
Note
The default installation directory is
/usr/local
. It may have been changed during the initial deployment. Make sure that the same installation directory is used when upgrading Unravel.Stop Unravel.
<Unravel installation directory>/unravel/manager stop
Activate the version that you want to upgrade/downgrade to.
<Unravel installation directory>/unravel/manager activate <
Unravel-version
>Apply the changes.
<unravel_installation_directory>/unravel/manager config apply
Start all the services.
<unravel_installation_directory>/unravel/manager start
Check the status of services.
<unravel_installation_directory>/unravel/manager report
The following service statuses are reported:
OK: Service is up and running.
Not Monitored: Service is not running. (Has stopped or has failed to start)
Initializing: Services are starting up.
Does not exist: The process unexpectedly disappeared. Restarts will be attempted 10 times.
Remove the old version of Unravel. Do the following:
Remove the
pre-conversion-can-be-deleted
directory in/usr/local/unravel/versions
Remove the
zk_*_data.pre-conversion-can-be-deleted
directories in/src/unravel
.Run
rpm -e
to delete the old RPM. That will also clean up the scripts in/etc/init.d
.
Note
If you have used the manager refresh files earlier, the following error is shown. This is because the command resets the content of current.yaml
file.
INS00142: Upgrade manager blocked the upgrade, reason: current.yaml state is unexpected. INSTALL-2347: This is a known issue on 4.6.1.x, run 'manager refresh all' and try the upgrade again.
In such a case, you must follow the instructions and run refresh all command before attempting the upgrade again.
Refer to Upgrading sensors.
Important
In a multi-cluster deployment, it is mandatory to upgrade the core node before you upgrade the sensors on the edge node.