Installing on a slave server using the installer

Overview

If additional servers were listed during master server installation, the wizard does not have to be run here: the master printed a ready non-interactive command for each of them — with the node role, mic address, database, and master NFS server.
The commands are saved next to the master server log in the .cmd file; the required one remains to be executed on this server.

System installation is performed from a local machine via an ssh connection to the server if the available server address matches the address on which the system is to be deployed.

cd /tmp/era_installer

bash install_ssh.sh --ui=text

Otherwise, when the server local address is not accessible externally, first unpack and copy the installer to the server, then connect over ssh and run the script.

rsync -avrh --progress -e "ssh -p PORT" /tmp/era_installer USER@HOST:/tmp

ssh USER@HOST -p PORT

cd /tmp/era_installer

bash era/scripts/install.sh --ui=text

The --ui=text key sets text mode: questions are asked line by line, and the answer is confirmed with Enter.
The same can be run via the dispatcher: bash era/era.sh install --ui=text.

IMPORTANT! The configuration with this server must be created and activated on the master before node installation: the node looks for its role in the applied configuration.
If there is no configuration, installation completes, but the platform reports ServInit. Connect to All MICIC fail, and the installer exits with code 5.

Installation process algorithm

1) Run the installation script: on the local machine bash install_ssh.sh --ui=text, on the server bash era/scripts/install.sh --ui=text.

When launched from the local machine, connection data is asked first, then the installer copies files to the server and continues the survey there.

Server address: 192.168.0.116
ssh user: admin
ssh port [22]:
ssh key file:

2) Wait for files to be copied to the server.

Copy era/image/era_1_11_0-2026_8_31_1_docker.tar.gz (1.2G)? (y/n) [y]:

3) Screen Server and role. The role is not master, so mic addresses are asked instead of the domain.

== Server and role ==
Platform IP address: 192.168.0.116
Instance name postfix: _01
Data path [/opt]:
Server name in configuration [box-116]: srv02
Is this the master server? (y/n): n
Mic addresses: mic1@192.168.0.115
PSK cookie [era2020key]:

Postfix should be the same as on the master server of the same configuration.

Server name must match the name of this server in the configuration created on the master.

Mic addresses — addresses of infrastructure microservices of the already deployed cluster, comma-separated without spaces.
The role name is taken from the platform configuration: if the role is called mic1 there, the address is written as mic1@192.168.0.115, not mic@….
Several addresses can be listed — connection will be attempted sequentially.

PSK cookie must match the one set during master server installation.

4) Screen Packages and network. Specify whether the server has internet access and whether a proxy is needed.

== Packages and network ==
Allow the installer to download packages from the internet? (y/n) [y]:
Use an http/https proxy? (y/n) [n]:

If there is no internet access, answer n and, if the missing package list is non-empty, perform package installation on the server.

5) Screen PostgreSQL — mode.

== PostgreSQL -- mode ==
Install PostgreSQL? (y/n) [y]: n

In a multi-server installation, DBMS instances are installed only on selected servers according to the deployment plan: the first of them is the master server, the second is any other.
On the remaining servers answer n — then connection parameters to an already running PostgreSQL server are requested.

If this server is selected for the second DBMS, answer y and specify the Replica (recovery) role:

Where to place PostgreSQL?
   1) On the host
   2) In a docker container
Choose a number: 1
Role of this PostgreSQL instance
   1) Master
   2) Replica (recovery)
Choose a number: 2

The passwords of the postgres, platformpgadmin, and era_replica users must match those set on the master server — otherwise streaming replication will not start.

6) Screen PostgreSQL — access. For a server without its own DBMS, the address and port of the ready server are specified.

== PostgreSQL -- access ==
PostgreSQL server IP address: 192.168.0.115
PostgreSQL port [5441]:
DB user for the platform [platformpgadmin]:
Password of DB user platformpgadmin [••••••]:

The values must match those set during master server installation.

7) Screen Platform volumes. Specify host directories for container volumes.

== Platform volumes ==
Volume for /var/lib/era [/opt/era_01/lib]:
Volume for /var/log/era [/opt/era_01/log]:
Volume for /var/lib/era_files/local [/opt/era_01/local]:
Volume for /var/lib/era_files/rectemp [/opt/era_01/rectemp]:
Volume for /var/lib/era_files/logstore [/opt/era_01/logstore]:
Volume for /var/lib/era_files/syncroot [/opt/era_01/syncroot]:
Volume for /var/lib/era_files/a [/opt/era_01/a]:
Volume for /var/lib/era_files/b [/opt/era_01/b]:
Volume for /var/lib/era_files/c [/opt/era_01/c]:

Default values should be changed if the deployment plan provides for placement in a specific mounted partition.
The purpose of the directories is described in the master server installation instructions.

8) Screen NFS. Specify client directories and the NFS server address.

== NFS ==
Local directory for /var/lib/recpath [/opt/era_01/era_recpath]:
Local directory for /var/lib/siteshare [/opt/era_01/era_siteshare]:
Local directory for /var/lib/globalshare [/opt/era_01/era_globalshare]:
Start an NFS server on this host? (y/n) [n]: n
NFS server address: 192.168.0.115

The NFS server address should be the same as during master server installation.
If the NFS server is started on another host with a different postfix, specify paths to its directories explicitly — with the --recpathnfssrvdir, --sitesharenfssrvdir, --globalsharenfssrvdir keys: the default is calculated from this server postfix and does not fit different postfixes.

The NFS server role should not be enabled on a node.

9) Screen Kernel parameters.

== Kernel parameters ==
Reuse connections in TIME_WAIT? (y/n) [n]:

10) Screen Check installation parameters. Check the summary and plan and select "Continue".

What do we do?
   1) Continue -- start changing the server  [*]
   2) Change...
   ...
Choose a number:

Until this moment the server has not been changed.

11) Wait for execution and the container report.

== Apply ==
  -> [1/6] Volume directories
  ...
Waiting up to 60 s for the container initialization report.
Container initialized: Install server success!

If the platform responds ServInit. Connect to All MICIC fail, the master does not see this server in the applied configuration: check that the configuration is created, active, and contains a server with this name and address.

12) Look at the "what changed on the server" form: it is printed immediately after application.

== What changed on the server ==
  [ ok ] Volume directories                  12 in /opt
  [ ok ] Shared directories                  mounted: 3
  [ ok ] Kernel parameters                   fs.inotify.max_user_watches = 10000000
  [ ok ] Platform container                  era_01, started
  [ ok ] Platform initialization             Install server success!

[FAIL] means the change failed: the installer will exit with code 5 even if all commands ran.
Most often this is an unmounted NFS directory — it does not interrupt installation, and without the form its failure would be visible only in the log.
More: manuals:era_installer/install-local.adoc#era-installer-install-local-changes.

13) Save the commands printed at the end: reinstallation and removal of this server.
The answers file .params and the ready command .cmd with 0600 permissions remain next to the log.

Installation complete!
You can proceed to installing the system on the next server!
If the system is installed on all servers, you can proceed to creating and configuring domains.