Skip to main content
Skip table of contents

Update to version 2.7.5

This procedure is applicable only if you have already installed version >= 2.7.2.

 

Before you START THE UPGRADE please check if you get SCORE (CONTEXT and MOTION). In order to do this please do a few SSP LOGIN.

Please be advised that for the Webapp servers, you will need approximately 50GB of free disk space to perform the upgrade.

The “variables.yaml“ must be in /opt/veridiumid/uba location. You need to have the file in this location before run the script.

On all UBA Webapp Servers / VeridiumID Persistence Servers you need to have an username with “sudo” privileges.

Before you start the update, please check if the file /opt/veridiumid/uba/variables.yaml exists on each server (Webapp UBA).

  1. Open a terminal for each node (Webapp UBA and VeridiumId Persistence) :

CODE
# Please replace <nexusUser> / <nexusPassword> with your nexus credentials
# Download "uba-onprem-installer.zip" on each node
wget --user <nexusUser> --password <nexusPassword> https://veridium-repo.veridium-dev.com/repository/UBAInstallerOnPrem/2.7.5/uba-onprem-installer.zip
CODE
unzip uba-onprem-installer.zip

 

  1. On UBA Webapp nodes (one server at time) - run the following command from uba-onprem-installer/update-procedure directory:

CODE
cd uba-onprem-installer/update-procedure
sudo /usr/local/bin/python3.8 update.py --version 2.7.5 --proxy <proxy>

 

  1. On VeridiumId Persistence nodes - run the following command from uba-onprem-installer/update-procedure directory:

CODE
sudo python3 update.py --version 2.7.5 --proxy <proxy>

 

  1. After you run the update on each VeridiumId Persistence node, you should run the ‘decoupleKafkaFromZk.sh’ script (located in uba-onprem-installer/update-procedure directory):

CODE
sudo bash decoupleKafkaFromZk.sh
  1. On UBA Webapp nodes (one server at time) - run the following command:

sudo uba_stop

sudo uba_start

Starting with 2.7.5 the jaeger service will be removed.

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.