Installing the application upgrade package to version 6.0.3

The update is aimed at solving the problem with a delay that may occur when applying anti-virus databases. We strongly recommend installing this update.

These instructions must be carried out on Central Node servers with version 6.0.2 of the component.

Depending on how your application is deployed and used, you need to install the update on the following Central Node servers:

• If you are running the application on a high availability cluster, you must install the update package on all worker servers in the Central Node cluster.
• If you are using the distributed solution and multitenancy mode, you must install the update package on each Central Node server. You do not need to disconnect SCN servers from the PCN.
• In other scenarios, you need to install the update package each Central Node server. You do not need to disable the Sandbox and Sensor servers.

You can install the update package using a script. In this case, the application is updated automatically and you do not need to follow the instructions below. To get the script, please contact Technical Support.

To install the upgrade package on the Central Node server:

1. Create a text file with the following content:

   mkdir -p /opt/kaspersky/ks_check_klava_patch

   cat <<EOF > /opt/kaspersky/ks_check_klava_patch/ks_check_klava_patch.sh

   #!/bin/bash

   KATA_SCANNER_ID=\$(docker ps -f name=kata_scanner -q)

   if [[ -z \${KATA_SCANNER_ID} ]]; then

   echo "kata_scanner not found - exit"

   exit 0

   fi

   CHECK_KLAVA_SRC="/opt/kaspersky/apt-scan-server/libexec/check_klava"

   CHECK_KLAVA_TGT="/opt/kaspersky/apt-updater/libexec/bases_test/check_klava"

   echo "before"

   docker exec \${KATA_SCANNER_ID} bash -c "ls -l \$(dirname \${CHECK_KLAVA_TGT})"

   docker exec \${KATA_SCANNER_ID} bash -c "[ -h \${CHECK_KLAVA_TGT} ] || ln -s -f \${CHECK_KLAVA_SRC} \${CHECK_KLAVA_TGT}"

   echo "after"

   docker exec \${KATA_SCANNER_ID} bash -c "ls -l \$(dirname \${CHECK_KLAVA_TGT})"

   EOF

2. Save it with the .sh extension.
3. Create a text file with the following content:

   cat <<EOF >/etc/cron.d/ks_check_klava_patch

   SHELL=/bin/bash

   PATH=/sbin:/bin:/usr/sbin:/usr/bin

   * * * * * root flock -w 3 /tmp/ks_check_klava_patch.lock /bin/bash /opt/kaspersky/ks_check_klava_patch/ks_check_klava_patch.sh 2>&1 > /tmp/ks_check_klava_patch.log

   EOF

4. Save it with the .sh extension.
5. Place the files created at steps 1–4 of these instructions on the Central Node server.
6. Log in to the management console of the relevant Central Node server over SSH or through a terminal.
7. When the system prompts you, enter the administrator user name and the password that was specified during installation of the component.

   The application component administrator menu is displayed.

8. In the application administrator menu, select Technical Support Mode.
9. Press ENTER.

   This opens the Technical Support Mode confirmation window.

10. Confirm that you want to manage the application in Technical Support Mode. To do so, select Yes and press ENTER.
11. Raise the privileges of the user by running sudo -i.
12. Run the scripts created at steps 1–4 of these instructions in the following order:
    1. The script created at steps 1–2.
    2. The script created at steps 3–4.

    To run a script, use the following commands:

    chmod +x <script name>.sh

    ./<script name>.sh

    You must run these commands for each script.

13. Make sure the application configuration log does not contain error messages. To output the log, run the following command:

    tail -f /tmp/ks_check_klava_patch.log

The upgrade package will be installed.

Page top