Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open EMR AWS Standard Cloud Formation #308

Closed
andrewbertran opened this issue Dec 9, 2021 · 10 comments
Closed

Open EMR AWS Standard Cloud Formation #308

andrewbertran opened this issue Dec 9, 2021 · 10 comments

Comments

@andrewbertran
Copy link

I tried installing the Open EMR AWS Standard Cloud Formation from the AWS marketplace but keep getting the stack error that the WebServerInstance failed. The EC2 instance is created and running but I'm unable to SSH using the designated keyfile (added port 22 to the security group) or access it through the browser.

image
image

There are no Outputs in the output tab which I believe is supposed to show my instances public IP.
All other components (DB in RDS, VPC, S3 etc.. get created successfully)

I left the Subnet and VPC settings at their default values.
The marketplace states OpenEMR version: 6.0.0 (Mar 10, 2021).
I also tried updating the Cloud formation template to use MySQL 5.7.

Does anyone have a more up to date Cloud formation template that works?

Thanks,
Andrew

@andrewbertran
Copy link
Author

Update, I was able to connect to the server as ubuntu user and access root.
After navigating to /root/openemr-devops/packages/standard/ I ran docker-compose up and got an error that the docker-compose.yml was using an incompatible version. I switched the version to 2.0 and then ran it again. Now the docker container is running and accessible through the browser. Im guessing it initially installed an older version of docker-compose.

To replicate the error after creating the stack.
SSH into the EC2 instance
Sudo -i
cd /root/openemr-devops/packages/standard/
docker-compose up

@jesdynf
Copy link
Collaborator

jesdynf commented Dec 10, 2021

Great job identifying that -- thanks! I have no idea what's going on in there but that's enough to get me looking (without the tests I couldn't run until this weekend).

By any chance do you know what version the file was showing before you fixed it?

@stephenwaite
Copy link
Sponsor Member

stephenwaite commented Dec 10, 2021

was working on a standard yesterday

docker-compose version 1.15.0, build e12f3b9

this was launched back in January of this year I believe

@jesdynf
Copy link
Collaborator

jesdynf commented Dec 10, 2021

Sorry, what internal version the docker-compose.yml was reporting, because I cannot recall changing that recently and it should be pretty static.

@stephenwaite
Copy link
Sponsor Member

docker-compose.yaml in standard directory is 3.1

@jesdynf
Copy link
Collaborator

jesdynf commented Dec 10, 2021

And that /works/ on the Standard you've installed? I knew I hadn't changed it recently.

@stephenwaite
Copy link
Sponsor Member

stephenwaite commented Dec 10, 2021

yes, just did a docker-compose up yesterday for let's encrypt

after upgrading to Ubuntu 18.04.6

@stephenwaite
Copy link
Sponsor Member

stephenwaite commented Dec 10, 2021

maybe @andrewbertran didn't run ./docker-compose up and instead grabbed the ubuntu version

Screenshot from 2021-12-10 16-58-43

@ralflukner
Copy link

@stephenwaite
I'm having the same problem on AWS when attempting to create STANDARD.
Is there a new cloudformation template file that works? How do I work around this problem?

@jesdynf
Copy link
Collaborator

jesdynf commented Apr 23, 2022

This got fixed in the https://community.open-emr.org/t/openemr-6-1-0-devops/18069 push.

@jesdynf jesdynf closed this as completed Apr 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants