8. Reconfiguring LOCKSS 2.x for Normal Operation

The next task, once all the content has been migrated from LOCKSS 1.x to LOCKSS 2.x, is to reconfigure LOCKSS 2.x for normal operation.

Follow these steps:

Stop your LOCKSS 2.x system (currently configured for migration) by running this command as the lockss user in the LOCKSS Installer Directory on your LOCKSS 2.x host [1]:
```
scripts/stop-lockss
```
Stop your LOCKSS 1.x system by running this systemctl command as root on your LOCKSS 1.x host [1]:
```
systemctl stop lockss
```
This step depends on your Migration Scenario:
New-Host Migration
If you are doing a new-host migration, it is strongly recommended that you allow your LOCKSS 2.x host to adopt the host name and IP address previously associated with your LOCKSS 1.x host.

Note

If adopting the IP address is not possible, contact the admin of your LOCKSS network to take into account the fact that your LOCKSS 2.x host now has an IP address not previously known to the other nodes in the network (e.g. firewall rules).

Adopting the host name is not required, but if the host name is not changed, clients -- including users of the Web user interface, monitoring tools and dashboards, link resolvers (e.g. OpenURL resolvers), proxies, and more -- will need to be updated to use this new host name.

To allow your LOCKSS 2.x host to adopt the host name and IP address of your LOCKSS 1.x host, follow these steps:
1. Shut down your LOCKSS 1.x host.
2. Reconfigure your LOCKSS 2.x host so it uses the host name and IP address previously associated with your LOCKSS 1.x host. Contact your system administrator for specifics.
3. If applicable, firewall rules on the LOCKSS 2.x host and elsewhere at your institution need to be updated, because LOCKSS 1.x and LOCKSS 2.x use different ports: firewall rules to TCP ports 8081-8085 are no longer needed and need to be replaced with rules to TCP ports 24600-24699 instead. Note that firewall rules to TCP ports 22, 8080, and 9729 remain the same.
4. Restart K3s on the LOCKSS 2.x node by running these two commands as root:
  1. First: /usr/local/bin/k3s-killall.sh
  2. Then: systemctl restart k3s
5. On the LOCKSS 2.x host, run this command as the lockss user in the LOCKSS Installer Directory:
  scripts/configure-lockss
6. The LOCKSS 2.x configuration process will repeat; for most questions, you will simply hit Enter to re-accept the previously entered value, except for the following prompts:
  1. Do you want to reconfigure LOCKSS 2.x to no longer be in migration mode?: Enter Y for "yes", or simply hit Enter.
  2. Fully qualified hostname (FQDN) of this machine: Enter the host name previously associated with your LOCKSS 1.x host.
  3. IP address of this machine: Enter the IP address previously associated with your LOCKSS 1.x host.
  4. Optional. There may be other configuration values you need to change at this stage, but in most cases, everything else will be the same.
  5. OK to store this configuration?: Enter Y for "yes", or simply hit Enter.
7. If your LOCKSS network uses LCAP SSL keystores for encrypted communication between nodes, see the Appendix: LCAP Over SSL Migration chapter.
Same-Host Migration
If you are doing a same-host migration, follow these steps:
1. On the LOCKSS 2.x host [1], run this command as the lockss user in the LOCKSS Installer Directory:
  scripts/configure-lockss -r
  which is short for:
  scripts/configure-lockss --replay
2. The LOCKSS 2.x configuration process will auto-repeat, but you will receive a few prompts:
  1. Do you want to reconfigure LOCKSS 2.x to no longer be in migration mode?: Enter Y for "yes", or simply hit Enter.
  2. OK to store this configuration?: Enter Y for "yes", or simply hit Enter.
On the LOCKSS 2.x host, run this command as the lockss user in the LOCKSS Installer Directory:
```
scripts/start-lockss -w
```
which is short for:
```
scripts/start-lockss --wait
```
to start the LOCKSS 2.0-beta1 system (now configured for normal operation).

Footnotes