$ curl https://sourceforge.net/projects/openemr/files/OpenEMR%20Current/6.0.0/openemr-6.0.0.tar.gz --output openemr-6.0.0.tar.gz
$ tar -pxvzf openemr-6.0.0.tar.gz
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
$ file openemr-6.0.0.tar.gz
openemr-6.0.0.tar.gz: HTML document, ASCII text
Apparently it isnāt gzipped at all?
āRBL
There is another distribution file in the .zip format. I also tried to extract it instead. When I did so, I got the following error:
~/openemr-6.0.0$ curl https://sourceforge.net/projects/openemr/files/OpenEMR%20Current/6.0.0/openemr-6.0.0.zip --output openemr-6.0.0.zip
~/openemr-6.0.0$ unzip openemr-6.0.0.zip
Archive: openemr-6.0.0.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of openemr-6.0.0.zip or
openemr-6.0.0.zip.zip, and cannot find openemr-6.0.0.zip.ZIP, period.
I looked at the .zip distribution and found the following:
<html>
<head>
<title>301 Moved Permanently</title>
</head>
<body>
<h1>301 Moved Permanently</h1>
The resource has been moved to <a href="https://sourceforge.net/projects/openemr/files/OpenEMR%20Current/6.0.0/openemr-6.0.0.zip/">https://sourceforge.net/projects/openemr/files/OpenEMR%20Current/6.0.0/openemr-6.0.0.zip/</a>;
you should be redirected automatically.
</body>
</html>
Based on what @Ralf_Lukner posted it sounded like sourceforge did a 301 redirect but apparently. After checking now on a computer the link works just fine so disregard my comment.
I think the problem was that I did not use wget (I used curl), which created this bizarre download.
Do you know of a script or a way that I can upgrade only my database from 5.0.2p5 to 6.0.0? I have everything else upgraded on my test system (openemr directory, restored documents).
āRBL
When I tried to run the sql_upgrade.php script, it told me to check if mysqld was running. That made me concerned that the sql_upgrade.php script and the scripts it calls were not aware that the AWS STANDARD implementation has the MySQL server on another instance (āworkstationā) ā¦ there shouldnāt be a mysql server running locally on the docker in this case.
openemr calls the upgrade script DB access the same way as normal DB access for login say.
If using a RDS on AWS this should be seamless to our App if setup correctly.
So if upgrade doesnāt work, neither will openemr.
The sql_upgrade.php file does not work and at this point, and, of course, openemr doesnāt either ā¦ I suspect because the database is not ready and maybe other things are undone.
I wonder if it is failing for similar reasons that docker up failed for me (webserver would not respond at all) or if there are different issues at play.
I guess I will need to go through the sql_upgrade.php file manually and do all the things it would have done at a command line.
I see the OpenEMR preinstallation screen when I go to the web server.
Pre Install - Checking File and Directory Permissions
Welcome to OpenEMR. This utility will step you through the installation and configuration of OpenEMR for your practice.
Before proceeding, be sure that you have a properly installed and configured MySQL server available, and a PHP configured webserver.
Detailed installation instructions can be found in the āINSTALLā manual file.
If you are upgrading from a previous version, DO NOT use this script. Please read the āUpgradingā section found in the āINSTALLā manual file.
We will now ensure correct file and directory permissions before starting installation:
Ensuring following file is world-writableā¦
/var/www/localhost/htdocs/openemr/sites/default/sqlconf.php file is ready
Ensuring the /var/www/localhost/htdocs/openemr/sites/default/documents directory and its subdirectories have proper permissionsā¦
/var/www/localhost/htdocs/openemr/sites/default/documents directory and its subdirectories are ready.
All required files and directories have been verified.
Click Proceed to Step 1 to continue with a new installation.
CAUTION: If you are upgrading from a previous version, DO NOT use this script. Please read the āUpgradingā section found in the āINSTALLā manual file.
I have been trying to get an upgrade from OpenEMR Cloud (AWS) STANDARD 5.0.2p5 -> 6.0.0 to work for months now. So far, no luck in demonstrating a successful upgrade with a test replica of my system.
Looks like you are installing a new OpenEMR instance instead of upgrade.
This may mean your installed flag is not set for some reason due to how you tried to create the test instance.
If you have copied your production site directory to your new instance then you shouldnāt get screen youāre getting.
Check the sites/default/sqlconf.php and ensure the config is set
//////DO NOT TOUCH THIS///
$config = 1; /////////////
//////////////////////////
It worked!! It was fast (I put a lot of effort and $$ into optimizing performance of the database and EC2 instance)! Now I have an upgraded test system. Now Iām going to upgrade the production server.
āRBL
One more thing ā¦ when I try to upgrade my production sever, Iām running out of space when I try to copy my documents onto the docker volume. The test system did not have this problem. I tried deleting the error logs to free up room. Still failing. I read somewhere that this can sometimes be a permissions issue. Anyway, Iām trying to figure out to how make space (I have plenty of disk space but my docker space is apparently full? 43G?)
For some reason the upgrade keeps hanging ā¦ I suspect that the aws timeouts are coming into play here. I suspect that I will need to change some of the aws timeout parameters to longer values in order for the production database upgrade to succeed. Alas, I need to call it a night here at 3:00am CST. Iāll restore the v502p5 production system from snapshots for now and try again on a different night.
āRBL
Iām able to increase the size of the volumes and extend the filesystems. I have read the conceptual process of increasing a docker volume (backing it up, deleting it, and re-creating it with a bigger size option). I do not have the confidence to do this on a production system yet. I may play around with a docker volume on a test replica of a production system, however.
I do not have the technical knowledge and experience to backup, delete, and restore the OpenEMR docker with a larger size. Thus, what I am doing is something that does work for me ā¦ create a duplicate system of my AWS OpenEMR Cloud 5.0.2p5 STANDARD system and then upgrading that. For some reason, when I run a cloudformation stack, it creates a docker that does not run out of space as my existing EC2/docker does.