Cronicle Static server name & ip doesn’t update

I am using AWS ECS to deploy Cronicle using s3 data backup. Everything works fine on the first time. However when I re-deploy the application, the login page doesn’t show up and UI stucks at “Loading master”.

On further debugging, I noticed that the server_group/0.json and server/0.json has the server name (eg cronicle-abcde-123ab) and IP (eg 192.168.88.13) which changes each time if the application re-deployed. And probably the next time when it looks into s3 data files, cronicle doesn’t find new values which was set later and hence UI stucks.

Shouldn’t it update the data files with new values? Any help would be appreciated to over come this. Thanks.

Aug 29 '22 02:08 asharma2040

See: https://github.com/jhuckaby/Cronicle/issues/95#issuecomment-411584456

Also see: https://github.com/jhuckaby/Cronicle/wiki/Troubleshooting for a full explanation.

Aug 29 '22 02:08 jhuckaby

@asharma2040 You need to keep static hostname (service name). IP may change. Share your deployment yaml if you still can't figure it out.

Aug 29 '22 20:08 mikeTWC1984

Thanks for helping guys.

I tried deployed it on EC2 (AWS virtual machine) using docker with s3 data backup & when I delete running container and re-deploy it, it agains stuck at master. I tried following #95 solution but when I run control.sh stop. It exits the running container. Can there be an easy fix for this which I can include while building my docker image?

Aug 30 '22 21:08 asharma2040