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 |
bash version below 4.2 |
Update bash. The installer uses associative arrays, and this cannot be avoided. |
Utilities not found |
The check requires |
|
These two are needed only for ssh installation: |
|
Install |
Platform image not found |
Place |
Failed to connect over ssh |
Check the address, port, and key with a regular |
No access to docker |
The daemon responds only to root, and |
|
|
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 |
|---|---|
|
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. |
|
The user is not in the |
|
The image was not fully copied. When installing over ssh, check that copying of large files completed. |
|
The cluster directory is not empty. Allow clearing ( |
|
The directory or port is not labeled. Check that |
|
Installation will continue, but the directory is marked with the |
|
|
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 examplemic1), not written asmic. - Report not received within the allotted time
-
This is a warning, not a refusal. The container may simply have been starting slowly. Check
docker psanddocker 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
whiptailordialog, on others — onlydialog. 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
-
The run log — it is self-contained: it contains the version, OS, command line, and all commands.
-
The return code.
-
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.