My Server: Ubuntu 22.04
Installed Java 17
Installed Docker - followed all necessary configuration and access right to complete the setup to this level.
Then follow:
curl -s https://raw.githubusercontent.com/ozone-his/ozone/main/scripts/install-stable.sh | bash /dev/stdin
I got the download completed without any error.
Then run “sudo ./start-demo-with-sso.sh”
At the very last stage container “ozone-openmrs-1” always shows error; I have tried at least 3 fresh installation.
From logs of ozone-openmrs-1 what I found is:
ERROR - CustomDispatcherServlet.setServletContext(66) |2025-06-23T06:51:23,715| [Ljava.lang.StackTraceElement;@724f9fcb
and also two more ERRORs like-
ERROR - AddressConfigurationLoader.loadAddressConfiguration(66) |2025-06-23T06:51:30,765| Address hierarchy configuration file appears invalid, skipping the loading process: /openmrs/data/configuration/addresshierarchy/addressConfiguration.xml
It seems like this is a know issue with OpenMRS when used with OAuth2 module.
Usually restarting the OpenMRS container after 5mins fixes this issue. Do note that this restart only needs to be done at first startup.
I have completed command sudo ./start-demo-with-sso.sh >> then waited 10 minutes then >> I have restarted the OpenMRS container by the command “sudo docker restart ozone-openmrs-1” - - now almost one hour 20 minutes it is showing “health: starting”.
@kazi.shahid Could you please confirm that your machine has at least 16GB of RAM and an 8-core or above processor?
The reason Ozone needs such high system resources is because it’s not just an integration platform — it also includes the full applications those are OpenMRS, Odoo, SENAITE, and Superset that come up on startup. These require sufficient RAM and CPU power to run smoothly.