Simulacro (MSRS)Not yet available
Real SSH and database access commands are generated here once this environment provisions successfully.
Environment PORT-ALLOC-VERIFY-2 (msrs-env-0025)
Current status: Failed · Deployment: SHR Colocated (shared host) · Install: Tarball (myharem)
- Display ID
- msrs-env-0025
- Internal ID
- eaafbce8-9e0c-4720-9546-2a750a6d9e41
- Status
- Failed
- Profile
- VM
- Provider
- aws
- Setup source
- custom-75084ac7-fcd0-4e5a-a77d-7932ba1f123b
- MariaDB
- custom-multi-node
- Distro
- mixed
- Retention
- 9/10/2026, 9:13:56 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
Stub instructions: no successful provision yet. Real hostnames and access commands are produced once a provisioning backend runs.
| Node | Host | Port | User | Role | Cluster |
|---|---|---|---|---|---|
| Volgo-01 | port-alloc-verify-2-cluster-a-volgo-01.stub.msrs.internal | - | support | master | cluster-a (async_replica) |
| Volgo-02 | port-alloc-verify-2-cluster-a-volgo-02.stub.msrs.internal | - | support | slave | cluster-a (async_replica) |
Connection methods
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 · failure · claudio.nanni@mariadb.comdecommission failed: Command failed: ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -i /etc/simulacro/keys/msrs-myharem rocky@63.187.135.15 sudo mh cluster erase 50 --yes --purge Error: No deployment '50' 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.
- decommission · failure · claudio.nanni@mariadb.comdecommission failed: Command failed: ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -i /etc/simulacro/keys/msrs-myharem rocky@63.187.135.15 sudo mh cluster erase 50 --yes --purge Error: No deployment '50' 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.
- decommission · failure · claudio.nanni@mariadb.comdecommission failed: Command failed: ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -i /etc/simulacro/keys/msrs-myharem rocky@63.187.135.15 sudo mh cluster erase 50 --yes --purge Error: No deployment '50' 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.
- decommission · failure · claudio.nanni@mariadb.comdecommission failed: Command failed: ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -i /etc/simulacro/keys/msrs-myharem rocky@63.187.135.15 sudo mh cluster erase 50 --yes --purge Error: No deployment '50' 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 · failure · support.engineer@mariadb.localprovision failed: Command failed: ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -i /etc/simulacro/keys/msrs-myharem rocky@63.177.106.175 sudo mh --json deployreplication mariadb-10.6.18-linux-systemd-x86_64.tar.gz 50 --slaves 1 Deploying replication: master=50, slaves=[60] 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.50 [2/4] Extracting mariadb-10.6.18-linux-systemd-x86_64.tar.gz... Extracted in 13.6s [3/4] Skipping my.cnf (custom config will be applied) [4/4] Skipping database init (done after config) Instance 50 deployed in 13.6s Generated my.cnf at /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.50/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.50/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.50' ; /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.50/bin/mariadbd-safe --datadir='/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.50/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.50/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 60 === 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.60 [2/4] Extracting mariadb-10.6.18-linux-systemd-x86_64.tar.gz... Extracted in 16.3s [3/4] Skipping my.cnf (custom config will be applied) [4/4] Skipping database init (done after config) Instance 60 deployed in 16.5s Generated my.cnf at /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.60/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.60/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.60' ; /var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.60/bin/mariadbd-safe --datadir='/var/opt/data/myharem/instances/mariadb-10.6.18-linux-systemd-x86_64.60/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.60/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 50... Waiting for instance 50 to be ready................................. Replication deploy failed — rolling back. Error: Instance 50 did not start within 30s. Check log: mh log 50 . Environment marked FAILED; retry or decommission.
- provision-started · success · support.engineer@mariadb.localProvisioning started via colocated executor (attempt 1).
- create · success · support.engineer@mariadb.localSetup saved with preset 'custom-75084ac7-fcd0-4e5a-a77d-7932ba1f123b'. Review and run provision when ready.