2. Configuring the LOCKSS System
After Installing the LOCKSS System and Downloading the LOCKSS Installer, configure the system with the configure script:
(If you have experience with classic LOCKSS daemon version 1.x, this is the equivalent of
The questions asked by the script often come with a suggested value, displayed in square brackets; hit Enter to accept the suggested value, or type the correct value and hit Enter. Questions include:
Fully qualified hostname (FQDN) of this machine:Enter the machine’s hostname (e.g.
IP address of this machine:The publicly routable IP address of the machine, or if it is not publicly routable but will be accessible via network address translation (NAT), its IP address on the internal network.
Is this machine behind NAT?:Enter Y if the machine is not publicly routable but will be accessible via network address translation (NAT), or N otherwise.
External IP address for NAT:If you answered Y to the previous question, enter the publicly routable IP address of the machine.
Initial subnet for admin UI access:Enter a semicolon-separated list of subnets in CIDR notation that should have access to the Web user interfaces of the system.
LCAP V3 protocol port:Enter the port on the publicly routable IP address that will be used to receive LCAP (LOCKSS polling and repair) traffic. Historically, most LOCKSS nodes use 9729.
PROXY port:Not yet re-enabled in 2.0-alpha1; ignore.
Mail relay for this machine:Hostname for this machine’s outgoing mail server.
Does mail relay <mailhost> need user & password: Enter Y if the outgoing mail server requires password authentication, N otherwise.
User for <mailhost>:If you answered Y to the outgoing mail server password authentication question, enter the username for the mail server.
Password for <mailuser>@<mailhost>:Enter the password for the given username.
Again:Re-enter the mail server password (if the two passwords do not match, the password will be asked again).
E-mail address for administrator:Enter the e-mail address of the person or team who will administer the LOCKSS system on this machine.
Configuration URL:Enter the URL of the LOCKSS network configuration file. If you are not running your own LOCKSS network, use
http://props.lockss.org:8001/demo/lockss.xml, the configuration file for a demo network set up for LOCKSS 2.0 pre-release testing.
Configuration proxy (host:port):enter a host:port combination for the proxy server needed to reach the network configuration file (or simply hit Enter if none is needed).
Preservation group(s):Enter a semicolon-separated list of preservation network identifiers. If you are not joining an existing network or running your own, enter demo, the network identifier for the demo network set up for LOCKSS 2.0 pre-release testing.
Content data storage directory:Enter the path of a directory that is the root of the main storage area of the LOCKSS system. If you are used to the classic LOCKSS daemon (1.x), this would be the equivalent of
Service logs directory:Enter the path of a directory that is the root of the storage area for LOCKSS-related log files (historically
Temporary storage directory:not actively used in LOCKSS 2.0-alpha2; ignore.
User name for web UI administration:Enter the username for an administrative user in the LOCKSS system’s Web user interfaces.
Password for web UI administration user <uiuser>:Enter the password for the given administrative user in the LOCKSS system’s Web user interfaces.
Password for web UI administration user <uiuser> (again):Re-enter the password for the given administrative user in the LOCKSS system’s Web user interfaces (if the two passwords do not match, the password will be asked again).
Password for database:Enter the password for the embedded Postgres database included in LOCKSS 2.0-alpha. Future versions will allow you to use an existing Postgres database and enter credentials accordingly.
Password for database (again):Re-enter the password for the embedded Postgres database (if the two passwords do not match, the password will be asked again).
OK to store this configuration:confirm with Y that the summarized configuration data is correct and that you are ready to write it to a file.
If prompted to generate files, accept (or run
scripts/generate-lockss immediately after).