Okay, I tried that. Things went from bad to worse.
Initially, things looked promising … I made sure I was working with /root/openemr-devops/packages/standard/
I did have to change the version from 3.1 to 2: version: '2'
in the docker_compose.yaml
because 3.1 was not supported:
$ sudo ./upgrade.sh
ERROR: Version in "./docker-compose.yaml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
Here is my “corrected” docker-compose.yaml:
version: '2'
services:
openemr:
restart: always
image: openemr/openemr:6.0.0
ports:
- 80:80
- 443:443
volumes:
- logvolume01:/var/log
- sitevolume:/var/www/localhost/htdocs/openemr/sites
environment:
MYSQL_HOST: 'xxxxxxxxxxxx.yyyyyyyy.rds.amazonaws.com'
MYSQL_ROOT_USER: openemr
MYSQL_ROOT_PASS: 'zzzzzzzzzzzzzzzzz'
MYSQL_USER: openemr
MYSQL_PASS: zzzzzzzzzzzzzzzzzz'
OE_USER: admin
OE_PASS: 'qqqqqqqqqqqqqqqqqqq'
volumes:
logvolume01: {}
sitevolume: {}
I modified my upgrade.sh script as follows:
#!/bin/sh
# pull in 6.0.0 container
cd /root/openemr-devops/packages/standard
sed -i 's/5.0.2/6.0.0/' docker-compose.yaml
./docker-compose up -d
And executed the script & rebooted the instance:
$ sudo ./upgrade.sh
Recreating standard_openemr_1
$ sudo reboot
Now that EC2 will not respond at all:
Going to the latest version of Chrome on Mac:
URL: xxxxxx.yyyyyyy.compute.amazonaws.com (EC2 instance address – web server)
Yields this error:
This site can’t be reached xxxxxx.yyyyyy.compute.amazonaws.com refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
There is nothing relevant in the logs as far as I can tell.
Basically, the EC2 web server can no longer be reached (from a web browser). I can ssh into the EC2 instance, however. Once we are done getting any information / trying to repair this instance … if we cannot repair it …I plan to terminate it and restart a replica from an image.