looks like the daily install has failed at the initial setup screen:
UNABLE to open file ‘/var/www/html/openemr/sites/default/sqlconf.php’ for writing.
Still noting some erratic issues on the development demo. @stephenwaite, that error is because it was unable to download the translation file from another appliance on my server. Should get it worked out soon.
@MatthewVita, regarding speed, since there are many appliances going on the server, the server seems to give priorities to the ones that are used. So, if you use the development demo for a couple minutes it should speed up. Of course, using a server that is using Ubuntu 8.04 with VMware server version 1 is likely not helping things.
I have a terribly hacky suggestion… because potential end users will be confused/disheartened if the demo is slow, we can run a cron job to hit an openemr page every 3 minutes or so.
@stephenwaite , A new server is on my christmas list. Then the sky will be the limit
(btw, I am glad to cover this since will be using it also for other geeky non openemr stuff)
@MatthewVita , Sounds like a good idea. The reason the main 5.0 demo runs smoothly is because it gets used almost all day. What would be a good command to run from cron to do this? If needed, could even drop in a more intensive php script in the server which would hit to keep the engine going.
May be some room to optimize it on the vm end also. looks like 500MB memory for this vm may not be enough since seems to be using swap memory. When have time will increase the memory to see if that helps; issue with that is that the main server itself may then go into swap memory if vm’s take up to much memory…
noticed that you had stated " that error is because it was unable to download the translation file from another appliance on my server. Should get it worked out soon."
That error was because the development codebase was a bit “broken” today (as a result of one of my code review suggestions ) and a fix was checked in a couple hours ago. These things can happen occasionally in the development codebase especially since the number of daily commits is getting larger.
Regarding the translation file collection, I am gonna implement a more solid strategy on the translation file collection in the demo to avoid that issue.
PHP Fatal error: Uncaught Error: Call to a member function getRegistrationId() on null in /var/www/html/emr/services/product_registration_service.php:55
Stack trace:\n#0 /var/www/html/emr/interface/product_registration/product_registration_controller.php(47): services\\ProductRegistrationService->getProductStatus()
#1 /var/www/html/emr/interface/product_registration/product_registration_controller.php(41): ProductRegistrationController->get()
#2 /var/www/html/emr/interface/product_registration/product_registration_controller.php(75): ProductRegistrationController->__construct()
#3 {main}
thrown in /var/www/html/emr/services/product_registration_service.php on line 55, referer: http://23.30.162.115/emr/interface/main/about_page.php
I’ll look into that. Changing the actual demo takes a bit of work since it’s triggered to go whenever I starts it (it can be done but have been lazy so far ). I think giving it a bit more memory will be helpful which plan to do when have time.
I did do some work on optimizing the main server that runs the demo farm; I removed a daily backup script that took hours and lots of processing/memory which seems to have speed things up. Just doing that seemed to speed the demo up quite a bit.