What to do on error

The first action is always the same: look at the log. The path is printed as the last line of any run; the link to the latest is logs/last.log.

Prechecks failed (code 3)

The server was not changed.

Message What to do

OS not supported

Check ID in /etc/os-release. The family list is in era_installer/reference-os-matrix.adoc#era-installer-os-matrix.

bash version below 4.2

Update bash. The installer uses associative arrays, and this cannot be avoided.

Utilities not found

The check requires tar, grep, sed, awk, find — the message names those that are missing. Install them with your OS packages; the full list with explanations is in era_installer/requirements.adoc#era-installer-requirements-tools.

ssh and rsync — not found / no rsync on the target host

These two are needed only for ssh installation: ssh and rsync on your machine and rsync on the target host — the distribution is copied with it. Install with a regular package: sudo apt-get install rsync (or dnf install rsync). A freshly deployed server usually lacks it.

sudo is absent

Install sudo or run as root.

Platform image not found

Place era_*.tar.gz in era/image or specify the path with --eradockerimagepath.

Failed to connect over ssh

Check the address, port, and key with a regular ssh. If the server was reinstalled — see era_installer/preparation.adoc#era-installer-preparation-known-hosts.

No access to docker

The daemon responds only to root, and sudo requires a password. In interactive mode the password is asked; in non-interactive mode root, membership in the docker group, or passwordless sudo is required.

docker not installed, daemon not responding

systemctl status docker on the target host.

Key error (code 2)

The installer stops at the first unknown key and suggests a similar one:

Unknown parameter "--masterdomian". Did you mean "--masterdomain"?

This is intentional: in the previous version a typo was silently ignored, and installation proceeded with a default instead of the specified value. The previous behavior is restored by the --ignore-unknown key.

The second common cause of code 2 is --non-interactive without all required values. Then the missing keys are listed.

Error during application (code 5)

The server was partially changed. Find the last EXEC line in the log without dry-run: not executed — this is the command where everything stopped.

Sign in the log Cause and what to do

apt-get/yum could not download a package

No internet access or proxy not set. See era_installer/preparation.adoc#era-installer-preparation-proxy. On CentOS 7 — era_installer/reference-os-matrix.adoc#era-installer-os-matrix-centos7.

docker: permission denied

The user is not in the docker group and there is no sudo.

docker load did not find the file

The image was not fully copied. When installing over ssh, check that copying of large files completed.

initdb refused to work

The cluster directory is not empty. Allow clearing (--pgcleardatafolder=y) or specify another path.

pg_ctl does not start, and SELinux is in enforcing

The directory or port is not labeled. Check that semanage is installed: era_installer/reference-os-matrix.adoc#era-installer-os-matrix-selinux.

mount failed to mount NFS

Installation will continue, but the directory is marked with the nomount.sign file. The platform will not accept it as working storage. Deal with the NFS server and repeat the run.

Failed to obtain root privileges

sudo requires a password and there is nowhere to ask it: non-interactive mode or ssh launch. Check the rule as described in era_installer/requirements.adoc#era-installer-requirements-privileges — with cache reset (sudo -k), otherwise the check lies.

A repeated run with the same answers file is safe: the actions are idempotent. But first eliminate the cause — otherwise the repeat will hit it again.

Code 5 but all commands ran

It means the "what changed on the server" form showed [FAIL]: the queue reached the end, but the change was not confirmed by the check. The form row names which one — an unmounted directory, an unresponsive cluster, a non-started container.

Such steps intentionally do not interrupt installation: the form is printed precisely so that their failure does not go unnoticed. The [warn] label does not affect the return code: the server works, albeit not completely.

Container started but the platform does not respond

The installer waits up to a minute for an initialization report from the container. Possible outcomes:

Report received, result success

Everything is fine.

Report received, result with an error

The error was reported by the image itself, not the installer, but the run ends with code 5. The cause is in the report line; see docker logs <container>. A common cause on a non-master is an incorrect --micaddress: the role name is taken from the platform configuration (for example mic1), not written as mic.

Report not received within the allotted time

This is a warning, not a refusal. The container may simply have been starting slowly. Check docker ps and docker logs.

If the container runs but the web interface is inaccessible externally — almost always the cause is firewalld. The installer does not know the ports the platform opens itself and cannot open them: era_installer/reference-os-matrix.adoc#era-installer-os-matrix-firewall.

Connection error (code 6)

The connection is checked before the installation survey, so code 6 usually means the server is unavailable or the key did not match.

Check manually:

ssh -p 22 user@192.168.0.10 'echo ok'

If ssh works but the installer does not, run it with --verbose: the exact ssh and rsync commands will be in the log.

Interface looks broken

Columns drift, garbage instead of letters

The terminal is not UTF-8. The installer switches to English itself and says so. Set a UTF-8 locale if a non-English interface is needed: era_installer/requirements.adoc#era-installer-requirements-locale.

Text questions instead of frames

A suitable tool was not found: on Debian-like systems it is whiptail or dialog, on others — only dialog. This is a full operating mode. Pseudo-graphics can be demanded explicitly: --ui=tui.

The screen shows param.<something>.prompt

A translation defect: the key exists in the code but is absent from the message catalog. Installation still works. Report it to the installer developer.

What to attach to a request

  1. The run log — it is self-contained: it contains the version, OS, command line, and all commands.

  2. The return code.

  3. For ssh installation — both logs, yours and the one fetched from the server.

Passwords in the log are masked, but check this before sending, especially if you ran with --log-secrets.