did not work. still get the same error

in the durable place I see:

root@IRIS:/dur/iconfig/csp/bin# ls -lt
total 16
-rw-rw-r-- 1 irisuser irisuser 5943 Aug 21 23:57 CSP.log
-rw-rw---- 1 irisuser irisuser  257 Aug 21 23:57 CSPRT.ini
-rw-rw---- 1 irisuser irisuser  745 Aug 21 23:57 CSP.ini
 

docker exec -it sam_iris_1 bash
root@IRIS:/tmp# cd /usr/irissys/csp/bin/
root@IRIS:/usr/irissys/csp/bin# ls
CSP.ini  CSP.log  CSPRT.ini  CSPa24.so  CSPa24Sys.so  CSPx.so  libz.so  temp
root@IRIS:/usr/irissys/csp/bin# ls -lt
total 3244
-rw-rw-r-- 1 www-data  www-data     6063 Aug 22 15:56 CSP.log
-rw-rw---- 1 irisuser  irisuser      253 Aug 21 23:57 CSPRT.ini
-rw-rw---- 1 irisuser  irisuser      606 Jun 26  2020 CSP.ini
-rwxrwxr-x 1 irisowner irisowner 1169384 Jun 26  2020 CSPa24.so
-rwxrwxr-x 1 irisowner irisowner  869720 Jun 26  2020 CSPa24Sys.so
-rwxrwxr-x 1 irisowner irisowner 1135208 Jun 26  2020 CSPx.so
-rwxr-xr-x 1 irisowner irisowner  117168 Jun 26  2020 libz.so
dr-xr-x--- 1 irisuser  irisuser     4096 Jun 26  2020 temp

I need to correct my last response. I did receive WRC response on Friday with this:

After discussing this issue with co-workers:

The message is due to the reassignment of the IP address:

  Yes – the basically the IP address changing underneath the mirror node “changed it’s identity”. This is expected behavior for mirroring.

Possible to setup virtual IP address/or DNS name for each member then in script assign new IP to the member's DNS name

Also not to use ECS but something long these lines found in this link, look it over and see if it applies:

https://medium.com/galvanize/static-ip-applications-on-aws-ecs-c7d411421d4f

I encountered another challenge this week. I utilized AWS Elastic Container Service (ECS) to deploy two Fargate tasks running IRIS MessageBank Mirror. The first task started on ip-10-xxx-xxx-146. It used failover1 volume which had previously been used by ip-10-xxx-xxx-168. The second task started on ip-10-xxx-xxx-168. The second task ran on failover2 volume. It started MessageBank production and it became Primary. Mirror Service did not start on the first task. In messages.log I saw:

Mirroring not started, this instance appears to have been copied. See ^MIRROR

I suspect this happened because the randomly assigned IP address for the second task matched the prior IP address of the first task. I opened a support ticket with InterSystems WRC on Tuesday morning and I still wait for their response.

Hello,

Started working on Message Bank mirror. Realized there is a MessageBank production running in the namespace with the mirrored database. I probably need to control the AutoStart global to start the production only on the Primary...

Hi Michael,

I implemented Message Bank because I did not want to check multiple instances trying to see what messages were processed in each production. Does that make sense?

Message bank is a central location for messages and logs from multiple productions. Please see my article here:

IRIS Interoperability Message Bank | InterSystems Developer Community | AWS
 

Not sure why my poll is closed :-(

Craig, our Health Connect production handles supply chain messages for Department of Veterans Affairs. Many of the messages are recordmap files. Messages volume is low. I hope to learn how to architect a solution that is reliable and scalable, just in case traffic increases or I can transfer this experience to the next project.