Updating openSUSE manually

Updating openSUSE manually

Applies to

Alert
Cryptshare Appliance with openSUSE 15.3 or later

Problem

The operating system is not up to date and may have unpatched security vulnerabilities.

Cause

No regular OS updates made via the Cryptshare Server Admin Interface when these were available.

Solution/Workaround

Warning
Backup of the entire system
It is highly recommended to make a full backup/snapshot of the server in order to be able to restore the state before the first update steps were made.

Step 1: Updating the existing operating system to the latest version

- Log in as root on the appliance

- Stop the Cryptshare service with the command
  1. systemctl stop cryptshare (use "rccryptshare stop" up to and including v.7.1)

- Run the following comm
ands, to install current patches
  1. zypper refresh
  2. zypper up -t patch

- Execute the following command as often as necessary until you receive the message “Nothing to do.”
  1. zypper up -t patch

Step 2: Manually OS upgrade to openSUSE-15.6

- Run the following commands, to add new repositories

- Run the following command, to perform the OS upgrade
  1. zypper dup --download-in-advance

- Wait for the process to finish

- Run the commands
  1. sync
  2. reboot

- after rebooting log in again as root

- check the OS version with
  1. cat /etc/os-release
The following output should be shown:

- run the following command, to reset the OS update notifications
  1. rm /opt/cryptshare-3/CS_EXECUTION_SERVICE_INDEX

Step 3: Starting Freshclam Timer

Since openSUSE 15.6, freshclam is controlled through the freshclam.timer service. After the update, you need to start and enable the service once:
  1. systemctl start freshclam.timer
  2. systemctl enable freshclam.timer
Freshclam will then be started at the time interval specified in /etc/freshclam.conf (every two hours by default).




    • Related Articles

    • Updating Cryptshare manually

      Applies to: Cryptshare Server from version 4.2.x Purpose: This is an example of the possibilities for updating Cryptshare manually. Note that manual updates should only be done if a regular update is not possible! Please make sure you have a working ...

    • Temporary Directory No Longer Persistent in openSUSE Leap 16.0

      Inhaltsverzeichnis 1 Applies To 2 Problem 3 Cause 4 Solution/Workaround Applies To OpenSUSE upgrade performing from version Leap 15.6 to Leap 16.0. Problem After upgrading to openSUSE Leap 16.0, any files stored in /tmp are permanently deleted on ...

    • Appliance is not available after upgrading to openSUSE 13.2

      Applies to: Cryptshare Appliance with openSUSE 13.2 Symptom: After updating the Operating System of the Cryptshare Appliance from openSUSE 13.1 to 13.2 the Server cannot be reached via the network any longer. Cause: The appropriate network route is ...

    • SSH Root Access Restriction openSUSE Leap 16.0

      Inhaltsverzeichnis 1 Applies To 2 Problem 3 Cause 4 Solution/Workaround Applies To OpenSUSE upgrade performing from version Leap 15.6 to Leap 16.0. Problem After upgrading to openSUSE Leap 16.0, SSH root login with a password no longer works. ...

    • Minimum Hardware Requirements for openSUSE Leap 16.0

      Inhaltsverzeichnis 1 Applies To 2 Problem 3 Cause 4 Solution/Workaround Applies To OpenSUSE upgrade performing from version Leap 15.6 to Leap 16.0. Problem Systems that do not meet the minimum hardware requirements for openSUSE Leap 16.0 may fail to ...