3. Upgrading LOCKSS
This chapter describes how to upgrade an existing LOCKSS 2.0 installation to LOCKSS 2.0-beta2 NOT YET RELEASED from any release of LOCKSS 2.0-alpha5, LOCKSS 2.0-alpha6, LOCKSS 2.0-alpha7, or LOCKSS 2.0-beta1. Please note:
If you are installing LOCKSS 2.0-beta2 NOT YET RELEASED from scratch, follow the instructions in Installing LOCKSS instead.
If you are upgrading an existing LOCKSS 1.x installation to LOCKSS 2.0-beta2 NOT YET RELEASED, follow the instructions in LOCKSS 1.x to 2.x Migration Guide instead.
Attention
Almost all network ports used in the LOCKSS stack changed in LOCKSS 2.0-beta2 compared to earlier "alpha" and "beta" versions of LOCKSS 2.0, which impacts firewall rules, browser bookmarks, scripts, and more. For example, the port for the Web user interface of the LOCKSS Configuration Service, often used when first logging in to LOCKSS in a browser, has moved from 24621 to 24602. See LOCKSS 2.0-beta2 Port Changes.
To upgrade to LOCKSS 2.0.90-beta2 NOT YET RELEASED, follow these steps:
Before you begin the upgrade process, we recommend you first bring your operating system up to date by applying security updates and upgrading installed packages. Ask your system administrator or see Operating System Updates in the appendix.
Establish a console session as the
lockssuser.Navigate to the LOCKSS Installer Directory, symbolically:
cd <LOCKSS_INSTALLER_DIR>Stop the LOCKSS stack with this command:
scripts/stop-lockss
Download the latest version of the LOCKSS Installer with the following Curl or Wget command [1]:
curl -sSfL https://lockss.org/downloader | sh -s - --download-dir=`pwd`
wget -qO- https://lockss.org/downloader | sh -s - --download-dir=`pwd`
The next task is to upgrade K3s from 1.21 to 1.31.
Important
This task is performed as
root, in the LOCKSS Installer Directory (cd <LOCKSS_INSTALLER_DIR>).First, run (as
root):scripts/install-lockss --install-k3sTip
This runs the K3s Installer -- the installation script provided by K3s itself. The warning or error messages that may occur while it runs vary. If this step fails, see the suggestions in the equivalent section of the manual for a first-time installation: Section 2.3.8 (Installing K3s).
Then, run (as
root):scripts/install-lockss --test-k3sTip
If this step fails, see the suggestions in the equivalent section of the manual for a first-time installation: Section 2.3.9 (Testing the K3s Node).
Return to your ongoing
lockssconsole session. Double-check that you are operating aslockssby typing:whoami
and verifying that the output is
lockss.Next, you will upgrade LOCKSS from a version 2.0-alpha5 or greater to LOCKSS 2.0.90-beta2 NOT YET RELEASED. Run this command:
scripts/upgrades/upgrade-to-beta2
If upgrade-to-beta2 succeeds, it will direct you to run configure-lockss; run this command:
scripts/configure-lockss --replayTip
If any configuration question requires input, see a reference of all of configure-lockss in Section 4 (Configuring LOCKSS).
Finally, start the LOCKSS stack with this command:
scripts/start-lockss