Simulacro (MSRS)SSH — Volgo-01
Log into the host running Volgo-01.
ssh rocky@18.197.171.86
Environment ZD_001 (msrs-env-0016)
Current status: Decommissioned · Deployment: SHR Colocated (shared host) · Install: Tarball (myharem)
- Display ID
- msrs-env-0016
- Internal ID
- 73ab90af-ba5d-4dc2-b873-5c0bf3ba4102
- Status
- Decommissioned
- Profile
- VM
- Provider
- aws
- Setup source
- custom-75084ac7-fcd0-4e5a-a77d-7932ba1f123b
- MariaDB
- custom-multi-node
- Distro
- mixed
- Retention
- 9/10/2026, 5:23:26 PM
- Auto-stop
- -
- Primary timezone
- UTC
- Assigned engineer timezones
- UTC
- Challenge timeout
- 30 minutes
- Presence challenge
- none
Lifecycle actions
Pause/decommission is enforced at whole-environment scope. Partial single-node lifecycle outcomes are not supported.
Timezone policy: UTC · Challenge timeout: 30 min
Setup can be edited until provisioning starts. Pause/Resume controls compute cost state; MariaDB service operations stay manual after provisioning.
Node access targets
Access targets from the last successful provision via the colocated executor. Real host — SSH access requires whatever key/credentials that host's operator has configured for you.
| Node | Host | Port | User | Role | Cluster |
|---|---|---|---|---|---|
| Volgo-01 | 18.197.171.86 | 10000 | rocky | master | cluster-a (async_replica) |
| Volgo-02 | 18.197.171.86 | 20000 | rocky | slave | cluster-a (async_replica) |
Connection methods
MariaDB client — Volgo-01
Connect to this node's MariaDB via myharem's CLI, over the SSH session above.
ssh rocky@18.197.171.86 sudo mh cli 10000
SSH — Volgo-02
Log into the host running Volgo-02.
ssh rocky@18.197.171.86
MariaDB client — Volgo-02
Connect to this node's MariaDB via myharem's CLI, over the SSH session above.
ssh rocky@18.197.171.86 sudo mh cli 20000
Custom topology
1 clusters, 0 MaxScale, 2 nodes, 0 links
cluster-a (Async replica cluster)
| Node | Role | Edition | MariaDB | Distro |
|---|---|---|---|---|
| Volgo-01 | master | CS | 10.6.18 | rocky 9 |
| Volgo-02 | slave | CS | 10.6.22 | rocky 9 |
Event timeline
- decommission · success · claudio.nanni@mariadb.comDecommission completed via colocated executor. All nodes removed.
- decommission-started · success · claudio.nanni@mariadb.comDecommission started via colocated executor. All nodes in this environment are torn down together.
- decommission · failure · claudio.nanni@mariadb.comdecommission failed: Command failed: ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -i /etc/simulacro/keys/msrs-myharem rocky@18.197.171.86 sudo mh cluster erase 10000 --yes --purge Error: No deployment '10000' in the manifest. (Deploy via mh deploygalera/deployreplication, or list with mh list.) . Environment marked FAILED; retry or decommission.
- decommission-started · success · claudio.nanni@mariadb.comDecommission started via colocated executor. All nodes in this environment are torn down together.
- provision · success · claudio.nanni@mariadb.comProvision completed via colocated executor. Setup is locked; 2 node(s) ready.
- provision-started · success · claudio.nanni@mariadb.comProvisioning started via colocated executor (attempt 3).
- provision · failure · claudio.nanni@mariadb.comprovision failed: Command failed: ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -i /etc/simulacro/keys/msrs-myharem rocky@18.197.171.86 sudo mh --json deployreplication mariadb-10.6.18-linux-systemd-x86_64.tar.gz 10000 --slaves 1 Deploying replication: master=10000, slaves=[20000] Found tarball in local: /var/opt/data/myharem/local/mariadb-10.6.18-linux-systemd-x86_64.tar.gz === Deploying Master === Found tarball in local: /var/opt/data/myharem/local/mariadb-10.6.18-linux-systemd-x86_64.tar.gz [1/4] Creating instance directory: mariadb-10.6.18-linux-systemd-x86_64.10000 [2/4] Extracting mariadb-10.6.18-linux-systemd-x86_64.tar.gz... Extracted in 9.7s [3/4] Skipping my.cnf (custom config will be applied) [4/4] Skipping database init (done after config) Instance 10000 deployed in 9.7s Generated my.cnf at /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/my.cnf Initializing the database... Database initialized successfully. Installing MariaDB/MySQL system tables in '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/data' ... OK To start mariadbd at boot time you have to copy support-files/mariadb.service to the right place for your system Two all-privilege accounts were created. One is root@localhost, it has no password, but you need to be system 'root' user to connect. Use, for example, sudo mysql The second is rocky@localhost, it has no password either, but you need to be the system 'rocky' user to connect. After connecting you can set the password, if you would need to be able to connect as any of these users with a password and without sudo See the MariaDB Knowledgebase at https://mariadb.com/kb You can start the MariaDB daemon with: cd '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000' ; /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/bin/mariadbd-safe --datadir='/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/data' You can test the MariaDB daemon with mysql-test-run.pl cd '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/mysql-test' ; perl mariadb-test-run.pl Please report any problems at https://mariadb.org/jira The latest information about MariaDB is available at https://mariadb.org/. Consider joining MariaDB's strong and vibrant community: https://mariadb.org/get-involved/ === Deploying Slave 20000 === Found tarball in local: /var/opt/data/myharem/local/mariadb-10.6.18-linux-systemd-x86_64.tar.gz [1/4] Creating instance directory: mariadb-10.6.18-linux-systemd-x86_64.20000 [2/4] Extracting mariadb-10.6.18-linux-systemd-x86_64.tar.gz... Extracted in 9.3s [3/4] Skipping my.cnf (custom config will be applied) [4/4] Skipping database init (done after config) Instance 20000 deployed in 9.3s Generated my.cnf at /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/my.cnf Initializing the database... Database initialized successfully. Installing MariaDB/MySQL system tables in '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/data' ... OK To start mariadbd at boot time you have to copy support-files/mariadb.service to the right place for your system Two all-privilege accounts were created. One is root@localhost, it has no password, but you need to be system 'root' user to connect. Use, for example, sudo mysql The second is rocky@localhost, it has no password either, but you need to be the system 'rocky' user to connect. After connecting you can set the password, if you would need to be able to connect as any of these users with a password and without sudo See the MariaDB Knowledgebase at https://mariadb.com/kb You can start the MariaDB daemon with: cd '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000' ; /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/bin/mariadbd-safe --datadir='/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/data' You can test the MariaDB daemon with mysql-test-run.pl cd '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/mysql-test' ; perl mariadb-test-run.pl Please report any problems at https://mariadb.org/jira The latest information about MariaDB is available at https://mariadb.org/. Consider joining MariaDB's strong and vibrant community: https://mariadb.org/get-involved/ === Starting Master === Starting instance 10000... Waiting for instance 10000 to be ready... OK Ensuring service users/grants (myharem, mh_repl, mh_sst)... Service users/grants ensured. === Starting + wiring Slave 20000 === Starting instance 20000... Waiting for instance 20000 to be ready... OK Ensuring service users/grants (myharem, mh_repl, mh_sst)... Service users/grants ensured. Replication deploy failed — rolling back. Instance 10000 stopped successfully. Instance 20000 stopped successfully. Error: SQL error on instance 20000: ERROR 29 (HY000) at line 1: File './relay-bin.index' not found (Errcode: 2 "No such file or directory") . Environment marked FAILED; retry or decommission.
- provision-started · success · claudio.nanni@mariadb.comProvisioning started via colocated executor (attempt 2).
- provision · failure · claudio.nanni@mariadb.comprovision failed: Command failed: ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -i /etc/simulacro/keys/msrs-myharem rocky@18.197.171.86 sudo mh --json deployreplication mariadb-10.6.18-linux-systemd-x86_64.tar.gz 10000 --slaves 1 Deploying replication: master=10000, slaves=[20000] Found tarball in local: /var/opt/data/myharem/local/mariadb-10.6.18-linux-systemd-x86_64.tar.gz === Deploying Master === Found tarball in local: /var/opt/data/myharem/local/mariadb-10.6.18-linux-systemd-x86_64.tar.gz [1/4] Creating instance directory: mariadb-10.6.18-linux-systemd-x86_64.10000 [2/4] Extracting mariadb-10.6.18-linux-systemd-x86_64.tar.gz... Extracted in 8.6s [3/4] Skipping my.cnf (custom config will be applied) [4/4] Skipping database init (done after config) Instance 10000 deployed in 8.6s Generated my.cnf at /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/my.cnf Initializing the database... Database initialized successfully. Installing MariaDB/MySQL system tables in '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/data' ... OK To start mariadbd at boot time you have to copy support-files/mariadb.service to the right place for your system Two all-privilege accounts were created. One is root@localhost, it has no password, but you need to be system 'root' user to connect. Use, for example, sudo mysql The second is rocky@localhost, it has no password either, but you need to be the system 'rocky' user to connect. After connecting you can set the password, if you would need to be able to connect as any of these users with a password and without sudo See the MariaDB Knowledgebase at https://mariadb.com/kb You can start the MariaDB daemon with: cd '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000' ; /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/bin/mariadbd-safe --datadir='/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/data' You can test the MariaDB daemon with mysql-test-run.pl cd '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/mysql-test' ; perl mariadb-test-run.pl Please report any problems at https://mariadb.org/jira The latest information about MariaDB is available at https://mariadb.org/. Consider joining MariaDB's strong and vibrant community: https://mariadb.org/get-involved/ === Deploying Slave 20000 === Found tarball in local: /var/opt/data/myharem/local/mariadb-10.6.18-linux-systemd-x86_64.tar.gz [1/4] Creating instance directory: mariadb-10.6.18-linux-systemd-x86_64.20000 [2/4] Extracting mariadb-10.6.18-linux-systemd-x86_64.tar.gz... Extracted in 8.5s [3/4] Skipping my.cnf (custom config will be applied) [4/4] Skipping database init (done after config) Instance 20000 deployed in 8.6s Generated my.cnf at /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/my.cnf Initializing the database... Database initialized successfully. Installing MariaDB/MySQL system tables in '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/data' ... OK To start mariadbd at boot time you have to copy support-files/mariadb.service to the right place for your system Two all-privilege accounts were created. One is root@localhost, it has no password, but you need to be system 'root' user to connect. Use, for example, sudo mysql The second is rocky@localhost, it has no password either, but you need to be the system 'rocky' user to connect. After connecting you can set the password, if you would need to be able to connect as any of these users with a password and without sudo See the MariaDB Knowledgebase at https://mariadb.com/kb You can start the MariaDB daemon with: cd '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000' ; /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/bin/mariadbd-safe --datadir='/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/data' You can test the MariaDB daemon with mysql-test-run.pl cd '/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/mysql-test' ; perl mariadb-test-run.pl Please report any problems at https://mariadb.org/jira The latest information about MariaDB is available at https://mariadb.org/. Consider joining MariaDB's strong and vibrant community: https://mariadb.org/get-involved/ === Starting Master === Starting instance 10000... Waiting for instance 10000 to be ready.... OK Ensuring service users/grants (myharem, mh_repl, mh_sst)... Warning: user creation failed: /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.10000/bin/mariadb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory === Starting + wiring Slave 20000 === Starting instance 20000... Waiting for instance 20000 to be ready.... OK Ensuring service users/grants (myharem, mh_repl, mh_sst)... Warning: user creation failed: /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/bin/mariadb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory Replication deploy failed — rolling back. Error: SQL error on instance 20000: /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.20000/bin/mariadb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory . Environment marked FAILED; retry or decommission.
- provision-started · success · claudio.nanni@mariadb.comProvisioning started via colocated executor (attempt 1).