Unable to setup HA group for event broker on Windows Docker

jonathanstuhrasferg

Hi

I followed the guide for setting up HA group locally on my computer:

https://docs.solace.com/Configuring-and-Managing/SW-Broker-Specific-Config/Docker-Tasks/HA-Config/HA-Docker-Windows.htm

When i run the docker start primary backup monitoring command the containers startup, but after 30-45 sec. the containers shutdown again.

I created the network using the command:

docker network create solace-net

Create command for primary:

docker create -p 212:2222 -p 213:8080 -p 214:55555 -p 215:8300 -p 216:8301 -p 217:8302 -p 218:8741 `
--shm-size=1g `
--ulimit nofile=2448:38048 `
--env 'username_admin_globalaccesslevel=admin' `
--env 'username_admin_password=admin' `
--env 'system_scaling_maxconnectioncount=100' `
--name=primary `
--hostname=primary `
--env 'routername=primary' `
--network solace-net `
--env 'nodetype=message_routing' `
--env 'configsync_enable=yes' `
--env 'redundancy_enable=yes' `
--env 'redundancy_group_node_primary_connectvia=primary' `
--env 'redundancy_group_node_primary_nodetype=message_routing' `
--env 'redundancy_group_node_backup_connectvia=backup' `
--env 'redundancy_group_node_backup_nodetype=message_routing' `
--env 'redundancy_group_node_monitoring_connectvia=monitoring' `
--env 'redundancy_group_node_monitoring_nodetype=monitoring' `
--env 'redundancy_authentication_presharedkey_key=1234' `
--env 'redundancy_activestandbyrole=primary' `
--env 'redundancy_matelink_connectvia=backup' `
solace-pubsub-standard:9.13.1.38

Create command for backup:

docker create -p 312:2222 -p 313:8080 -p 314:55555 -p 315:8300 -p 316:8301 -p 317:8302 -p 318:8741 `
--shm-size=1g `
--ulimit nofile=2448:38048 `
--env 'username_admin_globalaccesslevel=admin' `
--env 'username_admin_password=admin' `
--env 'system_scaling_maxconnectioncount=100' `
--name=backup `
--hostname=backup `
--env 'routername=backup' `
--network solace-net `
--env 'nodetype=message_routing' `
--env 'configsync_enable=yes' `
--env 'redundancy_enable=yes' `
--env 'redundancy_group_node_primary_connectvia=primary' `
--env 'redundancy_group_node_primary_nodetype=message_routing' `
--env 'redundancy_group_node_backup_connectvia=backup' `
--env 'redundancy_group_node_backup_nodetype=message_routing' `
--env 'redundancy_group_node_monitoring_connectvia=monitoring' `
--env 'redundancy_group_node_monitoring_nodetype=monitoring' `
--env 'redundancy_authentication_presharedkey_key=1234' `
--env 'redundancy_activestandbyrole=backup' `
--env 'redundancy_matelink_connectvia=primary' `
solace-pubsub-standard:9.13.1.38

Create command for monitor

docker create -p 412:2222 -p 413:8080 -p 414:55555 -p 415:8300 -p 416:8301 -p 417:8302 -p 418:8741 `
--shm-size=1g `
--ulimit nofile=2448:38048 `
--env 'username_admin_globalaccesslevel=admin' `
--env 'username_admin_password=admin' `
--env 'system_scaling_maxconnectioncount=100' `
--name=monitoring `
--hostname=monitoring `
--env 'routername=monitoring' `
--network solace-net `
--env 'nodetype=monitoring' `
--env 'redundancy_enable=yes' `
--env 'redundancy_group_node_primary_connectvia=primary' `
--env 'redundancy_group_node_primary_nodetype=message_routing' `
--env 'redundancy_group_node_backup_connectvia=backup' `
--env 'redundancy_group_node_backup_nodetype=message_routing' `
--env 'redundancy_group_node_monitoring_connectvia=monitoring' `
--env 'redundancy_group_node_monitoring_nodetype=monitoring' `
--env 'redundancy_authentication_presharedkey_key=1234' `
solace-pubsub-standard:9.13.1.38

In the logs for the containers the last lines look like this(They are all the same):

2022-04-27T06:19:11.784+00:00 <local0.warning> monitoring appuser[1]: /usr/sw                        main.cpp:752                          (SOLDAEMON    - 0x00000000) main(0)@solacedaemon                          WARN     Determining platform type: [  OK  ]
2022-04-27T06:19:11.805+00:00 <local0.warning> monitoring appuser[1]: /usr/sw                        main.cpp:752                          (SOLDAEMON    - 0x00000000) main(0)@solacedaemon                          WARN     Generating license file: [  OK  ]
2022-04-27T06:19:11.883+00:00 <local0.warning> monitoring appuser[1]: /usr/sw                        main.cpp:752                          (SOLDAEMON    - 0x00000000) main(0)@solacedaemon                          WARN     Running pre-startup checks: [  OK  ]
Unable to raise event; rc(would block)

I have created an .wslconfig file:

# Settings apply across all Linux distros running on WSL 2
[wsl2]

# Limits VM memory to use no more than 6 GB, this can be set as whole numbers using GB or MB
memory=6GB 

# Sets amount of swap storage space to 2GB, default is 25% of available RAM
swap=2GB


# Sets the VM to use four virtual processors
processors=4

I can't see what I'm doing wrong. When i try to run a single Solace install on docker:

docker run -d -p 8080:8080 -p 4444:55555 -p:8008:8008 -p:1883:1883 -p:8000:8000 -p:5672:5672 -p:9000:9000 -p:2222:2222 --shm-size=2g --env username_admin_globalaccesslevel=admin --env username_admin_password=admin --name=solace solace/solace-pubsub-standard 

The container get's up and running with no issues.

/Jonathan