2. Upgrading the LOCKSS System

This chapter describes how to upgrade an existing LOCKSS 2.0 system from LOCKSS 2.0-alpha5, LOCKSS 2.0-alpha6, LOCKSS 2.0-alpha7, and earlier versions of LOCKSS 2.0-beta1 (LOCKSS 2.0.81-beta1, LOCKSS 2.0.82-beta1, LOCKSS 2.0.83-beta1), to LOCKSS 2.0.84-beta1, the latest version of LOCKSS 2.0-beta1.

Tip

If you are installing the LOCKSS 2.x system for the first time, please see the installation instructions in the next chapter (Installing the LOCKSS System) instead.

Note

Commands in this chapter are run as the lockss user [1].

Tip

Before you begin the upgrade, 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.

2.1. Stop the LOCKSS System

The first step is to stop the running LOCKSS system. Log in as the lockss user and run the following command in the LOCKSS Installer Directory:

scripts/stop-lockss

You may verify all LOCKSS components have stopped by running the following command:

k3s kubectl get deployments -n lockss

which should return:

No resources found in lockss namespace.

2.2. Update the LOCKSS Installer

As the lockss user [1], run this Curl, Wget or HTTPie command [2]:

Curl

curl -sSfL https://lockss.org/downloader | sh -s -

HTTPie

http -qd https://lockss.org/downloader | sh -s -

Wget

wget -qO- https://lockss.org/downloader | sh -s -

This will download and invoke the LOCKSS Downloader, which in turn will install the latest version of the LOCKSS Installer into the Default LOCKSS Installer Directory ($HOME/lockss-installer). If you are using a custom LOCKSS Installer Directory DIR, remember to add --download-dir=DIR to the end of the command; see Running the LOCKSS Downloader for details.

2.3. Run the Upgrade Script

If you are upgrading from a version prior to alpha7, the next step will update PostgreSQL from 9.6.12 to 14.7. In addition, if updating from 2.0-alpha5, the archived content will then be reindexed. Either of these operations, may take some time. As the lockss user, run the following command in the LOCKSS Installer Directory:

scripts/upgrades/upgrade-to-beta1

Hint

If you have collected a substantial amount of content in the alpha system this may take a prohibitively long time. If you do not need that content, you can delete it and save time; see Resetting the System to a Blank State.

2.4. Re-run the Configure Script

Re-run the configuration script by running the command below and follow the instructions in Configuring the LOCKSS System to ensure all existing configuration parameters are still correct and to configure any new parameters:

scripts/configure-lockss

If you do not need to review the existing configuration values, run this command instead:

scripts/configure-lockss --replay

The --replay (or equivalently -r) option will re-use all previously-entered configuration values, and only ask questions for new prompts added since the previous release.

2.5. Start LOCKSS 2.0-beta1

You are now ready to start the LOCKSS system. Run this command as the lockss user [1]:

scripts/start-lockss

---

Footnotes

[1]

See Running Commands as the lockss User.

[2]

Most typical Linux systems have at least one of Curl, Wget or HTTPie installed by default. You can check by typing curl --version, wget --version or http --version, and seeing which ones do not output an error message. See Installing Curl, Installing Wget or Installing HTTPie for installation instructions.