Planning for OpenEMR 5.0.2 release

no change :grimacing:
still no users listing under admin login and physician login says invalid username/password

with ubuntu firefox https://six.openemr.io/openemr/interface/login/login.php?site=default admin login shows only admin user

also happening at https://eight.openemr.io/openemr/interface/login/login.php?site=default, so it’s the master branch that has a problem loading the users

Hi,

Chest pain… :slight_smile:

How about these 2 demos in https://www.open-emr.org/wiki/index.php/Development_5.0.2_Demo :
https://six.openemr.io/c/openemr/index.php
https://seven.openemr.io/f/openemr/index.php

(ensure you have that ‘c’ or that ‘f’ in the path)

1 Like

I tried the ‘six’ and it seems to be working well on a quick check.
–RBL

2 Likes

Hi,

Freezing the 5.0.2 branch (except for bug fixes). Please test, test, and then test some more.

The OpenEMR 5.0.2 development demos are here (4 environments each with a demo with and without demo data):
https://www.open-emr.org/wiki/index.php/Development_5.0.2_Demo

The OpenEMR 5.0.2 development package builds (and install/upgrade instruction sets) can be found here:
https://www.open-emr.org/wiki/index.php/OpenEMR_Downloads#Daily_snapshots

There is also a dev 5.0.2 docker that will upgrade automatically if proper conditions are met (https://hub.docker.com/r/openemr/openemr/):
"
Automatic upgrading of OpenEMR is supported when upgrade from 5.0.1 to 5.0.2+ (note this is not supported in the flex* series). In your docker-compose.yml file, you can basically change the 5.0.1 to 5.0.2 image and then do a docker-compose up. This will only work if you have set a shared volume for the /var/www/localhost/htdocs/openemr/sites directory (it will not work if either you didn’t set a shared volume or you set the shared volume to be the entire /var/www/localhost/htdocs/openemr directory). Before you do this, recommend backing everything up.
"

-brady

1 Like

:white_flag: last lap :slight_smile:

Congratulations to Brad et al as it always takes a significant effort to make a release!

  • ViSolve

Will there be a way to upgrade from AWS 5.0.1(7) to AWS 5.0.2?
–Ralf

hi @Ralf_Lukner ,
The dockers have a neat upgrade mechanism if certain criteria are met. Is there a docker-compose.yml in the AWS install? (I am guessing there is, which allows commands like docker-compose stop etc.). If so, can you paste what it looks like here.
thanks,
-brady

1 Like

Also gonna tag @jesdynf on above aws/docker upgrade discussion.

1 Like

Where would I look for the docker-compose.yml?

Also, would it be safer to create a new EC2 instance and then migrate the data over to the new instance somehow?

Something like Error Upgrade 5.0.1 to 5.0.2 could be a time-consuming problem for me if I’m doing the upgrade on the production instance.
–Ralf

hi @Ralf_Lukner ,
What does following command show:
docker ps -a

btw, above command will just list out active docker containers. Agree that will be best to do a trial run on a backup ec2 of your production instance when we get to that point.

ubuntu@ip-10-0-1-83:~$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3344de9fe048 hello-world “/hello” 4 weeks ago Exited (0) 4 weeks ago nostalgic_neumann
f401f8e1363e mysnapshot “/var/www/openemr/” 4 months ago Created 80/tcp, 443/tcp eloquent_mcnulty
f86553b67959 mysnapshot “standard_openemr_…” 4 months ago Created 80/tcp, 443/tcp epic_kalam
5187123d59f0 mysnapshot “/bin/bash” 4 months ago Created 80/tcp, 443/tcp affectionate_carson
8f38490e08fb mysnapshot “/usr/sbin/sshd -D” 4 months ago Created 80/tcp, 443/tcp, 0.0.0.0:32769->22/tcp nervous_elion
0ff0e2df5645 mysnapshot “/user/sbin/sshd -D” 4 months ago Created 80/tcp, 443/tcp, 0.0.0.0:32768->22/tcp elegant_goldstine
4024c1cd642a openemr/openemr:5.0.1 “./run_openemr.sh” 14 months ago Up 15 seconds 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp standard_openemr_1

Btw, I would be willing to help test the upgrade once it’s available.

ok, there should be a directory called standard, which will house the docker-compose.yml file. When you log in to your EC2 instance, what do you see with:
ls -al

Took a quick glance at the devops stuff. It might be at this path in ec2:

cd /root/openemr-devops/packages/standard

That’s where it is …
ubuntu@ip-10-0-1-83:~$ sudo ls -al /root/openemr-devops/packages/standard
total 8692
drwxr-xr-x 6 root root 4096 Jun 3 2018 .
drwxr-xr-x 8 root root 4096 Apr 28 2018 …
drwxr-xr-x 2 root root 4096 Apr 28 2018 ami
drwxr-xr-x 2 root root 4096 Apr 28 2018 cfn
-rwxr-xr-x 1 root root 8858496 Apr 28 2018 docker-compose
-r-x------ 1 root root 528 Jun 3 2018 docker-compose.yaml
-rw-r–r-- 1 root root 2820 Apr 28 2018 EULA.txt
-rw-r–r-- 1 root root 34 Apr 28 2018 .gitignore
-rw-r–r-- 1 root root 4075 Apr 28 2018 README.md
drwxr-xr-x 2 root root 4096 Apr 28 2018 scripts
drwxr-xr-x 2 root root 4096 Apr 28 2018 snippets

Paste the following output:

cat /root/openemr-devops/packages/standard/docker-compose.yaml

Also curious as to what is in that docker-compose directory:

ls -al /root/openemr-devops/packages/standard/docker-compose

ubuntu@ip-10-0-1-83:~$ sudo ls -al /root/openemr-devops/packages/standard/docker-compose
-rwxr-xr-x 1 root root 8858496 Apr 28 2018 /root/openemr-devops/packages/standard/docker-compose

Apparently nothing?